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.
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.
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.
patch committed