From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Shadowcat <shadowcat@phasethrough.com>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Dereferencing pointers on "backtrace full"
Date: Tue, 15 Sep 2009 19:02:00 -0000 [thread overview]
Message-ID: <m34or4xc9a.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4AAFD08B.2030404@vmware.com> (Michael Snyder's message of "Tue, 15 Sep 2009 10:36:11 -0700")
>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
Tom> You might be able to do it using Python scripting, in CVS GDB. I am not
Tom> certain... we have a "backtrace" written purely in Python on the archer
Tom> python branch, but offhand I don't recall whether all the infrastructure
Tom> bits needed for this have been pushed upstream yet.
Michael> Using the old-style gdb scripting language:
Michael> while (1)
Michael> info locals
Michael> up
Michael> end
This doesn't dereference pointers.
Tom
prev parent reply other threads:[~2009-09-15 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 10:21 Shadowcat
2009-09-14 15:44 ` Tom Tromey
2009-09-15 17:36 ` Michael Snyder
2009-09-15 19:02 ` Tom Tromey [this message]
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=m34or4xc9a.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=shadowcat@phasethrough.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