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

Latest revision as of 08:18, 1 October 2017

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).

Nå fejlsøgeren standser (ved et stoppunkt eller et sted, hvor abort() kaldes) kan du få forskellig slags information om dit program. I billedet ovenfor har vi for eksempel valgt værktøjet Frame Stack for neden i vinduet (det svarer nogenlunde til gdb's kommandoer "backtrace" og "info threads"), som til venstre viser de forskellige tråde, som i øjeblikket kører i dit program (der er i alt 8) og til højre, hvordan udførslen kom til det aktuelle stoppunkt (her blev run() kaldt fra main(); listen ville være længere, hvis vi var stoppet i en funktion kaldt fra run() selv). Til venstre kan vi inspicere lokale variable, herunder det aktuelle objekt (det objekt, som variablen this henviser til).