From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, doc RFA]: New python function lookup_global_symbol
Date: Tue, 22 Feb 2011 22:50:00 -0000 [thread overview]
Message-ID: <m3vd0bka2n.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110218235945.997602461AA@ruffy.mtv.corp.google.com> (Doug Evans's message of "Fri, 18 Feb 2011 15:59:45 -0800 (PST)")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> I couldn't figure out how to lookup up a global symbol without
Doug> having a running program and without knowing the block it is in.
Doug> Plus lookup_symbol already has a specified behaviour when the
Doug> `block' argument is elided: use the current frame.
Doug> So it seemed best to add a new function.
FWIW, it seems fine to me.
Tom
prev parent reply other threads:[~2011-02-22 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 1:04 Doug Evans
2011-02-19 10:37 ` Eli Zaretskii
2011-02-22 23:04 ` Doug Evans
2011-02-23 4:17 ` Eli Zaretskii
2011-02-24 3:51 ` Doug Evans
2011-02-24 4:14 ` Eli Zaretskii
2011-02-22 22:50 ` 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=m3vd0bka2n.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@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