You could try telling gdb to ignore the SIGPIPE:
Konsole output
(gdb) handle SIGPIPE nostop noprint
Signal Stop Print Pass to program Description
SIGPIPE No No Yes Broken pipe
On 07/17/2015 01:41 AM, BIKI BRAHIM wrote:
Error while debugging with GDB
Hello all,
Currently I'm debugging the sbatch.c code to figure out the job
execution sequence when we run jobs with *sbatch *command.
While debugging with GDB (using the command *step*), I encounter this
error "*Program received signal SIGPIPE, Broken pipe. (in writev ()
from /lib64/libc.so.6)*", this error stops the debugging and cancel
the job sent (for debugging) .
I think it's caused by munge, I believe that munge does not offer the
debug options for security reasons.
How to fix this problem or work around it ?
Regards
Biki brahim
University of Paris-Sud
Orsay, France
