Quote from: JoelKatz on July 16, 2011, 02:45:01 AM

This is one of the annoying things about C++ exception handling. The exception was caught, and that obscured the information needed to find the code that generated it. Sad

All we can tell from that is that the RPC code threw an exception. This could be for reasons that really aren't the code's fault, such as running out of memory at a critical point, or (more likely) they could be due to bugs in the code.

One thing you can try -- use the 'up' command until you get to level 7, the 'ThreadRPCServer' call. And type 'print e'. If for some reason that doesn't work, you can try level 6, 'PrintException' and the command 'print pszMessage'.

So it turns out I made a stupid mistake. As part of a test some days ago, I had created a cron job that stopped and restarted bitcoind on an hourly basis. It appears that I wasn't waiting long enough for the bitcoind stop command to close out bitcoind. The 'trying to start bitcoind when it was in the midst of still shutting down' seems to have caused the cores.

I'm sorry for wasting your time, but really appreciate what you have taught me about debugging/troubleshooting these issues.