Add documentation for parrot_debugger

[allison]

Add documentation for the PIR debugger, 'parrot_debugger'. We need more examples.

[dukeleto]

Replying to allison:

Add documentation for the PIR debugger, 'parrot_debugger'.

What kind of documentation is wanted? Is there other currently existing docs that can be used as a reference guide for the style and format?

[dukeleto]

21:00:55 < dukeleto> chromatic: i think if someone could tell me what they wanted to see in the debugger docs, i could 'finish' the task, but right now, it 
                     is ambiguously specc'ed
21:01:17 < chromatic> Do you have a list of tasks you can perform in the debugger?  We could brainstorm some use cases.
21:01:23 < allison> dukeleto: focus on helping people getting started in using it
21:01:52 < dukeleto> allison: ok, I think we definitely need more of a debugger "user guide" than a manual page. good idea
21:02:01 < pmichaud> dukeleto++
21:02:20 < chromatic> japhb, seed libraries?
21:02:30 < allison> dukeleto: a short manpage is also good (so we can ship it with the distros), but that should be fast

[dukeleto]

Currently we have three places with various types of parrot_debugger documentation : src/parrot_debugger.c (run time flag docs) src/debug.c (docs for interactive debugger use and internals docs) and docs/debugger.pod . A list of things that you can do in the debugger is in docs/debugger.pod as well as from typing "help" while in the debugger.

Allison said that she wants a short man page-like thing that can be installed for distros and pmichaud liked the idea of a "user guide." Where should these live? Also, should all of the docs inside the C files be moved somewhere more useful? It is POD, but nothing extracts it and puts it where mere mortals would find it useful.

[allison]

Need to check that we have an adequate manpage for 2.3 release.