From: Tim Beaulen <tbscope@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: Line numbers reported by pp() do not respond to the reality
Date: Sun, 05 Sep 2010 18:11:00 -0000 [thread overview]
Message-ID: <AANLkTikrUn+-rgJuZG+CLp2ms9BCDs6Lgd31NK-Ah5=_@mail.gmail.com> (raw)
In-Reply-To: <y0mvd6kxrqt.fsf@fche.csb>
sudo stap -p2 ./testpp.stp
...
# probes
process("/home/kdesystemtap/kdeinstall/lib/kde4/plugins/styles/oxygen.so").statement("drawScrollBarSliderControl@/home/kdesystemtap/kde/src/trunk/KDE/kdebase/workspace/kstyles/oxygen/oxygenstyle.cpp:4995")
/* pc=.dynamic+0x92035 */ /* <-
process("/home/kdesystemtap/kdeinstall/lib/kde4/plugins/styles/oxygen.so").statement("drawScrollBarSliderControl@*:*")
*/
...
addr2line -e /home/kdesystemtap/kdeinstall/lib/kde4/plugins/styles/oxygen.so
0x92035
/home/kdesystemtap/kde/src/trunk/KDE/kdebase/workspace/kstyles/oxygen/oxygenstyle.cpp:4995
I also checked with:
readelf --debug-dump=decodedline
/home/kdesystemtap/kdeinstall/lib/kde4/plugins/styles/oxygen.so
When I look up the address in this table, I get the same line number: 4995
I haven't checked with GDB yet but since this is the information in
the debug sections, I don't think GDB will report the correct line
number either.
I compiled everything as usual, I only added the -g compiler option.
next prev parent reply other threads:[~2010-09-05 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 10:09 Tim Beaulen
2010-09-05 13:08 ` Frank Ch. Eigler
2010-09-05 18:11 ` Tim Beaulen [this message]
[not found] ` <AANLkTi=PcchooJZCTkurLpYsWEhGwc=kdsdXmJ=F3bkq@mail.gmail.com>
2010-09-05 18:39 ` Tim Beaulen
2010-09-06 7:59 ` Tim Beaulen
2010-09-06 12:18 ` Frank Ch. Eigler
2010-09-12 8:26 ` Tim Beaulen
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='AANLkTikrUn+-rgJuZG+CLp2ms9BCDs6Lgd31NK-Ah5=_@mail.gmail.com' \
--to=tbscope@gmail.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).