Would there be any advantage in doing this? There's no deadlock info produced for a debug threaded runtime, for example. Not according to ghc/rts/Schedule.c. Of course I could print the capabilities of the main thread (TSO structure) and see what it's blocked on, etc. but I could do that just as well without using -threaded. My issue seems to be that of a deadlock. Strangely enough, building with -debug and running with +RTS -Ds seems to go through all the way. I think I'm not completely reproducing the previous deadlock situation, though, so I'm working on that. On Dec 11, 2005, at 5:12 PM, Peter Simons wrote:
Joel Reymont writes:
How do I get a threaded+debug runtime?
You have to build GHC from source code for that. When you do, make sure your ${srcdir}/ghc/mk/build.mk file contains:
GhcRTSWays += thr_debug