From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20195 invoked by alias); 16 Nov 2005 22:23:48 -0000 Received: (qmail 20108 invoked by uid 22791); 16 Nov 2005 22:23:43 -0000 Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 16 Nov 2005 22:23:43 +0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.54) id 1EcVgo-00025R-A3 for gdb@sources.redhat.com; Wed, 16 Nov 2005 22:23:38 +0000 Message-ID: <437BB169.D9EFCF92@dessent.net> Date: Wed, 16 Nov 2005 22:23:00 -0000 From: Brian Dessent MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Re: Dumping core on windows? References: <437B87D4.4060304@candelatech.com> <437B8D6B.65249253@dessent.net> <437B8F4C.8060708@candelatech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00326.txt.bz2 Ben Greear wrote: > After hours or days, my application crashes. It's not overly convenient for me > to attach gdb to the process(es), but it can be done if that is the only way. Since your app is not a Cygwin program you can't just set 'error_start' in $CYGWIN. But you can do the equivalent to set dumper as the windows JIT debugger. Set "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger" to a REG_SZ of the filename and args of dumper. Use "%ld" to represent the PID. e.g. "c:\cygwin\bin\dumper.exe myapp %ld" will create myapp.core when the program faults. Set "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Auto" to a REG_SZ of "1" to have this happen without the popup "This application has performed an illegal operation, ... [Debug] [Close]". However, if you do this then there will be no indication of the fault -- other than the existance of the core file and your app no longer running (and possibly an entry in the event log) -- so you might want to leave auto at 0 if you want to see when the fault occurs. Brian