This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug documentation/14929] New: staperrors man page
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 07 Dec 2012 14:49:31 +0000
- Subject: [Bug documentation/14929] New: staperrors man page
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14929
Bug #: 14929
Summary: staperrors man page
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: documentation
AssignedTo: systemtap@sourceware.org
ReportedBy: fche@redhat.com
Classification: Unclassified
Often, systemtap errors are too complicated to explain within the stderr
message, and are inconveniently documented only as random tips on the wiki.
Let's collect them in installed staperrors man pages, starting from pages such
as http://sourceware.org/systemtap/wiki/TipContextVariables, explaining some of
the more annoying ones. We could tag error messages that are known specially
documented with a code at the call site. Perhaps something like this:
% stap FOO.stp
semantic error: not accessible at this address (0x2b3e0, dieoffset: 0xaeff1):
identifier '$new' at ./sctp.stap:2:61
elaboration at man 3stap error::context
source: printf("sctp_assoc_update updates asoc peer rwnd to %d\n",
$new->peer->rwnd);
^
% man 3stap error::context
... some tips ...
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.