This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/12729] stap error message needs improvement
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 7 Jun 2011 18:35:30 +0000
- Subject: [Bug translator/12729] stap error message needs improvement
- Auto-submitted: auto-generated
- References: <bug-12729-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12729
--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> 2011-06-07 18:34:43 UTC ---
Unfortunately posix_spawnp() does not appear to give us -EPERM or
such detailed execve errors; it returns such errors instead with the
exit-status-127 catch-all that systemtap does print out (with stap -vv).
We could change remote.cxx users of stap_spawn / make_run_command()
to report that we had a problem launching staprun, like class
ssh_legacy_remote() does.
Or maybe util.cxx stap_spawn itself should print an error unconditionally upon
a failure. (Are there any cases where stap_spawn's failure is supposed
to be an acceptable situation?)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.