Translations:KDevelop5/Manual/Debugging programs/6/en
Once the debugger stops (at a breakpoint, or a point where abort()
is called) you can inspect a variety of information about your program. For example, in the image above, we have selected to show the programs output. The tool at the bottom (roughly equivalent to gdb's "backtrace" and "info threads" commands) that shows the various threads that are currently running in your program at the left, and how execution got to the current stopping point at the right (here: main()
called Bus bus;
; the list would be longer had we stopped in a function called by bus
itself). On the left, we can inspect local variables including the current object (the object pointed to by the this
variable).