From: "Eli Zaretskii" <eliz@elta.co.il>
To: Bob Rossi <bob@brasko.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: -symbol-list-lines doco update
Date: Tue, 17 Feb 2004 19:23:00 -0000 [thread overview]
Message-ID: <9003-Tue17Feb2004212321+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040217154339.GA5684@white> (message from Bob Rossi on Tue, 17 Feb 2004 10:43:39 -0500)
> Date: Tue, 17 Feb 2004 10:43:39 -0500
> From: Bob Rossi <bob@brasko.net>
>
> This documents several of the special case's that -symbol-list-lines
> outputs.
Thanks. I have several comments about your Texinfo usage.
> +There are two interesting points to be mentioned here.
> +
> +- The line number can be returned as "0". The line number "0" means
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.
Note two other changes I made in the original text: "0" should be
``0'', and there should be 2 blanks after each period that ends a
sentence. These are basic rules of Texinfo and should be observed
throughout.
> +For example, PCs greater than 0x8048406 that
> +don't have a new starting line do not belong to this line number table.
This sentence is confusing, I think: if I were a programmer of a front
end, I'd have hard time understanding what it means. What ``line
number table'' are we talking about, and what does it mean that a PC
value ``does not belong'' to it? Also, ``don't have a new starting
line'' is unclear, at least to me.
> +Duplicated line numbers are emitted by the compiler to mark, mostly,
> +the ends of prologues.
I think there's another noteworthy case where this happens: when
optimizations cause the code produced for some line be scattered
among the PC values.
Thanks again for taking time to write this up.
next prev parent reply other threads:[~2004-02-17 19:23 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 [this message]
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
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=9003-Tue17Feb2004212321+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=bob@brasko.net \
--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