Octavio Rojas Topete’s Post

Whenever an exception occurs in your application while you're in debugging mode, your API might crash, and you'd need to restart it. Here's a way to avoid this behaviour: In the Exception Settings window (𝐃𝐞𝐛𝐮𝐠 > 𝐄𝐱𝐜𝐞𝐩𝐭𝐢𝐨𝐧𝐬), uncheck the box for "𝐂𝐨𝐦𝐦𝐨𝐧 𝐋𝐚𝐧𝐠𝐮𝐚𝐠𝐞 𝐑𝐮𝐧𝐭𝐢𝐦𝐞 𝐄𝐱𝐜𝐞𝐩𝐭𝐢𝐨𝐧𝐬." This will prevent the debugger from breaking on these common exceptions, allowing your API to continue running. 𝐈𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭 𝐍𝐨𝐭𝐞: While this tip can be helpful for debugging specific issues, it's generally not recommended to disable exception handling entirely. Unhandled exceptions can lead to unexpected behavior or crashes in production environments. Use this approach cautiously and only during the debugging process.

If you feel stuck when debugging your embedded project, here's the formula that worked well for me: 1. Realize that some bugs, especially intermittent bugs, are notoriously hard to reproduce. Accept that first. This will relax my mind. 2. Start tidying up my code, like renaming dumb variable names, cleaning up unnecessary # include, refactoring duplicates, etc. 3. Start to pay an extra attention to data flow, not program flow. Sometimes, the bugs (especially intermittent) is caused by memory issues we're not aware of. Tidying up data flow will make things cleaner and clearer. 4. Don't forget to use version control while tidying up code. If your improvements make the firmware broken, easily revert back and clean again. 5. Slowly but surely, you will find that annoying bug. 6. Whenever you find the bug, kill it with no mercy.

How is software testing related to debugging? Debugging theory includes testing as part of its stadard resolution steps in the debug-fix cycle. https://buff.ly/3Jjn3BV

Validation is the process of uncovering issues and increasing confidence that the program performs as intended. Debugging is the process of determining why a program is malfunctioning or failing. To effectively resolve the issue, you must "analyze the events" that led to the error.

An example (or steps to reproduce an issue) goes a long way when reporting a technical issue. Of course this is not required, but it makes debugging a lot faster.

Best way to test system

Debugging isn't just about fixing errors; it's about understanding the root cause. Develop a systematic approach, utilize debugging tools effectively, and think critically to solve problems efficiently.

Simplify your Debugging Process! Follow these easy steps from spotting errors to fixing bugs and deploying changes. Get your code running smoothly in no time! 🐛💻 Here is a more detailed information about the Debugging Process:- 1) Start: Initiate the debugging process. 2) Identify Error: Recognize the issue or error causing the malfunction. 3) Reproduce the Bug: Replicate the bug to confirm it exists and understand its behavior. 4) Analyze Logs: Review system or application logs to gather insights into the root cause. 5) Apply Fix: Implement the necessary code changes to resolve the issue. 6) Run Tests: Execute tests to ensure the fix works and hasn't introduced new issues. 7) Validate Solution: Confirm that the issue is fully resolved and the system behaves as expected. 8) Deploy Changes: Roll out the fix to the appropriate environment (e.g., staging or production). 9) End: Conclude the debugging process once the issue has been fully addressed.

Ask yourself 3 questions before debugging a failure: 1. Is the failure consistent? 2. Have I checked the logs? 3. Did I validate recent code changes? Aimless debugging wastes time. Focus your investigation.

Shifting left in testing is about preventing bugs not finding them. But how do you prevent a bug? Easiest way? Become comfortable asking what seems like dumb questions as early and as often as possible in a software project. You may be surprised at the responses.