printing kernel backtrace

Frank Ch. Eigler fche@redhat.com
Sat Dec 12 16:01:00 GMT 2015


Hi -

> [...]
> So using -d kernel does indeed fix the backtrace. 

Good; will see if can add some diagnostics.

> For the sake of completeness I also tried using --ldd which
> according to the help should include debug info for all referenced
> objects (including the kernel) but it doesn't work.

A documentation glitch: --ldd is for shared library dependencies,
so not including the kernel, will fix.

- FChE



More information about the Systemtap mailing list