From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, danny.backx@scarlet.be
Subject: Re: Post mortem debugging for Windows CE
Date: Tue, 05 May 2009 16:53:00 -0000 [thread overview]
Message-ID: <200905051753.45227.pedro@codesourcery.com> (raw)
In-Reply-To: <1241530252.500.95.camel@dannypc>
On Tuesday 05 May 2009 14:30:51, Danny Backx wrote:
> It looks like I'm getting close to something that works. Small session
> below. Cleanup and more testing are certainly required.
This is looking very good!
> I'm about to look into your suggestion about .module sections.
>
> How can I observe the effect of that ? How can I test ?
The .modules sections would contain the list of loaded modules
at the time of the crash. So, 'info sharedlibrary' should list the same
list of dlls as the live inferior had, and their load addresses should
be the same.
You could tweak your test app to move the crashing code into a mini
dll you'd write. Use 'set sysroot' or 'set solib-search-path' command to
point GDB at the host copy of the dll, and load the minidump
into GDB. GDB should be able to show you the crash site source code,
backtracing from the function in the dll should work, and
'info sharedlibrary' should report correct data, of course.
--
Pedro Alves
next prev parent reply other threads:[~2009-05-05 16:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 14:45 Danny Backx
2009-04-28 16:02 ` Pedro Alves
2009-04-28 17:48 ` Danny Backx
2009-04-28 19:18 ` Danny Backx
2009-04-29 7:10 ` Eli Zaretskii
2009-04-29 7:19 ` Danny Backx
2009-04-29 7:44 ` Eli Zaretskii
2009-04-30 7:25 ` Danny Backx
2009-04-30 9:58 ` Pedro Alves
2009-05-01 14:35 ` Danny Backx
2009-05-01 15:37 ` Pedro Alves
2009-05-05 13:31 ` Danny Backx
2009-05-05 16:53 ` Pedro Alves [this message]
2009-05-06 14:13 ` Danny Backx
2009-05-06 14:34 ` Pedro Alves
2009-05-06 20:05 ` Danny Backx
2009-05-06 20:47 ` Pedro Alves
2009-05-07 1:21 ` Danny Backx
2009-05-10 19:21 ` Pedro Alves
2009-05-11 14:03 ` Danny Backx
2009-05-11 15:00 ` Danny Backx
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=200905051753.45227.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=danny.backx@scarlet.be \
--cc=gdb-patches@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