From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [repost] Re: RFC: support debug info in separate files
Date: Thu, 23 Jan 2003 23:04:00 -0000 [thread overview]
Message-ID: <vt2of67tqxr.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <vt2el89xf85.fsf@zenia.red-bean.com>
I've committed this patch, after making the changes to the
documentation that Eli suggested. I'll take care of the maint.exp
regressions in a bit.
Jim Blandy <jimb@redhat.com> writes:
> [My previous post omitted the patch to acconfig.h.]
>
> Here's a new shot at the separate debug patch. It's updated to apply
> to the current branch, and I believe I've addressed the comments folks
> have made:
> - The documentation has been completely rewritten, and provides much
> more detail. It includes all the information needed to implement
> `strip -f' in the GNU binutils, for example. It is better indexed.
> - The name ".debug" can be overridden by xm- files for systems that
> can't handle names like that.
> - The CRC function has a more descriptive name.
>
> Using separate debug info does introduce three new test suite
> failures:
> FAIL: gdb.base/maint.exp: maint print objfiles: psymtabs
> FAIL: gdb.base/maint.exp: maint print objfiles: symtabs
> FAIL: gdb.base/maint.exp: maint print msymbols
>
> These do not reflect GDB misbehavior: the objfile in question has no
> psymtabs, symtabs, or msymbols, but the test suite assumes they
> should. I think 'maint print objfiles' should print something
> indicating when an objfile has an associated separated debug file, and
> that the test should recognize and cope with this, but it seems like
> that should be a separate patch.
>
> Before you can apply this patch, you'll need to apply the following:
>
> Re: RFC: allow syms_from_objfile to take a section offset table directly
> http://sources.redhat.com/ml/gdb-patches/2002-12/msg00627.html
>
> RFC: Allow symbol_file_add to take section_offsets table
> http://sources.redhat.com/ml/gdb-patches/2002-11/msg00634.html
>
> gdb/ChangeLog:
> 2002-12-23 Alexander Larsson <alexl@redhat.com>
> Jim Blandy <jimb@redhat.com>
>
> Add support for executables whose debug info has been separated
> out into a separate file, leaving only a link behind.
> * objfiles.h (struct objfile): New fields: separate_debug_objfile
> and separate_debug_objfile_backlink.
> (put_objfile_before): New declaration.
> * symfile.c: #include "filenames.h".
> (symbol_file_add_with_addrs_or_offsets): If this objfile has its
> debug info in a separate file, read that, too. Save the addrs
> argument, so we can use it again to read the separated debug info;
> syms_from_objfile modifies the table we pass it.
> (reread_symbols): After re-reading an objfile, call
> reread_separate_symbols to refresh its separate debug info
> objfile, if it has one.
> (reread_separate_symbols, find_separate_debug_file,
> get_debug_link_info, separate_debug_file_exists): New functions.
> (debug_file_directory): New global var.
> (_initialize_symfile): Initialize debug_file_directory, and
> provide the new `set debug-file-directory' command to let the user
> change it.
> * objfiles.c (free_objfile): If this objfile has its debug info in
> a separate objfile, free that one too. If this is itself a
> separate debug info objfile, clear our parent's backlink.
> (put_objfile_before): New function.
> * utils.c (gnu_debuglink_crc32): New function.
> * defs.h (gnu_debuglink_crc32): New declaration.
> * Makefile.in (symfile.o): Note dependency on "filenames.h".
> * configure.in: Handle --with-separate-debug-dir config option.
> * acinclude.m4 (AC_DEFINE_DIR): New macro.
> * acconfig.h (DEBUGDIR): New macro.
> * configure, aclocal.m4, config.in: Regenerated.
>
> gdb/doc/ChangeLog:
> 2002-12-23 Jim Blandy <jimb@redhat.com>
>
> * gdb.texinfo (Separate Debug Files): New section.
prev parent reply other threads:[~2003-01-23 23:04 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
2003-01-23 23:04 ` Jim Blandy [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=vt2of67tqxr.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--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