Hi. I have a generated Haskell program that emits a "Fail: <<loop>>" at runtime. Are there some tools or standard manner for identifying the lines that participate in the loop? The use of "-debug" and "-prof -auto-all" only provides a call stack, and the loop is, is I understand it, due to a circular definition, so the call stack is of little help. -- Sincerely | Homepage: Jørgen | http://www.hex.no/jhf | Public GPG key: | http://www.hex.no/jhf/key.txt
Jørgen Hermanrud Fjeld
I have a generated Haskell program that emits a "Fail: <<loop>>" at runtime. Are there some tools or standard manner for identifying the lines that participate in the loop?
Provided your program does not use too many GHC extensions or fancy libraries, you could try using the Hat tracer http://haskell.org/hat which now comes with two tools called 'hat-nonterm' and 'black-hat', specially designed for finding the cycle that leads to a black hole or non-termination. Regards, Malcolm
participants (2)
-
Jørgen Hermanrud Fjeld -
Malcolm Wallace