[isabelle-dev] Methods that fail with stack-overflow

Makarius makarius at sketis.net
Thu Jul 3 15:13:08 CEST 2014

On Thu, 3 Jul 2014, Lars Noschinski wrote:

> On 03.07.2014 13:57, Peter Lammich wrote:
>> Hi,
>> I recently ran into a method that produced a stack-overflow.
>> The bad thing: The only way how to get a clue what is going wrong is to
>> open the "raw output panel". This writes "stack-overflow" then, without
>> any location or trace. How to enable tracing for those exceptions, in
>> particular as Toplevel.debug seems to have gone away?
> There is ML_trace (and a similar option)

Just by accident, I wrote some more documentation on the "similar options" 
42 hours ago:



More information about the isabelle-dev mailing list