From: Martin Langhoff <martin.langhoff@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: John Gilmore <gnu@toad.com>, gdb@sourceware.org
Subject: Re: Reading dynamic symbols from Linux core files?
Date: Fri, 16 Mar 2012 19:57:00 -0000 [thread overview]
Message-ID: <CACPiFCK6F0tAuEwrBv8eaHFn-qEvoFWA-YBeSdhrhwxD5Mokyw@mail.gmail.com> (raw)
In-Reply-To: <20120316184831.GA32437@host2.jankratochvil.net>
On Fri, Mar 16, 2012 at 2:48 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> The problem usually was - at least in some Fedoras + RHELs - that vDSO has
> overgrown 4KB. The loadable segment remained in the first 4KB part but
> debugging symbols spanned more pages which led to bfd_from_remote_memory
> cutting off the debug symbols. Recent Fedora patch for it is:
> http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-6.6-bfd-vdso8k.patch;hb=master
So we're SOL?
BTW, thanks Jan and John for taking this upstream with a background
knowledge I can't match!
One thing to note is that we cannot entirely rule out some binaries
being corrupt. This problem has already crossed several "that's
impossible" boundaries. One of our avenues of investigation is an SD
card duplicator introducing some odd fs corruption, although rpm -Va
and other checksums tell us the files are good.
Also - http://lists.fedoraproject.org/pipermail/devel/2012-March/164105.html
m
--
martin.langhoff@gmail.com
martin@laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
prev parent reply other threads:[~2012-03-16 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 18:39 John Gilmore
2012-03-16 18:48 ` Jan Kratochvil
2012-03-16 19:57 ` Martin Langhoff [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=CACPiFCK6F0tAuEwrBv8eaHFn-qEvoFWA-YBeSdhrhwxD5Mokyw@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--cc=jan.kratochvil@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