This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/18642] Probes not always invoked when probed functions are called
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 24 May 2016 15:29:06 +0000
- Subject: [Bug runtime/18642] Probes not always invoked when probed functions are called
- Auto-submitted: auto-generated
- References: <bug-18642-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18642
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |fche at redhat dot com
Resolution|--- |WORKSFORME
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
Testing your first scenario, I don't see a mismatch:
# stap -e 'probe process.syscall, nd_syscall.* {
if (pid() == target()) println(pp())
}' -c /bin/PROGRAM
Hypothetical mismatches could occur because of the different underlying probing
mechanisms (kprobes versus tracepoints), which can incur temporary failures in
different ways. (Use "stap -t" for more precise accounting of skipped probes.)
The second part of your report seems similar to bug #19812, which interfered
with intra-container targeted user-space probing. It was fixed in systemtap
3.0.
--
You are receiving this mail because:
You are the assignee for the bug.