From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1651 invoked by alias); 17 Nov 2005 00:09:50 -0000 Received: (qmail 1640 invoked by uid 22791); 17 Nov 2005 00:09:49 -0000 X-Spam-Check-By: sourceware.org Received: from c-24-61-23-223.hsd1.ma.comcast.net (HELO cgf.cx) (24.61.23.223) by sourceware.org (qpsmtpd/0.31-dev) with ESMTP; Thu, 17 Nov 2005 00:09:48 +0000 Received: by cgf.cx (Postfix, from userid 201) id DE5A813C6C1; Wed, 16 Nov 2005 19:09:46 -0500 (EST) Date: Thu, 17 Nov 2005 00:09:00 -0000 From: Christopher Faylor To: gdb@sources.redhat.com Subject: Re: Dumping core on windows? Message-ID: <20051117000946.GA28025@trixie.casa.cgf.cx> Mail-Followup-To: gdb@sources.redhat.com References: <437B87D4.4060304@candelatech.com> <437B8D6B.65249253@dessent.net> <437B8F4C.8060708@candelatech.com> <437BB169.D9EFCF92@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <437BB169.D9EFCF92@dessent.net> User-Agent: Mutt/1.5.8i 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/msg00328.txt.bz2 On Wed, Nov 16, 2005 at 02:23:37PM -0800, Brian Dessent wrote: >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. Have you actually tried this, Brian? I was going to suggest something like this but I wasn't sure if it worked with dumper. cgf