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, master, updated. release-0.9.7-10-gb637139
- From: jistone at sourceware dot org
- To: systemtap-cvs at sourceware dot org
- Date: 25 Apr 2009 03:11:33 -0000
- Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.7-10-gb637139
- 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, master has been updated
via b6371390a999711146084ed6377a64e4c9480d83 (commit)
via c8d9d15e8d696f556fd27ae43db12552bcc63512 (commit)
via 46856d8d04167a05b62f8d3a480b2be7509fcf86 (commit)
via 5badd4d0d1fc3f7dce2dc26a3ad5a69275ff07d2 (commit)
from 8f497c23fd73345bd73b085a853f9c8be548715c (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit b6371390a999711146084ed6377a64e4c9480d83
Author: Josh Stone <jistone@redhat.com>
Date: Fri Apr 24 20:06:58 2009 -0700
Enable kprobe.function.return.maxactive
The code to emit maxactive was almost there; it just needed to enable
the maxactive probe component and pass the value down.
commit c8d9d15e8d696f556fd27ae43db12552bcc63512
Author: Josh Stone <jistone@redhat.com>
Date: Fri Apr 24 19:30:59 2009 -0700
Simplify dwarfless kprobe stmt vs. name logic
commit 46856d8d04167a05b62f8d3a480b2be7509fcf86
Author: Josh Stone <jistone@redhat.com>
Date: Fri Apr 24 18:37:35 2009 -0700
Fill out the pp() for dwarfless kprobes
commit 5badd4d0d1fc3f7dce2dc26a3ad5a69275ff07d2
Author: Josh Stone <jistone@redhat.com>
Date: Fri Apr 24 18:07:12 2009 -0700
Don't terminate when a dwarfless kprobe fails
All of our other kprobe types will let the script continue after a
registration failure, as per PR6749. The dwarfless kprobes should be
no exception.
Also, the way they were exiting was causing an unclean shutdown, so I
added tests to badkprobe.exp to make sure that cleanup is always allowed
to run.
-----------------------------------------------------------------------
Summary of changes:
tapsets.cxx | 165 ++++++++++++++++++--------------
testsuite/systemtap.base/badkprobe.exp | 32 +++++--
2 files changed, 117 insertions(+), 80 deletions(-)
hooks/post-receive
--
systemtap: system-wide probe/trace tool