From: Brian Dessent <brian@dessent.net>
To: gdb@sources.redhat.com
Subject: Re: Dumping core on windows?
Date: Wed, 16 Nov 2005 22:23:00 -0000 [thread overview]
Message-ID: <437BB169.D9EFCF92@dessent.net> (raw)
In-Reply-To: <437B8F4C.8060708@candelatech.com>
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
next prev parent reply other threads:[~2005-11-16 22:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 19:26 Ben Greear
2005-11-16 19:50 ` Brian Dessent
2005-11-16 19:58 ` Ben Greear
2005-11-16 20:20 ` Christopher Faylor
2005-11-16 22:23 ` Brian Dessent [this message]
2005-11-16 22:29 ` Ben Greear
2005-11-17 0:09 ` Christopher Faylor
2005-11-17 1:18 ` Brian Dessent
2005-11-17 1:29 ` Ben Greear
2005-11-17 1:38 ` Brian Dessent
2005-11-17 3:29 ` Christopher Faylor
2005-11-17 4:07 ` gdb and threads on windows Ben Greear
2005-11-17 6:06 ` Dumping core on windows? Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=437BB169.D9EFCF92@dessent.net \
--to=brian@dessent.net \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox