From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [2/2] RFA: implement 'set print symbol'
Date: Mon, 09 Apr 2012 17:55:00 -0000 [thread overview]
Message-ID: <83r4vw7pwv.fsf@gnu.org> (raw)
In-Reply-To: <87zkak94w8.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 09 Apr 2012 11:44:23 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Tom> If you pick a better name, I will change the patch.
>
> Eli> How about "set print auto-symbol-filename"?
>
> Eli> Or maybe make "set print symbol-filename" a tristate setting, with an
> Eli> additional state "always"?
>
> It isn't directly related to whether or not the file name is printed.
> It has to do with whether the symbol name itself is printed.
> So I don't think either of these really fits.
Maybe I misunderstand what "set print symbol-filename" does, but at
least the manual seems to imply that it affects "print /a":
If you have a pointer and you are not sure where it points, try
@samp{set print symbol-filename on}. Then you can determine the name
and source file location of the variable where it points, using
@samp{p/a @var{pointer}}. This interprets the address in symbolic
form.
And your change makes it so the symbol is printed even without the /a
part, AFAIU. So what am I missing?
next prev parent reply other threads:[~2012-04-09 17:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 18:03 Tom Tromey
2012-04-05 21:13 ` Eli Zaretskii
2012-04-09 14:32 ` Tom Tromey
2012-04-09 16:31 ` Eli Zaretskii
2012-04-09 17:44 ` Tom Tromey
2012-04-09 17:55 ` Eli Zaretskii [this message]
2012-04-09 18:00 ` Tom Tromey
2012-04-09 19:14 ` Jan Kratochvil
2012-04-09 19:21 ` Tom Tromey
2012-04-09 19:36 ` Jan Kratochvil
2012-04-09 20:45 ` Eli Zaretskii
2012-04-09 21:04 ` Tom Tromey
2012-04-10 6:17 ` Eli Zaretskii
2012-04-10 6:56 ` Jan Kratochvil
2012-04-10 7:50 ` Eli Zaretskii
2012-04-10 8:19 ` Jan Kratochvil
2012-04-16 21:14 ` Tom Tromey
2012-05-14 19:39 ` Tom Tromey
2012-04-17 0:54 ` Doug Evans
2012-04-17 11:43 ` Tom Tromey
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=83r4vw7pwv.fsf@gnu.org \
--to=eliz@gnu.org \
--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