[m-rev.] for review: improve debugging support for il grade.

[Peter Ross]

On Wed, Nov 05, 2003 at 10:15:41AM +0100, Peter Ross wrote:
> On Wed, Nov 05, 2003 at 01:32:25PM +1100, Zoltan Somogyi wrote:
> > On 04-Nov-2003, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > > That looks pretty good.  However, there's still one thing that
> > > worries me.  If you use `--debug', then won't it think that the
> > > grade is `il.tr.debug'?
> > 
> > I agree. --debug should mean one thing: debugging the Mercury
> > source, which is not yet possible for the IL backend. The option to
> > turn on the debugging of the generated IL code should be called
> > something else.
> > 
> It does allow you to debug the Mercury source.  That is you can single
> step the Mercury code, step into a procedure, place a break point on a
> line number and inspect the values of the variables.  It is a bit
> rough around the edges with some of the line number mappings and the
> variable names, but that this should be just a SMOP to get working
> correctly.
> 
> It however doesn't use mdb but any .NET compatible debugger.
> 
> Of course we could change the option name to --il-debug or
> --source-debug (there may be other backends in the future which will
> have a generic debugging framework).

What is the preferred option here?

-- 
Peter Ross		
Software Engineer                                (Work)   +32 2 757 10 15
Mission Critical                                 (Mobile) +32 485 482 559
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------