Comments on: Debugging with GDB http://betterexplained.com/articles/debugging-with-gdb/ Learning shouldn't hurt. Let's share the insights that made difficult ideas click. Fri, 10 Sep 2010 15:29:12 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Eric http://betterexplained.com/articles/debugging-with-gdb/#comment-281841 Eric Thu, 15 Apr 2010 05:12:45 +0000 http://betterexplained.com/articles/debugging-with-gdb/#comment-281841 Good tutorial! I am debugging now and this tutorial helps me out. Thanks. Good tutorial!
I am debugging now and this tutorial helps me out.
Thanks.

]]> By: Nimrod http://betterexplained.com/articles/debugging-with-gdb/#comment-265336 Nimrod Tue, 15 Dec 2009 09:43:58 +0000 http://betterexplained.com/articles/debugging-with-gdb/#comment-265336 More tips that make gdb more bearable: 1. You can set conditions on breakpoints. E.g. "cond 3 (x==2)" will stop at breakpoint 3 only when x==2. 2. You can set ignore count on breakpoints. "ignore 3 1000" ignores the next 1000 crossing of breakpoint 3. Then at some interesting point in time (when your program crashes...), "info break 3" shows exactly how many times breakpoint 3 had been hit. Next time set the ignore count to one less than that number and gdb will stop one iteration before the crash... 3. When using "watch", make sure gdb says "hardware watchpoint set". Unlike software watchpoints, these do not slow down program execution. 4. It is possible to define macros (using define xxx ... end) in .gdbrc Other useful features I haven't used: 1. gdb7 supports reverse debugging 2. gdb7 is scriptable using Python. Together with the new libstdc++ you get pretty printing of C++ STL collection classes. More tips that make gdb more bearable:

1. You can set conditions on breakpoints. E.g. “cond 3 (x==2)” will stop at breakpoint 3 only when x==2.

2. You can set ignore count on breakpoints. “ignore 3 1000″ ignores the next 1000 crossing of breakpoint 3. Then at some interesting point in time (when your program crashes…), “info break 3″ shows exactly how many times breakpoint 3 had been hit. Next time set the ignore count to one less than that number and gdb will stop one iteration before the crash…

3. When using “watch”, make sure gdb says “hardware watchpoint set”. Unlike software watchpoints, these do not slow down program execution.

4. It is possible to define macros (using define xxx … end) in .gdbrc

Other useful features I haven’t used:

1. gdb7 supports reverse debugging

2. gdb7 is scriptable using Python. Together with the new libstdc++ you get pretty printing of C++ STL collection classes.

]]> By: links for 2009-06-12 | manicwave.com http://betterexplained.com/articles/debugging-with-gdb/#comment-245151 links for 2009-06-12 | manicwave.com Fri, 12 Jun 2009 12:03:14 +0000 http://betterexplained.com/articles/debugging-with-gdb/#comment-245151 [...] Debugging with GDB | BetterExplained (tags: debugging iphone osx gdb) [...] [...] Debugging with GDB | BetterExplained (tags: debugging iphone osx gdb) [...]

]]>