This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/11641] FAIL: fib (19 1) backtrace from uretprobe fails
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 3 Jun 2010 11:16:49 -0000
- Subject: [Bug runtime/11641] FAIL: fib (19 1) backtrace from uretprobe fails
- References: <20100528110745.11641.mjw@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mjw at redhat dot com 2010-06-03 11:16 -------
(In reply to comment #0)
> testsuite/systemtap.context/fib.exp tests a recursive Fibonacci program
> backtrace on function entry (which PASSes) and on return (which FAILs).
>
> This used to work some time ago, but I have not yet found what broke this test.
This is still the case.
> What is worse is that it seemed to crash my machine while trying to investigate
> the cause. But I have been unable to trigger that reliably :{
That part was related to the kernel I was running. And was fixed by:
commit c265cd259a82542abf290a6aeb058056d6c18b73
Author: Mark Wielaard <mjw@redhat.com>
Date: Thu Jun 3 11:26:17 2010 +0200
Replace walk_stack field version guard with autoconf test.
The test for whether or not to assign print_context_stack to the
walk_stack stacktrace_ops field depended on the kernel version.
Replace with a proper runtime/autoconf test to make sure the field
always gets assigned when available.
* buildrun.cxx (compile_pass): Add output for STAP_CONF_WALK_STACK.
* runtime/autoconf-walk-stack.c: New test.
* runtime/stack.c (print_stack_ops): Assign walk_stack field
print_context_stack depending on STAP_CONF_WALK_STACK.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11641
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.