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-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
