Translations:KDevelop5/Manual/Debugging programs/6/en: Difference between revisions

Latest revision as of 10:13, 6 September 2020

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (KDevelop5/Manual/Debugging programs)

Once the debugger stops (at a breakpoint, or a point where <code>abort()</code> is called) you can inspect a variety of information about your program. For example, in the image above, we have selected <menuchoice>Debug</menuchoice> to show the programs output. The <menuchoice>Frame Stack</menuchoice> 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: <code>main()</code> called <code>Bus bus;</code>; the list would be longer had we stopped in a function called by <code>bus</code> itself). On the left, we can inspect local variables including the current object (the object pointed to by the <code>this</code> variable).

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 Debug to show the programs output. The Frame Stack 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).

Revision as of 08:20, 1 October 2017 (view source) FuzzyBot (talk \| contribs) (Importing a new version from external source)		Latest revision as of 10:13, 6 September 2020 (view source) FuzzyBot (talk \| contribs) (Importing a new version from external source)
Line 1:		Line 1:
	Once the debugger stops (at a breakpoint, or a point where <code>abort()</code> is called) you can inspect a variety of information about your program. For example, in the image above, we have selected the <menuchoice>Frame Stack</menuchoice> 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 ~~(here a total of 8)~~ and how execution got to the current stopping point at the right (here: <code>main()</code> called <code>~~run()~~</code>; the list would be longer had we stopped in a function called by <code>~~run()~~</code> itself). On the left, we can inspect local variables including the current object (the object pointed to by the <code>this</code> variable).		Once the debugger stops (at a breakpoint, or a point where <code>abort()</code> is called) you can inspect a variety of information about your program. For example, in the image above, we have selected <menuchoice>Debug</menuchoice> to show the programs output. The <menuchoice>Frame Stack</menuchoice> 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: <code>main()</code> called <code>Bus bus;</code>; the list would be longer had we stopped in a function called by <code>bus</code> itself). On the left, we can inspect local variables including the current object (the object pointed to by the <code>this</code> variable).