Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Aleksandar Ristovski <aristovski@qnx.com>, gdb@sources.redhat.com
Subject: Re: working with split debug files and sectionless ELFs
Date: Fri, 14 Oct 2011 17:29:00 -0000	[thread overview]
Message-ID: <20111014172508.GA4939@host1.jankratochvil.net> (raw)
In-Reply-To: <201110141305.47508.vapier@gentoo.org>

On Fri, 14 Oct 2011 19:05:46 +0200, Mike Frysinger wrote:
> build-id is a section. my ELF has no sections.  i'm back where i started :).

build-id is in a note being both a section and a segment.  GDB currently reads
it as a section but this can be changed.

Program Headers:
  Type           Offset   VirtAddr           PhysAddr           FileSiz  MemSiz   Flg Align
[...]
  NOTE           0x000254 0x0000000000400254 0x0000000000400254 0x000044 0x000044 R   0x4
[...]
Notes at offset 0x00000274 with length 0x00000024:
  Owner         Data size       Description
  GNU           0x00000014      NT_GNU_BUILD_ID (unique build ID bitstring)

It was designed by Roland McGrath exactly this way so that in all cases of
debug info stripping build-id remains in the main executable.  Otherwise
build-id would be useless.


Thanks,
Jan


  reply	other threads:[~2011-10-14 17:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 17:36 Mike Frysinger
2011-10-14 14:23 ` Aleksandar Ristovski
2011-10-14 15:37   ` Mike Frysinger
2011-10-14 15:27     ` Mike Frysinger
2011-10-14 15:42     ` Aleksandar Ristovski
2011-10-14 16:00       ` Jan Kratochvil
2011-10-14 16:47         ` Jan Kratochvil
2011-10-14 17:08           ` Mike Frysinger
2011-10-14 17:29             ` Jan Kratochvil [this message]
2011-10-15  5:28               ` Mike Frysinger
2011-10-14 17:20         ` Mike Frysinger
2011-10-14 17:31           ` Jan Kratochvil
2011-10-14 17:34           ` Aleksandar Ristovski

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=20111014172508.GA4939@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=aristovski@qnx.com \
    --cc=gdb@sources.redhat.com \
    --cc=vapier@gentoo.org \
    /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