Description: KDbg is a graphical user interface to gdb, the GNU debugger. It provides an intuitive interface for setting breakpoints, inspecting variables, and stepping through code.Last changelog:
KDbg 3.0.1
- Use a color of the selected line with better contrast depending on the UI theme being used.
- Recognize parameter names of variadic function templates.
- Show char16_t and char32_t string values.
- No longer install individual frame images of the pulse animation.
Using Fedora 4; GDB: "GNU gdb Red Hat Linux (6.3.0.0-1.21rh)" (gdb-6.3.0.0-1.21.i386.rpm).
"kdbg myapp" gives error dialog: "GDB exited unexpectedly."
However, "gdb myapp" works fine.
Any ideas?
It is a bug in the gdb build shipped with Fedora 4. Rebuild gdb from source and the problem goes away. Specifically "info line main" crashes that version of gdb.
...are so importatnt? When options like LD_BIND_NOW=1 will be persistent? It's crazy we need to enter it every time. And gdb (6.x) crashes for every two sessions.
kdevelop already have a debugger.
I personnaly like to use both. from time to time... kdevelop can be a bit big on a small computer. especialy for a quick task.
kdbg with vim,gcc,bash,etc. is great.
KEEP UP THE GOOD WORK BUD !!!
kdbg always been great and just get better and better.
Ratings & Comments
10 Comments
Subject line says all. m0nk
It's in the works.
How I can find ALL kdbg's config files ? kdbg 2.1.0. Thank you.
Using Fedora 4; GDB: "GNU gdb Red Hat Linux (6.3.0.0-1.21rh)" (gdb-6.3.0.0-1.21.i386.rpm). "kdbg myapp" gives error dialog: "GDB exited unexpectedly." However, "gdb myapp" works fine. Any ideas?
It is a bug in the gdb build shipped with Fedora 4. Rebuild gdb from source and the problem goes away. Specifically "info line main" crashes that version of gdb.
This has been fixed in 2.0.1
...are so importatnt? When options like LD_BIND_NOW=1 will be persistent? It's crazy we need to enter it every time. And gdb (6.x) crashes for every two sessions.
LD_BIND_NOW=1 need no longer be set; gdb does it the right way now. -- Hannes
kdevelop already have a debugger. I personnaly like to use both. from time to time... kdevelop can be a bit big on a small computer. especialy for a quick task. kdbg with vim,gcc,bash,etc. is great. KEEP UP THE GOOD WORK BUD !!! kdbg always been great and just get better and better.
The program is nice, but when will you integrate it with KDevelop ?