From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: gdb@sourceware.org
Subject: Re: Dumping core on windows?
Date: Thu, 17 Nov 2005 03:29:00 -0000 [thread overview]
Message-ID: <20051117032949.GA9646@trixie.casa.cgf.cx> (raw)
In-Reply-To: <437BDF25.87B13E4A@dessent.net>
On Wed, Nov 16, 2005 at 05:38:45PM -0800, Brian Dessent wrote:
>Ben Greear wrote:
>>Is there a way to get the program name programatically so that this
>>works with any application? For instance, I'm using this value for
>>Debugger:
>
>Not that I know of. Of course, you could easily write a wrapper for
>dumper that uses the PID to get the image name of the faulting process,
>and calls dumper with that filename. Or just patch dumper to do this.
>
>>Also, is there a way to cause a fault in a program for testing, similar
>>to 'kill -11 pid' ?
>
>You can just run dumper directly with the pid of the running process to
>generate a core file without causing a fault. However this will cause
>the process to terminate (something about a win32 limitation of not
>being able to detach from a process without killing it.)
This limitation does not exist on XP or greater. Corinna Vinschen modified
gdb to take advantage of that fact.
See DebugSetProcessKillOnExit.
cgf
next prev parent reply other threads:[~2005-11-17 3:29 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
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 [this message]
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=20051117032949.GA9646@trixie.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=gdb@sourceware.org \
/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