Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Skip declarations in "info variables"
Date: Sat, 14 Nov 2009 15:54:00 -0000	[thread overview]
Message-ID: <20091114155316.GB17114@caradoc.them.org> (raw)
In-Reply-To: <833a4ho3ej.fsf@gnu.org>

On Sat, Nov 14, 2009 at 11:35:00AM +0200, Eli Zaretskii wrote:
> To decide whether or not this is a Good Thing, we need to answer a
> question: What is the purpose of "info variables"?  More specifically,
> what are the main use-cases for using it?  Can people please share
> their experience with this command?
> 
> Without that, I'm not sure we are not removing a potentially useful
> behavior.

A very good question.

I use "info variables" to find definitions - and some information
about where they come from.  With all the declarations showing up I
can't figure out what file defined the variable, which I find
inconvenient.  Actually, I'd like it even better if I had the
memory location...

There's usually at least one definition, so the only thing the
declarations add is a list of files that (may or may not depending on
the whim of the compiler) have referenced the global variable.

Thoughts?  Anyone see a use for the declarations that I don't?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-11-14 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 21:44 Daniel Jacobowitz
2009-11-13 22:27 ` Joel Brobecker
2009-11-14  9:36 ` Eli Zaretskii
2009-11-14 15:54   ` Daniel Jacobowitz [this message]
2009-11-14 16:03     ` Paul Pluzhnikov
2009-12-28 21:05   ` Daniel Jacobowitz
2009-12-28 21:21     ` Eli Zaretskii
2009-12-28 21:31       ` Daniel Jacobowitz

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=20091114155316.GB17114@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --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