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

Tobias Nipkow nipkow at in.tum.de
Thu Jul 3 14:16:40 CEST 2014

Funnily enough I had the same problem yesterday and was at a loss what happened
until Johannes pointed out to me that there is a "stack overflow" message in the
shell window. Of course you need to scroll through all those messages to find it.


On 03/07/2014 13:57, Peter Lammich wrote:
> Hi,
> I recently ran into a method that produced a stack-overflow.
> The good thing is: In the current jedit version, it is properly
> highlighted and you immediately see that there is some error. (This was
> not always the case in the past)
> 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?
> --
>   Peter
> _______________________________________________
> isabelle-dev mailing list
> isabelle-dev at in.tum.de
> https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev

More information about the isabelle-dev mailing list