F
F
fryme2011-06-24 09:24:07
linux
fryme, 2011-06-24 09:24:07

C/C++ debugger under linux

I write code of varying complexity under linux. It happens in pure C ++, sometimes using Qt, sometimes in pure C, in different ways. And as much as I write it, I most often debug it using the “poke” method, or by displaying some kind of stupid messages in stdout / stderr. This seems to me to be a very big gap in my practice.
And all because I can't find a good debugger for these languages. I tried a lot of things, but none of them can come close to what is built into Microsoft's visual studio. Convenient, fast, error-free.
Here's what I've tried:
gdb - hard and inconvenient to use, especially when a large project with a lot of sources;
ddd - sorry, but this is about the same as gdb;
kdbg - almost perfect, but still not up to Microsoft, sometimes buggy and jumps from function to function, does not see all calls;
QtCreator dbg is good, but not all projects using Qt, and those without them I prefer to use some kind of vim as a text editor, and pulling a whole qt for the sake of the environment is kind of stupid.

There were some others, but they were discarded for low functionality and I don’t even really remember what they are called.

Tell me, am I picky or maybe there really is a good debugger for linux with the requirements set (the maximum approximation to what is in visual studio), which I don’t know?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
S
simplecode, 2011-06-24
@simplecode

when they talk about a debugger for Linux, it comes to mind - gdb,
ddd, kdbg ... - GUI interfaces to debuggers ...
IMHO: I advise you to make friends with gdb

A
afiskon, 2011-06-24
@afiskon

gdb for sure. Well, look for a GUI shell for it. Or write your own.

R
Rafael Osipov, 2011-06-24
@Rafael

Try Netbeans

V
vadiml, 2011-06-26
@vadiml

When I made calls to Qt4 from perl-a (I wrote the wrapper myself in perl xs), the GUI for gdb turned out to be the most convenient for digging inside the library - ddd, because. when using the console gdb, it stopped the output the first time control was transferred to the GUI.
> when a large project with a large number of sources;
Qt4 is one of the largest libraries, but I did not notice any inconvenience with ddd, only the appearance is a little archaic, but this does not interfere with work.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question