> I'm suffering stack overflow in a program that uses both multiple
> processes and multiple threads. Can anyone help me interpret the
> following -xc output? In particular, which "<...>" reports relate to
> the stack overflow? (I've added a newline following each '>' to
> increase readability.) I think most (if not all) of the reports
> preceding the "stack overflow" line reflect EOF exceptions that are
> expected.
>
> Also, how can I tell which thread in which process is suffering the
> stack overflow?
The -xc hack was never really designed to do this. However, you could
improve matters by modifying the code (PrimOps.hc:359 in the 5.04.1
sources), to include the process pid and perhaps the thread ID
(CurrentTSO->id). If you're using Volker Stolz's labelled threads, then
you could print out the thread label too.
I think perhaps at least we ought to print a newline after the cost
centre stack :)
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
