From: Tom Tromey <tromey@redhat.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: About the "info locals" command of gdb and python pretty printer
Date: Tue, 22 Jun 2010 02:18:00 -0000 [thread overview]
Message-ID: <m3k4prg690.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C2003E8.3000407@gmail.com> (asmwarrior@gmail.com's message of "Tue, 22 Jun 2010 08:29:28 +0800")
>>>>> ">" == Asm gmail <asmwarrior@gmail.com> writes:
>> I'm not sure how to get a "stack track" when gdb crashed. Do I need to
>> run GDB under GDB. So, the debuggee GDB get crashed, the debugger GDB
>> can generate some stack trace inforamtion?
Yes. Or at least, try that, and if it does not work we may need to look
into alternatives.
Tom
next prev parent reply other threads:[~2010-06-22 2:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 9:13 asmwarrior
2010-06-21 7:48 ` André Pönitz
2010-06-21 20:08 ` Tom Tromey
2010-06-22 0:29 ` asmwarrior
2010-06-22 2:18 ` Tom Tromey [this message]
2010-06-23 12:30 ` asmwarrior
[not found] ` <4C21FCDC.5050503__12891.7291098789$1277296251$gmane$org@gmail.com>
2010-06-23 20:28 ` Tom Tromey
2010-06-24 1:16 ` asmwarrior
2010-07-02 10:57 ` Matthias Klose
2010-06-21 3:02 asmwarrior
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=m3k4prg690.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=asmwarrior@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).