From: Brian Dessent <brian@dessent.net>
To: gdb@sources.redhat.com
Subject: Re: Dumping core on windows?
Date: Thu, 17 Nov 2005 01:18:00 -0000 [thread overview]
Message-ID: <437BD9F9.C2632918@dessent.net> (raw)
In-Reply-To: <20051117000946.GA28025@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> Have you actually tried this, Brian? I was going to suggest something
> like this but I wasn't sure if it worked with dumper.
Yeah, I tried it before posting and it seemed to work - it created the
core but I didn't try loading it into GDB. At first I thought it did
not, though, because I was trying to specify a path to the filename
argument of dumper, which does not work - it seems to create it using
the given filename in the CWD of the faulting program, regardless of any
path you give it.
And I forgot to mention that you can run "drwtsn32 -i" to reinstall the
default Dr. Watson fault handler after you're done with dumper.
(BTW, there is a second %ld argument that the system will pass if
present, I'm not sure what it represents though. Perhaps it's the
exception number, but I tried testing with an access violation but the
second parameter was 1928 - nothing close to 0xC0000005. I thought it
also might have been the thread ID of the fault but that did not match
up either... so it's a mystery to me.)
Brian
next prev parent reply other threads:[~2005-11-17 1:18 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 [this message]
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=437BD9F9.C2632918@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