From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: -symbol-list-lines doco update
Date: Tue, 17 Feb 2004 20:46:00 -0000 [thread overview]
Message-ID: <20040217204628.GB5744@nevyn.them.org> (raw)
In-Reply-To: <20040217200911.GD5982@white>
On Tue, Feb 17, 2004 at 03:09:11PM -0500, Bob Rossi wrote:
> > Please use "@itemize @minus" and "@item" here, like this:
> >
> > There are two interesting points to be mentioned here.
> >
> > @itemize @minus
> > @item
> > The line number can be returned as ``0''. The line number ``0'' means
> >
> > etc., I hope you get the point. The Texinfo translators, like
> > makeinfo and TeX, will then take care of producing the "-" before
> > every @item, and will also indent the list so it looks pretty.
>
> Understood, thanks. Andrew, I will use @bullet.
>
> > > +For example, PCs greater than 0x8048406 that
> > > +don't have a new starting line do not belong to this line number table.
>
> I don't even know what this means. That's why it's confusing. Maybe
> Daniel can give us a better description, otherwise, I'll just put
>
> The line number can be returned as ''0''.
>
> I will resubmit this patch soon, if Daniel doesn't have a better
> description.
I'm not especially good with documentation. Let me see if I can
explain the comment, and then maybe you can think of a better way to
say it...
An entry in the line table is "starting PC" and "line". But a line is
not a starting PC, it's a range of PC values from start to end. The
end is taken from the next line entry in the table. The line table:
0x0 1
0x4 2
0x8 4
0xc 0
means:
line 1 from 0x0 to 0x3
line 2 from 0x4 to 0x7
line 4 from 0x8 to 0xb
no line number information at 0xc
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-02-17 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 15:43 Bob Rossi
2004-02-17 19:23 ` Eli Zaretskii
2004-02-17 19:50 ` Andrew Cagney
2004-02-17 20:54 ` Eli Zaretskii
2004-02-17 20:09 ` Bob Rossi
2004-02-17 20:46 ` Daniel Jacobowitz [this message]
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=20040217204628.GB5744@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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