From: Stan Shebs <stan@codesourcery.com>
To: tromey@redhat.com
Cc: Stan Shebs <stan@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Dwarf location expressions, tracing and printing
Date: Tue, 20 Apr 2010 19:03:00 -0000 [thread overview]
Message-ID: <4BCDFA67.2030404@codesourcery.com> (raw)
In-Reply-To: <m3fx2qgg12.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:
>>>>>>
>
> Stan> Perhaps the most interesting part is that I finally got tired of
> Stan> working blind and filled out description location functions, so
> Stan> now both "info scope" and "info address" have quite a lot of say
> Stan> about variables. Try things like "info scope
> Stan> handle_inferior_event" to get some truly awesome verbiage. :-)
>
> Thanks, I think this is great.
>
> I think Jan had a similar patch that would enable disassembling the
> DWARF expression. I'm not sure what happened to that; it seems like
> something that would at least be useful when working on gdb or other
> parts of the toolchain.
>
What I did is not quite the same thing, in that it restricts itself to
interpreting location expressions, and tries to do it in a
user-intelligible way, no opcodes shown. But yeah, we could use more
display power; with dwarf things being so data-driven, GDB backtrace
alone isn't that useful.
Stan
next prev parent reply other threads:[~2010-04-20 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 1:07 Stan Shebs
2010-04-20 18:01 ` Tom Tromey
2010-04-20 19:03 ` Stan Shebs [this message]
2010-04-20 19:26 ` Stan Shebs
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=4BCDFA67.2030404@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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