This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/20363] New: syscall return probes should provide a richer retstr
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 13 Jul 2016 00:10:02 +0000
- Subject: [Bug tapsets/20363] New: syscall return probes should provide a richer retstr
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20363
Bug ID: 20363
Summary: syscall return probes should provide a richer retstr
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
Target Milestone: ---
The result of most system calls is just a simple return value, and our
tapset-provided retstr=return_str(...) is sufficient.
Some system calls have additional data to return, and it would be nice to have
a uniform way to show this too. A sys_read will have written some data in the
buffer, a sys_ptrace may have extra data depending on the sort of PTRACE_FOO
request, etc. And these only apply when the primary return value was not an
error.
It would be nice if this were added to ALL syscalls, even if they have nothing
extra to show, so one could write something like:
probe syscall.*.return { printf("%s = %s\n", name, detailed_retstr) }
--
You are receiving this mail because:
You are the assignee for the bug.