-
Book Overview & Buying
-
Table Of Contents
Practical Debugging for Embedded ARM Systems
By :
Let's assume that you already have an automated build system running that produces your output binary file. You maybe even have a way to automatically program the target device and run some unit tests, which can indicate whether they have passed or failed.
How would you analyze a test failure?
One approach would be to simply look at the problematic code part that failed the test and try to do a static analysis. While it is definitely a valid strategy that will yield results in many cases, it is not really very fast or flexible.
Another way would be to analyze the system log and see whether you can spot anomalies, which would bring you back to the approach before, where you do a static analysis on the problematic code around the affected log message.
Again, such setups will already catch and solve many bugs. But what if I told you that you were already debugging all along?
Yes, the approach is not very dynamic or modern, but...