From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add fullname field for MI -break-info command
Date: Wed, 25 Jan 2006 13:51:00 -0000 [thread overview]
Message-ID: <20060125135122.GA10783@nevyn.them.org> (raw)
In-Reply-To: <200601251631.19779.ghost@cs.msu.su>
On Wed, Jan 25, 2006 at 04:31:19PM +0300, Vladimir Prus wrote:
> On Wednesday 25 January 2006 00:13, Daniel Jacobowitz wrote:
>
> > > + {
> > > + struct symtab_and_line sal = find_pc_line (b->loc->address,
> > > 0); + symtab_to_fullname (sal.symtab);
> > > +
> > > + if (sal.symtab->fullname)
> > > + {
> > > + annotate_field(10);
> >
> > annotate_field (10);
>
> Is that a formatting change, or moving the "annotate_field" call out of "if"?
Sorry, I just meant the space before the parentheses.
> > But I don't think you need this at all; there's no point emitting
> > annotations when we're guarded by ui_out_is_mi_like_p.
>
> For a future: can you explain what "annotate_field" does? The annotate.h file
> has no comments at all, and gdbint has "annotate_field" only inside code
> examples. And generally, what are "annotations"?
As Bob said, an old interface. See "set annotate".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-25 13:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 16:42 Vladimir Prus
2006-01-24 16:51 ` Bob Rossi
2006-01-25 11:07 ` Vladimir Prus
2006-01-25 12:10 ` Bob Rossi
2006-01-25 12:37 ` Andreas Schwab
2006-01-25 12:50 ` Vladimir Prus
2006-01-25 13:45 ` Bob Rossi
2006-01-26 7:10 ` Vladimir Prus
2006-01-28 13:10 ` Vladimir Prus
2006-02-01 22:32 ` Daniel Jacobowitz
2006-02-02 7:07 ` Vladimir Prus
2006-02-06 21:55 ` Daniel Jacobowitz
2006-01-24 21:13 ` Daniel Jacobowitz
2006-01-25 13:31 ` Vladimir Prus
2006-01-25 13:46 ` Bob Rossi
2006-01-26 7:20 ` Vladimir Prus
2006-01-25 13:51 ` Daniel Jacobowitz [this message]
2006-01-25 17:56 ` Eli Zaretskii
2006-01-24 16:42 Vladimir Prus
2006-01-26 7:06 Nick Roberts
2006-01-26 7:13 Nick Roberts
2006-01-26 11:27 Nick Roberts
2006-01-26 11:44 ` Vladimir Prus
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=20060125135122.GA10783@nevyn.them.org \
--to=drow@false.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