From: Jim Blandy <jimb@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: support debug info in separate files
Date: Mon, 09 Dec 2002 19:55:00 -0000 [thread overview]
Message-ID: <vt27keid1kl.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1021126082512.23833G@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> On 25 Nov 2002, Jim Blandy wrote:
>
> > This patch, written by Alexander Larsson, allows GDB to use debug info
> > that has been extracted into a separate executable file, using the
> > "strip -f" command as provided in Ulrich Drepper's elfutils.
>
> Does that mean this feature is not supported by GNU `strip'? If so, this
> should be reflected in the docs.
On rereading I think the docs should be a bit more detailed about
all that, yeah.
> > + debugfile = alloca (strlen (debug_file_directory) + 1
> > + + strlen (dir)
> > + + strlen (".debug/")
> > + + strlen (basename)
> > + + 1);
>
> `.debug' is an invalid file name on DOS 8+3 filesystems (leading dots are
> not allowed). For the benefit of users of the DJGPP port of GDB, I
> suggest to allow an additional name, `_debug', as a substitute. Thus,
> conditioned on __MSDOS__, GDB would look for `_debug' subdirectory if
> `.debug' does not exist.
I'm reluctant to put #if __MSDOS__ in there directly. Would it be
appropriate to #define something in xm-go32.h, which could be given a
default value of ".debug" in symfile.c?
> > diff -u -r1.131 gdb.texinfo
> > --- gdb/doc/gdb.texinfo 11 Oct 2002 16:13:15 -0000 1.131
> > +++ gdb/doc/gdb.texinfo 26 Nov 2002 03:42:46 -0000
>
> The doco patch is approved, but please add at least one index entry that
> leads to this information. Something like
>
> @cindex separate debug info file
>
> sounds appropriate.
Of course --- thanks for pointing out that omission.
next prev parent reply other threads:[~2002-12-10 3:16 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 [this message]
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
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=vt27keid1kl.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=eliz@is.elta.co.il \
--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