[Bug translator/12033] New: 'stap -l' needs better error reporting

[dsmith at redhat dot com]

'stap -l' is a bit too silent when it comes to errors.  It makes it quite
difficult to really know what is going on.  (See bug 12032 for another example.)

# stap -l 'kernel.function("X")'

Function "X" doesn't exist, so nothing is reported.  Perhaps a "No probes found"
error message here would be nice.

# stap -l 'module("Y").function("X")'

Nothing is reported here either.  At this point a user doesn't know if:
1) module "Y" couldn't be found; or
2) module "Y" was found but function "X" doesn't exist

The same thing happens as the previous example when static user markers are used:

# stap -l 'process("abc").mark("X")'

Nothing is reported here.  At this point a user doesn't know if:
1) the "abc" executable couldn't be found; or
2) the "abc" executable was found but marker "X" doesn't exist

-- 
           Summary: 'stap -l' needs better error reporting
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: dsmith at redhat dot com


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.