Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: danny.backx@scarlet.be
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: Post mortem debugging for Windows CE
Date: Wed, 29 Apr 2009 07:10:00 -0000	[thread overview]
Message-ID: <83d4awdjfh.fsf@gnu.org> (raw)
In-Reply-To: <1240946254.29047.159.camel@dannypc>

> From: Danny Backx <danny.backx@scarlet.be>
> Cc: gdb-patches@sourceware.org
> Date: Tue, 28 Apr 2009 21:17:34 +0200
> 
> Here's more info, I've decoded more of the dump.
> 
> I think the three chunks of memory included (see stream 8) are :
> #0 : 80 bytes from the program text at the point of the crash
> #1 : 380 bytes near the end of address space (I have no clue)
> #2 : some amount of memory from the frame pointer (see stream 6)

Thanks.

I know very little about Windows minidump files, but unless this
feature is going to allow GDB to debug the dump, as we do with core
files, the feature does not belong to GDB but to Binutils.  At least
IMHO.


  reply	other threads:[~2009-04-29  7:10 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 [this message]
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
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=83d4awdjfh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=danny.backx@scarlet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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