[Bug translator/2949] New: need "probe listing" command line option

[Bug translator/2949] New: need "probe listing" command line option

[fche at redhat dot com]

The stap program should have a command line option that
- lists available probes matching a probe-point wildcard
  (something like "-p2 -e 'probe $PATTERN' {}" but prettier)
- for probe aliases from a tapset, lists their local variables

This should enable tapsets that neglect to document themselves
in stapprobes(5) to still be presentable.

-- 
           Summary: need "probe listing" command line option
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


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

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

[Bug translator/2949] need "probe listing" command line option

[joshua dot i dot stone at intel dot com]

------- Additional Comments From joshua dot i dot stone at intel dot com  2006-07-27 16:28 -------
For tapsets, it might be nice if we had inline documentation describing probe
points and local variables, and then a 'stapdoc' command-line could present that
in a nice way.  I would imagine this would work something like a doxygen syntax,
or Perl's POD, or Python's pydoc.

-- 


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

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

[Bug translator/2949] need "probe listing" command line option

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2007-05-05 14:50 -------
Maybe we could kill two birds with one stone.

Many of our tapset functions/probes remain undocumented (and some untested,
but that's another problem).   We could ease the former problem by including
documentation right within the tapset script files, a la the javadoc experiment
in the runtime.

This would enable the translator to parse these documentation bits, and print
them alongside the raw data produced by the future list-probes option.


-- 


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

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

[Bug translator/2949] need "probe listing" command line option

[fche at redhat dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |5679


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

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

[Bug translator/2949] need "probe listing" command line option

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2008-04-10 19:40 -------
patch committed

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


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

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

[Bug translator/2949] need "probe listing" command line option

[fche at redhat dot com]

-- 
Bug 2949 depends on bug 5679, which changed state.

Bug 5679 Summary: inline documentation for scripts/tapsets
http://sourceware.org/bugzilla/show_bug.cgi?id=5679

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

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

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