From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10174] Enable stap to map function addresses to function names
Date: Mon, 25 May 2009 16:24:00 -0000 [thread overview]
Message-ID: <20090525162429.17425.qmail@sourceware.org> (raw)
In-Reply-To: <20090520112758.10174.prerna@linux.vnet.ibm.com>
------- Additional Comments From fche at redhat dot com 2009-05-25 16:24 -------
> > Thanks Frank !! This construct doesnt seem to work in dwarfless scenario
>
> You need to add dwarf :)
> stap -d kernel (or stap -d module-name) will make the symbols available by
> reading them from the debuginfo.
Yeah, but that seems to defeat the purpose of dwarfless probing.
Maybe extend -d to accept a (presumed) kernel symbol table file
-d /lib/modules/`uname -r`/build/System.map
And the kprobes.* logic can add this to session.unwindsyms. For
that matter, it could read the file (like in jkenisto's older
symbol-table-based probing implementation) to verify placement
of kernel-side symbol probes.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10174
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-05-25 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 11:28 [Bug translator/10174] New: " prerna at linux dot vnet dot ibm dot com
2009-05-20 11:34 ` [Bug translator/10174] " fche at redhat dot com
2009-05-25 4:54 ` prerna at linux dot vnet dot ibm dot com
2009-05-25 7:25 ` mjw at redhat dot com
2009-05-25 16:24 ` fche at redhat dot com [this message]
2010-08-12 18:11 ` [Bug translator/10174] let stap -d take a symbol table file as argument, for dwarfless *symname() fche at redhat dot com
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=20090525162429.17425.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--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).