From: nick clifton <nickc@redhat.com>
To: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Cc: binutils@sourceware.org
Subject: Re: [PATCH] fix PR symtab/15597
Date: Wed, 14 Aug 2013 11:25:00 -0000 [thread overview]
Message-ID: <520B689A.6030908@redhat.com> (raw)
In-Reply-To: <1375983426-19308-1-git-send-email-tromey@redhat.com>
Hi Tom,
> This patch touches BFD. Previously, gdb had its own code for parsing
> .gnu_debugaltlink; I changed it to use the BFD functions after those
> were introduced. However, the BFD functions are incorrect -- they
> assume that .gnu_debugaltlink is formatted like .gnu_debuglink.
> However, it it is not. Instead, it consists of a file name followed
> by the build-id -- no alignment, and the build-id is not a CRC.
>
> Fixing this properly is a bit of a pain. But, because
> separate_alt_debug_file_exists just has a FIXME for the build-id case,
> I did not fix it properly. Instead I introduced a hack. This leaves
> BFD working just as well as it did before my patch.
>
> I'm willing to do something better here but I could use some guidance
> as to what. It seems that the build-id code in BFD is largely punted
> on.
True - it would be nice to see this fixed, but it can be left for a
future patch.
> * bfd-in2.h: Rebuild.
> * opncls.c (bfd_get_alt_debug_link_info): Add buildid_len
> parameter. Change type of buildid_out. Update.
> (get_alt_debug_link_info_shim): New function.
> (bfd_follow_gnu_debuglink): Use it.
>
> * Makefile.in (SFILES): Add build-id.c.
> (HFILES_NO_SRCDIR): Add build-id.h.
> * build-id.c: New file, largely from elfread.c. Modified
> most functions.
> * build-id.h: New file.
> * dwarf2read.c (dwarf2_get_dwz_file): Update for change to
> bfd_get_alt_debug_link_info. Verify dwz file's build-id.
> Search for dwz file using build-id.
> * elfread.c (build_id_bfd_get, build_id_verify)
> (build_id_to_debug_filename, find_separate_debug_file): Remove.
>
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2013-08-14 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 17:37 Tom Tromey
2013-08-10 5:36 ` Alan Modra
2013-08-12 8:41 ` Tom Tromey
2013-08-12 9:29 ` Alan Modra
2013-08-14 11:25 ` nick clifton [this message]
2013-10-08 19:38 ` Tom Tromey
2013-10-08 22:10 ` Hans-Peter Nilsson
2013-10-09 1:27 ` Tom Tromey
2013-10-09 14:09 ` Tom Tromey
2013-10-09 14:54 ` Build regression on 32-bit hosts [Re: [PATCH] fix PR symtab/15597] Jan Kratochvil
2013-10-09 15:46 ` Tom Tromey
2013-10-10 0:17 ` [PATCH] fix PR symtab/15597 Doug Evans
2013-10-10 2:29 ` Tom Tromey
2013-10-10 19:04 ` Doug Evans
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=520B689A.6030908@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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