Debugging AssertionFailure panics... deviceos 3.3.1

Firmware Device OS
1

hello,

in some situations on some of our p1 devices we sometime get lots of panic (10) restarts. in an old post i read:

At the moment, all of the AssertionFailures are in things related to threads and the system thread, but that’s just because those are the only things that have been instrumented with an AssertionFailure panic.

is this true for deviceos 3.3.1?

anyone any idea how to debug this?

thanks
frank

2

This will be difficult to debug. The assertion failure usually results because of memory corruption somewhere else. This could be overwriting a block of memory, using a freed pointer, etc..

While you can put a breakpoint in the panic handler, it's not always helpful because the problem isn't always in the stack backtrace because memory was corrupted somewhere else.

3

Hey,
my troubleshooting process would go like this:

  • comment out everything in loop() or add a return; at the top - does it still Panic?
  • comment out everything in setup() or add a return; at the top - does it still Panic?
  • comment all the global classes instantiating before setup - it should not panic anymore.
  • this could be very time consuming.

That way I narrow it down to where the issue might be. Not bulletproof if there are other things at play.

Best of luck!

4

thanks @gusgonnet, this is what i am doing. problem is that the panics seem to happen in very specific situations (and i am not exactly sure what they are)... time consuming indeed! cheers!