I've just committed a good, stable, version of froggy, including
documentation complete with respect to current function: cd to
froggy/docs and bang in 'make', then point your browser at
/froggy/docs/html/book1.html. It's still a bit rough, and I
need to add more details in various places, and may
Just for the curious, here's an update on the current capabilities of
the froggy module, expressed as a description of the command line
options that exercise them. (This is cut'n'pasted from the latest
froggy README.)
Just to put it all in one place, current usage of froggy-test is as
From the README:
Added module code that utrace_attach()es the client
process,e.g., the
debugger.itself. What this does is allow fork()s of the
debugger to be
caught by report_clone(), thereby allowing the resultant child
process
to be utrace_attach()ed, which has
