Once gdb starts, you can run the program using “r args“. So if you are running your code by: $ executablefile arg1 arg2 arg3 Debug it on gdb by: $ gdb executablefile (gdb) r arg1 arg2 arg3
It works when I change to sudo gdb executableFileName! 🙂
I don’t believe so (but I may be wrong). You can do something like this: (gdb) define fn > finish > next > end And then just type: (gdb) fn You can put this in your ~/.gdbinit file as well so it is always available.
In contrast with the other answers, there are at least three options that do just what you require: clewn, pyclewn and vimgdb. All three projects are related. vimgdb is a patch against Vim and requires Vim to be recompiled. clewn is a standalone program that communicates with Vim through the Netbeans socket interface. This requires … Read more
You can use strcmp: break x:20 if strcmp(y, “hello”) == 0 20 is line number, x can be any filename and y can be any variable.
.gdbinit You can tweak your ~/.gdbinit to have colors. You can use mammon’s .gdbinit which is available here: https://github.com/gdbinit/gdbinit You can tweak it as much as you want too. I found this thanks to this SO answer. Here’s the kind of output that you can obtain: A GitHub repository is also available: https://github.com/gdbinit/Gdbinit On a … Read more
You can list breakpoints with: info break This will list all breakpoints. Then a breakpoint can be deleted by its corresponding number: del 3 For example: (gdb) info b Num Type Disp Enb Address What 3 breakpoint keep y 0x004018c3 in timeCorrect at my3.c:215 4 breakpoint keep y 0x004295b0 in avi_write_packet atlibavformat/avienc.c:513 (gdb) del 3 … Read more
You can use the finish command. finish: Continue running until just after function in the selected stack frame returns. Print the returned value (if any). This command can be abbreviated as fin. (See 5.2 Continuing and Stepping.)
You can use the core with GDB in many ways, but passing parameters which is to be passed to the executable to GDB is not the way to use the core file. This could also be the reason you got that error. You can use the core file in the following ways: gdb <executable> <core-file> … Read more
Generally, the backtrace is used to get the stack of the current thread, but if there is a necessity to get the stack trace of all the threads, use the following command. thread apply all bt