[Bug translator/14738] New: Stop overuse of _stp_error for warning conditions

["fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=14738

             Bug #: 14738
           Summary: Stop overuse of _stp_error for warning conditions
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap@sourceware.org
        ReportedBy: fche@redhat.com
    Classification: Unclassified


It is not unusual for some probe types (massive uprobes or kprobes) to suffer
partial failures in the form of registration errors.  The user is often
notified of these errors with an _stp_error ("... registration error ...") type
message, which results in staprun exiting with a failing rc.  In fact, these
are not errors in the overall sense, since the systemtap probing session went
on without them.  They should just have been _stp_warn's.

(The runtime is also implicated.  e.g. uprobes registration warnings can bubble
up as mmap-callback failures, which also go through _stp_error.)

The gist is that if we use _stp_error, it should be for cases that are going to
shut down the systemtap session pretty quickly, not for cases that permit its
continuation.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.