How to debug an unhandled exception

The exception string and stack trace should get printed as the application teardown happens. I'd be interested to see a test case that demonstrates the problem so we can get a look and make a fix if necessary. As for how to debug it, you have a few options. You can debug the program under eclipse and set breakpoints at various places and step through the code as is necessary. The classic printf debugger is often sufficient for most needs, but it isn't ideal as it takes time (sprinkle print calls throughout the code and then run it, find the area where the problem is, remove print code from other areas and add more in the problem area until you find the exact line), or catch the exception and log the result... try { // code that might throw an exception } catch (ex) { Toybox.System.println(ex.getErrorMessage()); ex.printStackTrace(); // rethrow if you want to let it crash throw ex; } Travis

The exception string and stack trace should get printed as the application teardown happens. I'd be interested to see a test case that demonstrates the problem so we can get a look and make a fix if necessary. As for how to debug it, you have a few options. You can debug the program under eclipse and set breakpoints at various places and step through the code as is necessary. The classic printf debugger is often sufficient for most needs, but it isn't ideal as it takes time (sprinkle print calls throughout the code and then run it, find the area where the problem is, remove print code from other areas and add more in the problem area until you find the exact line), or catch the exception and log the result... try { // code that might throw an exception } catch (ex) { Toybox.System.println(ex.getErrorMessage()); ex.printStackTrace(); // rethrow if you want to let it crash throw ex; } Travis