This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/2861] New: user_string fault handling
- From: "hunt at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 28 Jun 2006 16:49:48 -0000
- Subject: [Bug tapsets/2861] New: user_string fault handling
- Reply-to: sourceware-bugzilla at sourceware dot org
Fallout from bug 2637. Now that we have more page faults, we must handle them
gracefully.
Currently when user_string() fails, it sets CONTEXT->last_error, which causes
the script to exit, unless you set MAXERRORS to something high enough. Using
MAXERRORS this way is not appropriate and you end up just always setting it to
something high so your scripts don't terminate, even if they should because they
are dividing by zero or overflowing arrays. Userspace data not always being
available is an expected limitation of our implementation, not an unexpected error.
I think a better solution is to generate a warning and return "<unknown>".
The warning might even be optional.
This has been discussed before with no consensus. Leaving things broken is not
an option. Please document your objections and post alternatives.
--
Summary: user_string fault handling
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P1
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: hunt at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2861
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.