“c” (continue) will make gdb continue the execution of the program where its interrupted until a new breakpoint is found.“finish” will make gdb complete all the lines within the current function until its completed, i.e.“l” (list) will show a few listing of lines (usually 20) of the source code that gdb is currently inspecting.

“s” (step) will make gdb to execute the next line of the source program but if there is any sub-function then it will entered.“n” (next) will make gdb to execute the next line of the source program without entering any sub-functions, it will considered as a single instruction.“r” (run) will make gdb to start running the program until a breakpoint (or a crash) is found.“main” ) will set a breakpoint breakpoints are places where you (the developer) ask the debugger to stop the running of the program to inspect what’s happening at that specific point “b” (break) followed by a source code line numer (i.e.When starts gdb ready all the infoes it can from withing the binary or the core file and provide you with a propt, usually “gdb>” from where you can issue the command to operate with it. debugging a core file: gdb crash /tmp/re.11234.debugging a binary: gdb /usr/bin/myprogram.emacs – yes, the old monster integrates gdb.

If your lazy you can use many frontends to gdb for example: A core is a file left around by an application when it crashes. Gdb is the command line tool to debug any Linux binary that has not been stripped or a core file.

Markdown monster keeps crashing