I have use a lot the debuggers, but veru often without succes because:

- my program was to complex to debug it without backtracking
- backtracking often crashes (but it is hard to reproduce) and moreover 
is not usable when performing IO (at least the last time I used it)

If would be nice to have two ml functions (to use inside your code to 
debug):

allow_debugback (): backtraking is allowed after this function is 
executed (create the first fork for backtracking there). This function 
could recieve the maximum number of fork in argument instead of unit.

disallow_debugback (): no more backtracking possible (kills all the 
previous forks)

I think this is simple to implement and not very hard to use (for 
instance it is easy to put such a function in the treatment part of a 
parser to solve the IO problems).


-- 
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex

tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature
---------------------------------------------