This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [RFC] Crash extension for SystemTap
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: "Discussion list for crash utility usage, maintenance and development" <crash-utility at redhat dot com>
- Cc: Dave Anderson <anderson at redhat dot com>, systemtap at sources dot redhat dot com, yumiko dot sugita dot yf at hitachi dot com
- Date: 02 Jul 2007 15:48:34 -0400
- Subject: Re: [RFC] Crash extension for SystemTap
- References: <46542938.3070502@hitachi.com> <4654E1F4.2030107@hitachi.com> <4655A59E.40102@redhat.com> <467BD175.6050303@hitachi.com>
Satoru MORIYA <satoru.moriya.br@hitachi.com> writes:
> [...] I updated my extension for crash-4.0-4.2. [...]
This module is now built as a part of systemtap. The "staplog.so"
file is installed into $prefix/lib/systemtap, for loading using
crash's "extend" command.
As a part of the import, I took the liberty of renaming it "staplog".
I could not make it print data from a crash session running against
the live kernel [1], so it still needs more work. It would be nice if
it also learned to operate against the plain, non-"-b", tracing
backend.
- FChE
[1]
% stap -b something.stp &
% sudo crash
crash 4.0-4.3
[...]
KERNEL: /usr/lib/debug/lib/modules/2.6.21-1.3194.fc7debug/vmlinux
DUMPFILE: /dev/crash
CPUS: 4
DATE: Mon Jul 2 15:34:21 2007
UPTIME: 20 days, 00:56:36
LOAD AVERAGE: 2.97, 1.62, 1.25
TASKS: 268
NODENAME: super.elastic.org
RELEASE: 2.6.21-1.3194.fc7debug
VERSION: #1 SMP Wed May 23 22:12:03 EDT 2007
MACHINE: x86_64 (2659 Mhz)
MEMORY: 4 GB
[...]
crash> extend ..../staplog.so
..../staplog.so: shared object loaded
crash> staplog stap_96acf0ec9a0b8e844b920b552e0b992a_232
staplog: Failed to find _stp_utt/_stp_chan.
crash>
crash> quit