KDbg: Difference between revisions

From KDE UserBase Wiki
No edit summary
No edit summary
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<languages />
<languages />
{{Proposed deletion|Not a KDE app}}
<translate>
<translate>


<!--T:1-->
{|class="vertical-centered"
{|class="vertical-centered"
|[[Image:Kdbgtotal.png|300px]]||KDbg is a graphical tool for debuggin your programs
|[[Image:Kdbgtotal.png|300px]]||KDbg is a graphical tool for debugging your programs
|}
|}


== Features ==
== Features == <!--T:2-->




<!--T:3-->
[[Image:Kdbgtotal.png|center|500px|thumb|Source code, breakpoint, local variables, watched expressions, and the thread list]]
[[Image:Kdbgtotal.png|center|500px|thumb|Source code, breakpoint, local variables, watched expressions, and the thread list]]


<!--T:13-->
* Inspection of variable values in a tree structure.


* Easy inspection of variables
<!--T:15-->
* Basic commands (step, next, etc..) bound to function keys
* Direct member: For certain compound data types the most important member values are displayed next to the variable name, so that it is not necessary to expand the subtree of that variable in order to see the member value. For example, you don't need to go into a variable of type QString if you want to see the string that the variable holds. (BTW, this is of course not hardcoded, but can be extended to new types.) KDbg can even display Qt's QString values, which are Unicode strings.
* Conditional breakpoints
* A full set of tools for viewing code, searching text, and for manipulating variables.
{{Community-app}}


<!--T:16-->
* Debugger at your finger tips: The basic debugger functions (step, next, run, finish, until, set/clear/enable/disable breakpoint) are bound to function keys F5 through F10. Quick and easy.
<!--T:17-->
* Of course, lots of other basic functions: View source code, search text, set program arguments and environment variables, display arbitrary expressions. Everything you need to debug a program!
<!--T:18-->
* Debugging of core dumps, attaching to running processes is possible.
<!--T:5-->
[[Image:Kdbglocalswatches.png|center|500px|thumb]]
[[Image:Kdbglocalswatches.png|center|500px|thumb]]


<!--T:6-->
[http://www.kdbg.org/ The project home page] gives more details.


[http://www.kdbg.org/ The project home page] gives more details. <br />
<!--T:14-->
A User Manual [http://www.kdbg.org/manual/ is on-line]
A [http://www.kdbg.org/manual/ User Manual]  is available on the project website.


<!--T:7-->
{{Community-app-footnote}}
{{Community-app-footnote}}


<!--T:8-->
[[Category:Development]]
[[Category:Development]]
</translate>
</translate>

Latest revision as of 13:34, 23 April 2024

Other languages:

Pending Deletion

This page has been proposed for deletion for the following reason:
Not a KDE app
Please use the discussion section of this page to voice your opinion on this.
KDbg is a graphical tool for debugging your programs

Features

Source code, breakpoint, local variables, watched expressions, and the thread list
  • Inspection of variable values in a tree structure.
  • Direct member: For certain compound data types the most important member values are displayed next to the variable name, so that it is not necessary to expand the subtree of that variable in order to see the member value. For example, you don't need to go into a variable of type QString if you want to see the string that the variable holds. (BTW, this is of course not hardcoded, but can be extended to new types.) KDbg can even display Qt's QString values, which are Unicode strings.
  • Debugger at your finger tips: The basic debugger functions (step, next, run, finish, until, set/clear/enable/disable breakpoint) are bound to function keys F5 through F10. Quick and easy.
  • Of course, lots of other basic functions: View source code, search text, set program arguments and environment variables, display arbitrary expressions. Everything you need to debug a program!
  • Debugging of core dumps, attaching to running processes is possible.

The project home page gives more details.

A User Manual is available on the project website.



Support for this application can be found from the project's home page