From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: -symbol-list-lines
Date: Tue, 17 Feb 2004 01:20:00 -0000 [thread overview]
Message-ID: <20040217012035.GA4965@nevyn.them.org> (raw)
In-Reply-To: <20040216205557.GE3978@white>
On Mon, Feb 16, 2004 at 03:55:58PM -0500, Bob Rossi wrote:
> On Mon, Feb 16, 2004 at 03:45:16PM -0500, Daniel Jacobowitz wrote:
> > On Mon, Feb 16, 2004 at 03:40:35PM -0500, Bob Rossi wrote:
> > > I am seeing 2 potential problems,
> > >
> > > Several lines come back as {pc="0x08048406",line="0"},
> > > should the value "0" be documented? or is it a bug?
> > >
> > > Also, for some reason, a value is repeated
> > > {pc="0x0804849c",line="38"}. Is this ok?
> >
> > I can't say anything about what is appropriate (or useful) for the MI
> > interface but I can tell you what's going on. This matches the
> > structure of the internal line table precisely.
> >
> > - line 0 means end-of-sequence. I.E. PCs greater than 0x8048406 that
> > don't have a new starting line do not belong to this line number table.
>
> I personally can't see why this would be useful to front ends. Can
> anyone else? If it isn't, I will submit a patch to not print this data.
>
> > - duplicated line numbers are emitted by the compiler to mark, mostly,
> > the ends of prologues. Sometimes the prologue is zero-sized.
>
> Would keeping a list internally of numbers that have been sent out
> already be reasonable? or is it repeating the data unimportant?
>
> I would also be willing to fix this.
I don't know. I think I'd prefer for frontends to tolerate this data;
just because I can't think of a use for it now doesn't mean someone
else won't later. I was recently reminded that "front-end" can be a
pretty broad concept, not just user interfaces.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-17 1:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 20:40 -symbol-list-lines Bob Rossi
2004-02-16 20:45 ` -symbol-list-lines Daniel Jacobowitz
2004-02-16 20:56 ` -symbol-list-lines Bob Rossi
2004-02-17 1:20 ` Daniel Jacobowitz [this message]
2004-02-17 1:28 ` -symbol-list-lines Bob Rossi
2004-02-17 5:45 ` -symbol-list-lines Eli Zaretskii
2004-02-18 14:29 ` -symbol-list-lines Alain Magloire
2004-02-17 5:44 ` -symbol-list-lines 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=20040217012035.GA4965@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.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