The process received a SIGPIPE. The default behaviour for this signal is to end the process. A SIGPIPE is sent to a process if it tried to write to a socket that had been shutdown for writing or isn’t connected (anymore). To avoid that the program ends in this case, you could either make the … Read more
For example, here is how you could use breakpoint commands to print the value of x at entry to foo whenever x is positive. break foo if x>0 commands silent printf “x is %d\n”,x cont end If the first command you specify in a command list is silent, the usual message about stopping at a … Read more
To debug optimized code, learn assembly/machine language. Use the GDB TUI mode. My copy of GDB enables it when I type the minus and Enter. Then type C-x 2 (that is hold down Control and press X, release both and then press 2). That will put it into split source and disassembly display. Then use … Read more
This error occurs because OSX implements a pid access policy which requires a digital signature for binaries to access other processes pids. To enable gdb access to other processes, we must first code sign the binary. This signature depends on a particular certificate, which the user must create and register with the system. To create … Read more
You can attach to a running process with gdb -p PID.
Short answer: mkdir -p ~/.config/gdb echo ‘set history save on’ >> ~/.config/gdb/gdbinit Long answer: Command history is covered in the GDB manual, 22.3 Command History. Create a file $HOME/.config/gdb/gdbinit, and add the following line: set history save on You can set the number of past commands saved with the following. The command is described as … Read more
As far as I know you can’t get such information with help of gdb, but for these purpose you can try valgrind memcheck with option –track-origins
Your GCC makes PIE executables by default, so there is no fixed base address in the file (and disassembly shows it relative to 0, i.e. offsets rather than absolute addresses). Once the kernel’s ELF program loader has created a running process from the executable (and chosen a virtual address as the base), GDB can show … Read more
but the corresponding file is not changed. It’s hard to say what address you are actually modifying, and so whether your change should actually modify the binary or not. In the past, I’ve found that after modifying the binary, I need to immediately quit. If I do anything other than quit (e.g. run), then GDB … Read more
(Ref: http://lists.gnu.org/archive/html/gdb/2009-12/msg00004.html) gdb is missing the debug information of the cos function, and therefore assume it is an int cos(…) function, so the values are not returned correctly (esp. on x86 as the registers to store floating point return and integer return are different). This could be worked around by specifying the type: (gdb) p … Read more