[m-rev.] diff: fix debugger/interactive failures

[Fergus Henderson]

> tests/debugger/interactive.{inp,exp}:
> 	Test only the interactive commands of mdb. The other commands are well
> 	exercised by the other test cases; duplicating them only leads to
> 	double maintenance of the expected outputs.

Sorry I didn't remember this earlier, but I remember now why the test
of the interactive debugger was done in the middle of other tests of
the debugger functionality.  The reason is that it is important to
test that execution of interactive queries doesn't corrupt the behaviour
of the program being debugged.  It's easy to imagine a case where
interactive queries work fine, but the state of the program and/or
the debugger is not properly restored after the query, so that something
goes wrong during subsequent execution.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------