This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug releng/6491] need runtime-analysis tool to extend blacklist
- From: "mhiramat at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 7 May 2008 21:27:31 -0000
- Subject: [Bug releng/6491] need runtime-analysis tool to extend blacklist
- References: <20080507205137.6491.fche@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mhiramat at redhat dot com 2008-05-07 21:27 -------
(In reply to comment #0)
> As seen in bug #6487, new kernel-side code called indirectly from probe handlers
> via the runtime can cause deadlocks and whatnot. It may be nice to have a script
> that searches the external-reference/undefined-symbol chain starting from the
> systemtap probe module, and a kernel build tree (individual compilation unit .o
> files). If only it could follow the undefined reference chain on a per-function
> basis, the transitive closure could give us a pretty good blacklist suggestions.
Some functions called from probe 'module' may be safe. I think only functions
called from probe 'handlers' will cause problems.
> (given an unresolved external function, find object file that defines it,
> "objdump -dr" it to find the functions that it calls, then recurse).
cscope will help you trace call graph.
Thanks,
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6491
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.