From: James Y Knight <foom@fuhm.net>
To: Frank Ch. Eigler <fche@redhat.com>
Cc: Eugeniy Meshcheryakov <eugen@debian.org>, systemtap@sourceware.org
Subject: Re: Troubles with debug info, using systemtap on debian.
Date: Tue, 10 Nov 2009 18:24:00 -0000 [thread overview]
Message-ID: <09848B55-4B13-4652-B493-AADB8B31C77C@fuhm.net> (raw)
In-Reply-To: <y0mtyx2p82e.fsf@fche.csb>
On Nov 10, 2009, at 1:07 PM, Frank Ch. Eigler wrote:
> Eugeniy Meshcheryakov <eugen@debian.org> writes:
>
>> [...]
>>> 3) The debian kernel's debuginfo does "objcopy --only-keep-
>>> debug"...That seems like it shouldn't cause systemtap to blow up,
>>> but it does. I guess that's a known bug? [...]
>>> 5) Whose bug is it that systemtap doesn't look for
>>> /usr/lib/debug/.../autofs4.ko, but only autofs4.ko.debug?
>>> [...]
>
> The issue here is that elfutils looks for .ko.debug files, if the
> original .ko was stripped of debug data. The fedora naming convention
> communicates the fact that the separated .ko.debug files are not
> .ko's, in that they lack executable .text/.data/etc. payload.
>
> Some distributions don't strip the debug data the same way as fedora,
> but instead preserve the original unstripped binaries under
> /usr/lib/debug or similar. In this case, since the original files are
> complete, it makes sense not to rename them "anything.debug", but OTOH
> then elfutils must break the tie between that copy and an identically
> named stripped one.
Debian preserves only the debug info in /usr/lib/debug, with objcopy --
only-keep-debug. So, the files are generally not complete. But, they
are named "anything", not "anything.debug".
James
next prev parent reply other threads:[~2009-11-10 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 1:18 James Y Knight
2009-11-10 9:35 ` Eugeniy Meshcheryakov
2009-11-10 10:19 ` Eugeniy Meshcheryakov
2009-11-10 18:07 ` Frank Ch. Eigler
2009-11-10 18:24 ` James Y Knight [this message]
2009-11-10 18:38 ` James Y Knight
2009-11-11 9:41 ` Eugeniy Meshcheryakov
2009-11-11 9:50 ` Eugeniy Meshcheryakov
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=09848B55-4B13-4652-B493-AADB8B31C77C@fuhm.net \
--to=foom@fuhm.net \
--cc=eugen@debian.org \
--cc=fche@redhat.com \
--cc=systemtap@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).