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.
To read the full article, click here
Related Semiconductor IP
- ReRAM NVM in DB HiTek 130nm BCD
- UFS 5.0 Host Controller IP
- PDM Receiver/PDM-to-PCM Converter
- Voltage and Temperature Sensor with integrated ADC - GlobalFoundries® 22FDX®
- 8MHz / 40MHz Pierce Oscillator - X-FAB XT018-0.18µm
Related Articles
- Corner Case Scenario Generation (CCSG) Tool: A Novel Approach to find corner case bugs in next generation SoCs
- Optimized tools ZAP embedded bugs
- SoCs: IP Reuse -> Design tool smooths complex core use
- SoCs: IP Reuse -> Right tool mix points to reuse success
Latest Articles
- An FPGA-Based SoC Architecture with a RISC-V Controller for Energy-Efficient Temporal-Coding Spiking Neural Networks
- Enabling RISC-V Vector Code Generation in MLIR through Custom xDSL Lowerings
- A Scalable Open-Source QEC System with Sub-Microsecond Decoding-Feedback Latency
- SNAP-V: A RISC-V SoC with Configurable Neuromorphic Acceleration for Small-Scale Spiking Neural Networks
- An FPGA Implementation of Displacement Vector Search for Intra Pattern Copy in JPEG XS