This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/13404] DTRACE_PROBE for more that 10 arguments needed
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Sat, 12 Nov 2011 22:11:14 +0000
- Subject: [Bug uprobes/13404] DTRACE_PROBE for more that 10 arguments needed
- Auto-submitted: auto-generated
- References: <bug-13404-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13404
--- Comment #7 from Mark Wielaard <mjw at redhat dot com> 2011-11-12 22:11:14 UTC ---
Josh fixed this:
commit 88e39987df7109b26343c9c33567646873d6f829
Author: Josh Stone <jistone@redhat.com>
Date: Fri Nov 11 11:11:11 2011 -1100
PR13404: Dial SDT args up to twelve
This is SystÃmTap, and eleven is so 1984...
* includes/sys/sdt.h: Expand all macros from 10 to 12.
* tapsets.cxx (sdt_uprobe_var_expanding_visitor): Allow 12 args now.
* testsuite/systemtap.base/sdt.*: Test 12 args for SDT v3 only.
* testsuite/systemtap.base/sdt_va_args.*: Test 12 in STAP_PROBEV.
If you could test this against the Erlang DTRACE support that would be great.
If you don't want to build a new systemtap you should be able to just replace
sys/sdt.h with the latest one from git:
http://sourceware.org/git/?p=systemtap.git;a=blob_plain;f=includes/sys/sdt.h;hb=HEAD
Please do reopen or file a new bug if there is still a problem.
BTW. 11 arguments is really a lot of information for one probe. Maybe you could
look into more splitting some of them up into more fine grained probes (for
example specific ones for each command in this case).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.