This is the mail archive of the
systemtap-cvs@sourceware.org
mailing list for the systemtap project.
[SCM] systemtap: system-wide probe/trace tool branch, mjw/backtrace, created. release-1.5-160-g61d152d
- From: mark at sourceware dot org
- To: systemtap-cvs at sourceware dot org
- Date: 22 Jul 2011 10:01:09 -0000
- Subject: [SCM] systemtap: system-wide probe/trace tool branch, mjw/backtrace, created. release-1.5-160-g61d152d
- Reply-to: systemtap at sourceware dot org
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".
The branch, mjw/backtrace has been created
at 61d152dcd195d745a57c73c8f26d99eef255b172 (commit)
- Log -----------------------------------------------------------------
commit 61d152dcd195d745a57c73c8f26d99eef255b172
Author: Mark Wielaard <mjw@redhat.com>
Date: Fri Jul 22 11:51:41 2011 +0200
Remove stack-x64x.c specific fallback for _stp_stack_print_fallback().
If the standard kernel based _stp_stack_print_fallback() isn't available
don't try to be smart and guess at stack addresses ourselves. Just give
up. Dwarf based unwinding is good enough now and the kernel dump_stack()
does a much better job than we can at guessing stack values.
commit 7e46daf103bea7dcc92e255629e8412e8f608215
Author: Mark Wielaard <mjw@redhat.com>
Date: Thu Jul 21 16:51:48 2011 +0200
Remove STP_USE_FRAME_POINTER support and merge i386/x86_64 into stack-x86.c
The only real difference between stack-i386.c and stack-x86_64 was that
the former supported a buggy frame pointer based unwind. Which we never
used and for which the kernel has a better fallback (dump_trace).
-----------------------------------------------------------------------
hooks/post-receive
--
systemtap: system-wide probe/trace tool