From: Eugeniy Meshcheryakov <eugen@debian.org>
To: James Y Knight <foom@fuhm.net>
Cc: systemtap@sourceware.org
Subject: Re: Troubles with debug info, using systemtap on debian.
Date: Wed, 11 Nov 2009 09:50:00 -0000 [thread overview]
Message-ID: <20091111095025.GA9619@localhost.localdomain> (raw)
In-Reply-To: <20091111094104.GA6320@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
11 листопада 2009 о 10:41 +0100 Eugeniy Meshcheryakov написав(-ла):
> Hello,
>
> 10 листопада 2009 о 13:38 -0500 James Y Knight написав(-ла):
> > Unless something *further* strange is going on in my environment,
> > anyone should be able to reproduce by:
> > 1) removing the symlink to your kernel build dir (rm /lib/modules/
> > $VERS/build): renaming is not enough, systemtap still finds it!
> > 2) ensuring that the debug info in /usr/lib/debug is stripped of
> > code with objcopy --only-keep-debug.
> > 3) ensuring the kernel modules in /lib/modules/$VERS are stripped of
> > debug info.
> This does not work at all. With DWARF probes stap does not find debug
> info (and does not segfault). With dwarfless probes stap still requires
> build directory (I guess to build module?) and does not segfault.
>
I tried to symlink snd.ko to snd.ko.debug and can reproduce the bug now.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-11-11 9:50 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
2009-11-10 18:38 ` James Y Knight
2009-11-11 9:41 ` Eugeniy Meshcheryakov
2009-11-11 9:50 ` Eugeniy Meshcheryakov [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=20091111095025.GA9619@localhost.localdomain \
--to=eugen@debian.org \
--cc=foom@fuhm.net \
--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).