Working with Nordic Semi Bluetooth Stack was like that when working with it a few years ago. If you reach a breakpoint while the Bluetooth stack was running, it would crash the program.
So printf to dump data while it ran and only break when absolutely necessary.
Try debugging a distributed embedded real time system which crashes when you are in a breakpoint too long because the heartbeat doesn't respond
Working with Nordic Semi Bluetooth Stack was like that when working with it a few years ago. If you reach a breakpoint while the Bluetooth stack was running, it would crash the program.
So printf to dump data while it ran and only break when absolutely necessary.
Oh? Another embedded programmer? This behavior pains me as well.
Yeah. I mostly code in C because the tools come natively in C. I also do python and C# to create tools for my embedded projects.
Or just any dpdk program, where any gdb caused slowdown causes the code to "behave as expected"