Debugging application by jumping in time

RE: Debugging application by jumping in time

awneil — Wed, 13 Feb 2019 14:12:11 GMT

Yes - That kind of thing.

As I said initially, it can be as simple as just dropping bytes into a ring buffer

RE: Debugging application by jumping in time

schef — Wed, 13 Feb 2019 14:04:39 GMT

Aha some kind of profiler. I have found something like this: https://mcuoneclipse.com/2015/04/04/poor-mans-trace-free-of-charge-function-entryexit-trace-with-gnu-tools/

Another idea that came to me was to write a script which would generate gdb code which would write enter and exit of functions which would then be written to a file. And then use a external tool to examine this data.

RE: Debugging application by jumping in time

awneil — Wed, 13 Feb 2019 13:57:55 GMT

[quote userid="15419" url="~/f/nordic-q-a/43666/debugging-application-by-jumping-in-time/170899"]What do you mean by "breadcrumbs"?[/quote]

This kind of thing:

https://blog.sentry.io/2016/05/04/breadcrumbs

RE: Debugging application by jumping in time

schef — Wed, 13 Feb 2019 13:37:46 GMT

I found the problem using trial and error. When the app timer overflowed i made a recursive call.

Is is possible to see the stack size using gdb?

What do you mean by "breadcrumbs"?

Thanks for the ideas.

RE: Debugging application by jumping in time

awneil — Wed, 13 Feb 2019 13:10:32 GMT

How, exactly, does it "crash" ? eg, Is it hitting the Nordic Fatal Error handler?

Other suggestion:

* think if there's anything that your app does at 8 minutes (or some sub-multiple); eg timing-out or re-starting advertising

* instrument your code to give diagnostic traces via UART or RTT

* implement a memory buffer (not cleared by a reset) to record "breadcrumbs" as your code runs

* Break execution shortly before 8 minutes - are you running out of stack, for example ?