public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luto at mit dot edu" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17064] New: gdb's can't find Linux 3.16-rc1's vdso build-id
Date: Tue, 17 Jun 2014 22:53:00 -0000 [thread overview]
Message-ID: <bug-17064-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17064
Bug ID: 17064
Summary: gdb's can't find Linux 3.16-rc1's vdso build-id
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: luto at mit dot edu
In Linux 3.16-rc1, the vdso is more heavily stripped than it is in prior
versions. It has no section table*. Nonetheless, gdb should still be able to
find its build-id, because its PT_NOTE phdr is in perfect order. eu-readelf -n
works, but readelf -n does not.
(Actually, there's a complication: due to a workaround for a bug in Go, the
64-bit vdso currently has a fake section header that does not contain a note
section. This causes even elfutils to be unable to find the ELF notes. If
necessary, I can change that.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-06-17 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 22:53 luto at mit dot edu [this message]
2014-06-18 3:42 ` [Bug symtab/17064] " luto at mit dot edu
2014-06-18 7:22 ` nickc at redhat dot com
2014-06-18 10:23 ` palves at redhat dot com
2014-06-18 14:53 ` luto at mit dot edu
2014-06-18 14:55 ` luto at mit dot edu
2014-06-18 14:58 ` palves at redhat dot com
2014-06-18 15:01 ` luto at mit dot edu
2014-06-18 15:19 ` palves at redhat dot com
2014-06-18 15:29 ` luto at mit dot edu
2014-06-18 15:37 ` palves at redhat dot com
2014-06-18 19:56 ` luto at mit dot edu
2014-06-19 13:13 ` nickc at redhat dot com
2014-06-19 13:16 ` nickc at redhat dot com
2014-06-19 14:48 ` luto at mit dot edu
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=bug-17064-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).