Author Topic: Where to start debugging an exception  (Read 4631 times)

Last_Mile

  • Newbie
  • *
  • Posts: 15
Where to start debugging an exception
« on: May 07, 2017, 05:19:28 pm »
My project is trying to get the x10 library working for the oak.  The library works for an Arduino, but pops  out exceptions on the Oak.  It looks like the exceptions occur when the code enters into an ISR routine.

I'm getting exceptions (0), (9) and (28).  After reading through http://digistump.com/board/index.php/topic,2407.msg11436.html#msg11436 and installing https://github.com/me-no-dev/EspExceptionDecoder, I'm no further along trying to figure the issue out.  The EspExceptionDecoder throws out a not supported on Oak error.

Are there other tools out there to help me decode the exception errors and stack dumps?  I'd put in a ton of Serial.println statements, but everything I've read says don't put print or delay statements in ISRs.

What other avenues could I explore to solve this issue?

Any pointers would be greatly appreciated.

Thanks

PeterF

  • Hero Member
  • *****
  • Posts: 881
Re: Where to start debugging an exception
« Reply #1 on: May 07, 2017, 11:56:12 pm »
I don't know if I'll have time to play with the Java SDK and get things set up so I can compile stuff again, but from what Nevyn said in the last post, two lines need to be changed in the source code and then the tool recompiled, and then it will work for the Oak.

I suspect from a quick look at the code that it is somewhere in the createAndUpload() function, probably related to the path check... either he deleted it, or added a second part to the test so it a) doesn't bug out and b) is correctly configured for the oak. I was actually hoping he would post his modified build or the changed lines, but maybe he'll come along later ;)




« Last Edit: May 07, 2017, 11:58:47 pm by PeterF »

Last_Mile

  • Newbie
  • *
  • Posts: 15
Re: Where to start debugging an exception
« Reply #2 on: May 08, 2017, 09:17:25 am »
I tried changing various lines, but got the same results.  Hopefully Nevyn will let us know which lines he changed or post a modified and running version.  This would really help.