From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Tristan Su <sooqing@gmail.com>, gdb <gdb@sourceware.org>
Subject: Re: can pahole print a struct definition in a given CU?
Date: Wed, 02 Jan 2013 19:05:00 -0000 [thread overview]
Message-ID: <87y5gbwglp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22ToZbGzscJ4gSN+GOLEqdMfF-U30n3eGn9BW7A8hCOpgw@mail.gmail.com> (Doug Evans's message of "Wed, 2 Jan 2013 11:56:35 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> Thus,
Doug> what about adding a "context" parameter to parse_and_eval, etc.?
Doug> And then provide a way to specify that context (e.g., both from the
Doug> CLI and from Python).
Doug> We'd still have to support "p 'bar.c'::foo + 'baz.c::foo'", but when,
Doug> e.g, cut-n-pasting expressions from source we shouldn't have to force
Doug> the user to insert 'bar.c::' in front of objects that gdb might end up
Doug> otherwise picking the wrong one for.
Doug> E.g., something like: (gdb) with-symtab bar.c p foo+baz
Doug> or whatever.
It would be fine by me.
I was just pointing out the simplest way to make pahole work the same
way ptype does.
Really I would like to roll the pahole functionality into ptype.
It is useful enough that there's no reason to need a second command for it.
Tom
next prev parent reply other threads:[~2013-01-02 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 14:15 Tristan Su
2013-01-02 17:32 ` Tom Tromey
2013-01-02 18:56 ` Doug Evans
2013-01-02 19:05 ` Tom Tromey [this message]
2013-01-02 19:06 ` Doug Evans
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=87y5gbwglp.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=sooqing@gmail.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