I think someone on this mailist recently said that an exception that occurs
in a thread is sometimes lost? That is, even if I put in a lot of pprint
statements or println statements* or (stack/print-stack-trace e)
expressions, and I just want it to show up in terminal, so I can debug it,
but
I don't see any threads in your Stack Overflow post.
I thought it would be over-complicated to include all of the code. But
inside my -main function I start a new thread and call the function that
calls the function that causes this error.
They are not lost. Unhandled exceptions cause
On Jan 29, 2013, at 4:56 PM, Michael Klishin wrote:
2013/1/30 larry google groups lawrencecloj...@gmail.com
That is good to know. I have the top level function call wrapped in a
try/catch block, but I suppose I'll get better results if I do more of the
try/catch at a lower level, closer
