From: Elena Zannoni <ezannoni@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: support debug info in separate files
Date: Mon, 09 Dec 2002 22:13:00 -0000 [thread overview]
Message-ID: <15861.29951.564644.347349@localhost.redhat.com> (raw)
In-Reply-To: <vt2znrxt1k2.fsf@zenia.red-bean.com>
Jim Blandy writes:
>
> 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. This
> allows a distribution to provide debug info in separate packages from
> the executables it describes.
>
Actually thinking about this, where can one get a copy of elfutils?
Could the same functionality be added to binutils?
> If you've got all the previous patches I've posted (and if I haven't
> botched anything), this should cause no test suite regressions, and
> the results of running the test suite both with and without separated
> debug info are identical. Starting with current GDB sources, the
> other patches you need are:
>
> RFA: testsuite: pass optimization flag in the proper way
> RFA: testsuite: attach.exp: don't move executables to /tmp
> Re: RFC: allow syms_from_objfile to take a section offset table directly
> RFC: Allow symbol_file_add to take section_offsets table
>
> To run the GDB test suite against executables with separated debug info,
> see: http://sources.redhat.com/ml/gdb/2002-11/msg00202.html
> and: http://sources.redhat.com/ml/gdb/2002-11/msg00215.html
>
> (Note: there is a bug in the elfutils strip that causes some stripped
> executables to crash. This has been fixed only very recently, so
> you'll need a bleeding-edge version of elfutils, or else you'll get
> failures in try_catch.exp due to the inferior crashing.)
>
> If folks don't have concerns about this, I'll commit it on Fri Dec 6.
>
Some random comments...
This works only for Elf. Will this interfere when other file formats
are processed? (I haven't tried with a, say, coff file, which is
impossible of course because this is elfutils based).
> * utils.c (calc_crc32): New function.
> * defs.h (calc_crc32): New declaration.
Now we have 4 identical crc32's functions in gdb. Any chance to
delete a few?
For the debug file name suggest looking at HAVE_DOS_BASED_FILE_SYSTEM
in libiberty, and its uses in gdb/source.c.
[...]
> + strcat (debugfile, ".debug/");
[...]
> + strcat (debugfile, "/");
[...]
> + strcat (debugfile, "/");
Should these be DIR_SEPARATOR instead? I guess DJGPP doesn't care though.
In this message,
http://sources.redhat.com/ml/gdb/2002-09/msg00312.html I pointed out a
few things that could be done to improve this patch. For instance,
instead of adding a completely new objfile that would be only for the
debug info, add the debug info to the existing objfiles. I haven't
had a chance to see if you changed the patch to do something different
or not. It also seemed at that stage that we were gaining an extra
copy of the minimal symbols, and this can bloat gdb even more. Was
this changed?
Other comments I pointed out in that message have been addressed by
Alex already.
Elena
next prev parent reply other threads:[~2002-12-10 6:05 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 [this message]
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=15861.29951.564644.347349@localhost.redhat.com \
--to=ezannoni@redhat.com \
--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