Hello again, Thank you for your response. I tried it but the sigpipe still occurs, so this error stops the execution process and wont let the sbatch submit the job, so with that I cannot observe the job execution sequence, any other solutions?
2015-07-17 17:27 GMT+02:00 Brian Christiansen <[email protected]>: > You could try telling gdb to ignore the SIGPIPE: > > (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: > > > 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 > > > -- Bien Cordialement. BIKI Brahim， -------------------------------------------------------------------- Student in Polytech Paris-Sud University of Paris-Sud XI ( Orsay,France) Étudiant à Polytech Paris-Sud Université de Paris-Sud (Orsay,France) --------------------------------------------------------------------- Work mail: [email protected] Mail : [email protected] Tel: +33 (0)6 83 72 59 06 ---------------------------------------------------------------------
