From: Daniel Jacobowitz <drow@false.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>,
msnyder@vmware.com, gdb-patches@sourceware.org
Subject: Re: [RFA] [patch] 'info symbol' to print more info
Date: Mon, 17 Nov 2008 23:35:00 -0000 [thread overview]
Message-ID: <20081117193531.GA17547@caradoc.them.org> (raw)
In-Reply-To: <8ac60eac0811171112x5b555146lefb27f36e773ac25@mail.gmail.com>
This discussion seems to have wandered far afield from Paul's
reasonable patch :-(
On Mon, Nov 17, 2008 at 11:12:45AM -0800, Paul Pluzhnikov wrote:
> > For instance, there was this discussion
> > about not printing the name of the objfile if MULTI_OBJFILE_P. If we
> > get rid of that, does it reduce the number of cases?
>
> I think the answer is no, because we still have to check for:
>
> && osect->objfile && osect->objfile->name
I suspect that can be an assert, or you could use "<unnamed objfile>".
If that helps. I can't imagine where we'd get an objfile section
without an objfile.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-17 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 16:15 Paul Pluzhnikov
2008-11-15 17:00 ` Michael Snyder
2008-11-15 17:22 ` Paul Pluzhnikov
2008-11-15 18:51 ` Michael Snyder
2008-11-15 23:16 ` Paul Pluzhnikov
2008-11-15 23:35 ` Andreas Schwab
2008-11-16 1:35 ` Eli Zaretskii
2008-11-16 1:38 ` Paul Pluzhnikov
2008-11-16 8:20 ` Joel Brobecker
2008-11-17 22:37 ` Paul Pluzhnikov
2008-11-17 23:35 ` Daniel Jacobowitz [this message]
2008-11-18 16:07 ` Paul Pluzhnikov
2008-11-18 19:55 ` Eli Zaretskii
2008-11-19 4:20 ` Joel Brobecker
2008-11-19 12:45 ` Paul Pluzhnikov
2008-11-15 17:40 ` Eli Zaretskii
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=20081117193531.GA17547@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=ppluzhnikov@google.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