[m-users.] Mercury Development Docker, and Bisecting Debugger?

[Volker Wysk]

Am Dienstag, dem 21.12.2021 um 19:08 +1100 schrieb Zoltan Somogyi:
> 
> On Tue, 21 Dec 2021 08:56:06 +0100, Volker Wysk <post at volker-wysk.de> wrote:
> 
> > Am Dienstag, dem 21.12.2021 um 11:34 +1100 schrieb Peter Wang:
> > > asm_fast.gc.decldebug.stseg is the one you will need to use the
> > > declarative debugger. 
> > 
> > Is the declarative debugger different from the normal debugger, "mdb"?
> 
> Yes and no. It is invoked from within mdb, via the "dd" command,
> but it is quite different. Within the declarative debugger, the debugger itself
> decides what to look at next, though you can control it. If you know military
> terminology, think of yje as the debugger being a tactician that executes
> your chosen strategy.

This sounds interesting.  :-)

> Also, to make full use of the declarative debugger, you have to compile
> your program in a grade whose name contains "decldebug", not just
> "debug". This puts into the executable the extra info that the declarative
> debugger can use but non-dd mdb does not.
> 
> See section 7.11 of the Mercury users' guide.

Okay, thanks. I'll read the user's guide.

Cheers,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.mercurylang.org/archives/users/attachments/20211221/35e21661/attachment.sig>