[m-rev.] for review: some documentation for ssdebug

[Peter Wang]

On 2010-06-10, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
> 
> On Thu, 10 Jun 2010, Peter Wang wrote:
> >
> >+* We have added an alternative debugger, the source-to-source debugger.
> >+  It is much more limited than mdb, but works not just with the low-level
> >+  C backend.
> 
> I suggest:
> 
> 	* We have added another debugger, called the source-to-source debugger (ssdb).
>  	  Currently it is more limited than mdb, but it does work with
>           backends other than the low-level C backend, e.g. the Java
>           backend.

I have removed "currently".

> >index 0000000..51ffbea
> >--- /dev/null
> >+++ b/README.ssdebug
> >@@ -0,0 +1,81 @@
> >+-----------------------------------------------------------------------------
> >+
> >+SOURCE-TO-SOURCE DEBUGGER
> >+
> >+The source-to-source debugger (ssdebug, ssdb) is a debugger of last resort.
> 
> I would not describe it as the debugger of "last resort", for me that
> would be gdb or jdb (depending on the backend).

Ok.

> >+As in mdb, the three numbers are the event number, call sequence number (CSN)
> >+and the stack depth.  Type "help" to show a list of commands.
> 
> How closely to mdb and ssdb commands line up (for the subset that ssdb
> supports)?

There's only one command which does something outright different,
which is that "print" acts like "print *".  To be fixed.

Peter
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------