This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/20618] New: Cannot get the real syscall return code value
- From: "mysecondaccountabc at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 19 Sep 2016 02:56:42 +0000
- Subject: [Bug tapsets/20618] New: Cannot get the real syscall return code value
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20618
Bug ID: 20618
Summary: Cannot get the real syscall return code value
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: mysecondaccountabc at gmail dot com
Target Milestone: ---
We need to get the syscall return value and the errno separately. However, when
for instance, the connect syscall is executed in a non-blocking socket and it
returns -1 and errno=115 (EINPROGRESS) all we get in a "probe syscall.*.return"
is:
returnval() = -115
retstr = "-115 (EINPROGRESS)"
We couldn't find in any part of the documentation that returnval() or the
syscall return value will be replaced with the errno value, so I wonder if it's
a bug or in any case, how can we get/recover the original syscall return code?
--
You are receiving this mail because:
You are the assignee for the bug.