Re: systemtap GUI Requirements

[Henry Hughes <hughesw at us dot ibm dot com>]

My understanding of this feature is that we are going to allow the user 
to browse through a kernel source tree, open a file at random, e.g. 
kernel/fork.c, view the contents of the file, and click in the margin to 
place a kernel.statement block in the current systemtap file. It would 
work similarly to placing a breakpoint in most IDEs (eclipse in specific).

So it'd be...
User browses to specific kernel source file in the kernel browser, which 
pops up the selected file in a text editor
User finds the line they want to probe
User marks the point they want to probe
A skeleton probe kernel.statement("*@somefile:someline") statement is 
constructed for them and inserted inside the current .stp file.


Now as for where we get the kernel source that is being displayed... 
that I'm not sure about. We could give the user some freedom to just 
point us at a kernel source directory, but if that isn't the source for 
the running kernel it could cause problems. The /usr/src/linux symlink 
doesnt seem to be too common anymore, so that's probably not a good 
idea. I'm not sure what the best way to handle that is yet.

Hope that helps

Kevin Jia wrote:
> Very nice, but about "kernel source browser" --simply double click on
> the line they wish to probe. Doing so will leave a marker beside the
> line they clicked on as well as insert a prototype probe at the bottom
> of the script code.
>
> A little inexplicit, can you explain more ?
>
>
> On 4/18/06, Ryan Morse <ryan@linux.ibm.com> wrote:
>   
> > Hi-
> >
> > We have finished writing the systemtap GUI requirements document.  If
> > interested, please look over the pdf I attached.
> >
> > -Ryan
> >
> >
> >
> >