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

Peter Ross pro at missioncriticalit.com
Wed Nov 5 20:15:41 AEDT 2003

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).
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

More information about the reviews mailing list