This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: full dwarf backtracing kernel to user
- From: amouehsan <moussa dot ehsan at gmail dot com>
- To: systemtap at sourceware dot org
- Date: Mon, 1 Aug 2011 15:15:46 -0700 (PDT)
- Subject: Re: full dwarf backtracing kernel to user
- References: <1310384101.3241.54.camel@springer.wildebeest.org>
Hi,
I am trying systemtap and when probing a kernel function ("bio_endio") I
need to get the user backtrace. When I use
probe kernel.function("bio_endio@fs/bio.c:1443").call
{
print_ubacktrace();
}
I get the following message.
<no ubacktrace: kernel.function("bio_endio@fs/bio.c:1443").call>
I tried using --ldd but it didn't help. By what you have written:
Mark Wielaard-4 wrote:
>
> I have been cleaning up the dwarf unwinder a bit, and after some small
> fixes (all in git trunk now) it is now finally possible to unwind fully
> from kernel space right into user space. This provides better user
> backtraces when a probe point triggered in kernel space.
>
> With the new setup it is now possible to get a
> full user space register set to start the user space dwarf unwinder and
> always do a full unwind. One example is setting a probe point on
> syscall.close and then doing a print_ubacktrace().
>
I understand the feature I wanted to use was not implemented before. Is my
understanding right? If no, how can I do that? If yes, how I can have this
new feature enabled? Should I get a new code and re-compile systemtap?
Thanks,
--
View this message in context: http://old.nabble.com/full-dwarf-backtracing-kernel-to-user-tp32036694p32173616.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.