English
How to use a debugger as a bug preventive tool
The essence of preventive debugger-driven software verification is "Debug Early, Debug Often"
By Nathan Field, Green Hills Software, Inc.
Embedded.com (12/16/09, 12:42:00 PM EST)
Generally speaking, a debugger is thought of as a tool to use after a problem is encountered, when its cause is not obvious. Although a good debugger is the best tool for diagnosing problems and defects in software products, their use in the code writing phase is often overlooked. In this article, I will discuss how and why you would want to use a debugger before you know that you have a bug to track down and fix. At the end of the article, I will discuss some of the basic requirements that a debugger must meet in order to apply this technique.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- How to Ensure a Bug Free BootROM?
- How the Ability to Manage Register Specifications Helps You Create More Competitive Products
- How to Save Time and Improve Communication Between Semiconductor Design and Verification Engineers
- Last-Time Buy Notifications For Your ASICs? How To Make the Most of It
- How to cost-efficiently add Ethernet switching to industrial devices
New Articles
- Beyond Limits: Unleashing the 10.7 Gbps LPDDR5X Subsystem
- How to Design Secure SoCs: Essential Security Features for Digital Designers
- System level on-chip monitoring and analytics with Tessent Embedded Analytics
- What tamper detection IP brings to SoC designs
- RISC-V in 2025: Progress, Challenges,and What's Next for Automotive & OpenHardware