This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/20333] merge syscall and nd_syscall tapsets
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 07 Jul 2016 18:00:04 +0000
- Subject: [Bug tapsets/20333] merge syscall and nd_syscall tapsets
- Auto-submitted: auto-generated
- References: <bug-20333-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20333
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #2 from Josh Stone <jistone at redhat dot com> ---
(In reply to David Smith from comment #0)
> - If you have debuginfo installed, there really isn't a way to specify you
> want the non-debuginfo version of the probe. (Although why you'd really want
> to do that I'm not so sure). The above code prefers the debuginfo version.
I doubt end-users should ever need to force non-debuginfo, but we'll want to do
this for testing at least. Setting an invalid SYSTEMTAP_DEBUGINFO_PATH should
suffice.
> - Perhaps the biggest problem with this idea is how users actually use
> syscall probes. I've seen user code (and I believe some of our examples) use
> a syscall probe, but then also use the 'raw' $FOO variables, which certainly
> wouldn't work correctly if no debuginfo was installed.
If it weren't for this point, I would have suggested we just ditch the
debuginfo flavor altogether. But at least having the two share the same probe
body will make the doubled-maintenance more obvious, and make it easier to stay
consistent.
--
You are receiving this mail because:
You are the assignee for the bug.