RE: Virtual Watchdog Timeout

Tom, thank you for your reply! 

 Can you help me understand the relationship between the addresses being thrown as the exceptions and the MAP file? You had address e2e9, but then the MAP file had e2bf as the address for the acos function that was causing the exception. I find this to generally be the problem I see. No real relationship between the address that gets thrown and anything meaningful to look at in the map file...
 

 I have an error handler, and its throwing virtual watchdog timeouts, but its VERY hard to figure out where the execution of the program really is when its getting stuck. 
 

 The original problem I was posting about I did wind up fixing, that was related to a network socket pointer that was getting overwritten in a funky way and making the http_handler() get stuck in one of its functions. But identifying that was a painstaking process of me walking through the code with breakpoints and watches, and debugging strings in stdio. I would love to be able to read my run time exception handler messages and get a little more useful info out of them. 
 

 Thanks