After a couple hours of debugging, I located the culprit! I inserted some inter-thread signaling to force execution to follow a particular order until I got a deadlock, and then tracked down the bug. Now I just have to go back and get rid of all those print statements Shoe and Dusty had me put in… You know life is getting bad when your blog is being used as a place of communion for your friends across state boarders to get together to give you crap.
Yup…you’re a tool.
Hahahaha. And common, you know the ghetto-rigged print statements was a more elegant, modular, dynamic, and agile solution to the problem.