Invoking frysk as:
should cause frysk??
-> start the source code browser on that process
-> start the monitor on that process; or more exactly, start the setup assistant
with that process pre-selected
I'm going to recommend the second, since the command line utilities all do an
attach/continue and it would be consistent.
Please debate :-)