This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
print_backtrace() problem
- From: Peter Teoh <htmldeveloper at gmail dot com>
- To: SystemTAP <systemtap at sources dot redhat dot com>
- Date: Fri, 16 Jan 2009 11:24:44 +0800
- Subject: print_backtrace() problem
Why is it that when I call print_backtrace() inside stp script, it
only give me a short stacktrace:
====>ext2_readdir
0xf7e1e97f : ext2_readdir+0x1/0x2d7 [ext2]
====>ext2_get_page
0xf7e1e33d : ext2_get_page+0x1/0x22d [ext2]
<====ext2_get_page
Returning from: 0xf7e1e33c : ext2_get_page+0x0/0x22d [ext2]
Returning to : 0xf7e1eae7 : ext2_readdir+0x169/0x2d7 [ext2]
whereas when I inserted a dump_stack() call inside my ext2_readdir() I
got a much longer stacktrace:
Jan 16 00:28:46 localhost kernel: Call Trace:
Jan 16 00:28:46 localhost kernel: [<f8a2e9f2>] ext2_readdir+0x74/0x2ed [ext2]
Jan 16 00:28:46 localhost kernel: [<c04a3748>] ? filldir64+0x0/0xd2
Jan 16 00:28:46 localhost kernel: [<c04ab7e8>] ? mnt_drop_write+0x22/0xbd
Jan 16 00:28:46 localhost kernel: [<c04a394f>] vfs_readdir+0x68/0x94
Jan 16 00:28:46 localhost kernel: [<c04a3748>] ? filldir64+0x0/0xd2
Jan 16 00:28:47 localhost kernel: [<c04a39de>] sys_getdents64+0x63/0xa4
Jan 16 00:28:47 localhost kernel: [<c0403245>] sysenter_do_call+0x12/0x26
I suspect something wrong with the .config:
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_INFO=y
CONFIG_FRAME_POINTER=y
CONFIG_KPROBES=y
CONFIG_HAVE_KPROBES=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_MARKERS=y
CONFIG_OPROFILE=m
CONFIG_HAVE_OPROFILE=y
CONFIG_RELAY=y
CONFIG_STACKTRACE_SUPPORT=y
Is that correct?
Thanks for the help.
--
Regards,
Peter Teoh