While running your program in memory intensive workflows, you may often run into a situation where the low memory condition starts to thrash the system. Such a program usually exhibits a performance problem as it has consumed most of its available virtual memory. Developers often use their favorite profilers to figure out the performance bottlenecks [...]
Have you faced the problem of breakpoint clutter where breakpoints keep piling up only to hinder the debugging session? It is then that one realizes that there are some breakpoints that can be deleted and others disabled.
A useful feature in a debugger is a temporary breakpoint that automagically gets deleted when hit thereby reducing the clutter of unnecessary breakpoints. These breakpoints are [...]
If you haven’t debugged in assembly yet, you haven’t debugged enough :-) Debugging assembly in gdb can be tricky at times.
A normal debugging session involving assembly language consists of the following steps -
Launch the program in gdb and set the required breakpoint(s).
When the breakpoint is hit, use the disassemble command to view the assembly language [...]
The rule of debugging is very simple -
“Every developer should strive to reproduce the bug by hitting the required set of breakpoints the least number of times. This allows faster and efficient debugging sessions.”
If you are familiar with hit count breakpoints already, you may want to click here to jump to the advanced tricks shared in this article.
What is the hit count of a breakpoint?
A debugger allows users to set a breakpoint at a specific line in code. When the execution reaches that line, the breakpoint is said [...]
