On 2013-04-15, at 11:10 AM, Edward Chapin wrote:
> Hi,
>
> I mostly used kdbg which is a kde front-end to gdb. I would typically run things through valgrind to find problem spots, and then put in breakpoints in the relevant places in the code and step through carefully with the debugger.
Thanks for the suggestion. I'll give that a try. Could you provide a brief workflow summary for me please?
> More recently I've been having fun with newer versions of valgrind which provide a gdb server - basically you run valgrind with some special options in one window, and then you fire-up another gdb sessionin another window to control valgrind with a "remote" (i.e. to step through, query bits of memory to see when/where they were allocated etc.). If you'd like more information on that I could dig up my notes for you... kdbg can also be made to work with this - it's nice because every error generated by valgrind produces a breakpoint.
That looks like a very useful configuration. Yes please, I'd be interested in seeing your notes if it's not too much trouble.
|