[Bug tapsets/18143] target_set tapset does not track threads created with clone()

dsmith at redhat dot com sourceware-bugzilla@sourceware.org
Fri Mar 20 17:42:00 GMT 2015


https://sourceware.org/bugzilla/show_bug.cgi?id=18143

--- Comment #8 from David Smith <dsmith at redhat dot com> ---
(In reply to Josh Stone from comment #7)

> Strange that "!" lets these continue -- without those you'll still get the
> "cannot probe pid" error.  It's supposed to mark a probe sufficient,
> skipping any alternates listed, but it appears to be working like the "?"
> optional marker too.  I don't think that's intended -- it's only "optional"
> as long as something else in the chain resolves (or is marked truly "?"
> optional).

The '!' marker means "optional and sufficient", not just "sufficient". Here's
some text from the stapprobes man page:

====
       However, a probe point may be followed by a "?" character, to  indicate  
       that it is optional, and that no error should result if it fails to re-  
       solve.  Optionalness passes down through all levels  of  alias/wildcard  
       expansion.  Alternately, a probe point may be followed by a "!" charac-  
       ter, to indicate that it  is  both  optional  and  sufficient.
====

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



More information about the Systemtap mailing list