From: Eli Zaretskii <eliz@is.elta.co.il>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [repost] Re: RFC: support debug info in separate files
Date: Mon, 23 Dec 2002 06:59:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1021223114735.13625A-100000@is> (raw)
In-Reply-To: <vt2el89xf85.fsf@zenia.red-bean.com>
On 23 Dec 2002, Jim Blandy wrote:
> - The documentation has been completely rewritten, and provides much
> more detail. It includes all the information needed to implement
Thanks. The doco patch is approved (assuming that the code is
accepted). I have a few minor change requests:
> + @cindex .debug subdirectories
Please use the normal markup in @cindex entries, in this case .debug
should be in @file...
> + @cindex .gnu_debuglink sections
...and here .gnu_debuglink should be in @code.
> + Drepper's @file{elfutils} package, starting with version 0.53,
> + contains a version of the @code{strip} command such that the command
> + @samp{strip foo -f foo.debug} removes the debugging information from
I think it's better to put commands users type in @kbd instead of @samp.
But I don't object to @samp if you like it better.
> + @kindex gnu_debuglink_crc32
> + @example
> + unsigned long
> + gnu_debuglink_crc32 (unsigned long crc, unsigned char *buf, size_t len)
IIRC, we decided to use @smallexample throughout. Also, the last line
above is too long even for @smallexample (will produce overfull hbox
warnings from TeX), so please break it into 2 lines.
Thanks again for such a clear and concise description.
next prev parent reply other threads:[~2002-12-23 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 20:27 Jim Blandy
2002-11-25 22:34 ` Eli Zaretskii
2002-12-09 19:55 ` Jim Blandy
2002-12-10 12:19 ` Eli Zaretskii
2002-12-09 22:13 ` Elena Zannoni
2002-12-10 8:13 ` Andrew Cagney
2002-12-10 9:14 ` Elena Zannoni
2002-12-10 11:39 ` Andrew Cagney
2002-12-10 12:43 ` Eli Zaretskii
2002-12-14 16:48 ` Jim Blandy
2002-12-23 1:25 ` Jim Blandy
2002-12-23 1:58 ` [repost] " Jim Blandy
2002-12-23 6:59 ` Eli Zaretskii [this message]
2003-01-23 23:04 ` Jim Blandy
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=Pine.SUN.3.91.1021223114735.13625A-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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