Hello Guilaume, On Mon, Sep 03, 2012 at 02:05:15PM +0200, Guillaume Seren wrote: > but I try with the "-safe-mode", and the crash did appened again, > when filtering large number of mail, so maybe it could be related to > this process. > > I follow the wiki debugging process, and it crash really fast, with a > "Broken pipe", > I attach the details of the log, to this mail. > > Regards > Guillaume. >
> [New Thread 0x7fffa1bfd700 (LWP 19547)] > [Thread 0x7fffa38fe700 (LWP 19543) exited] > > Program received signal SIGPIPE, Broken pipe. > [Switching to Thread 0x7fffa21fe700 (LWP 19546)] > 0x00007ffff73fb79d in write () at ../sysdeps/unix/syscall-template.S:82 > 82 ../sysdeps/unix/syscall-template.S: Aucun fichier ou dossier de ce type. > (gdb) [K(gdb) thread apply bt > (gdb) thread apply bt > (gdb) x > Argument required (starting display address). > (gdb) quit > A debugging session is active. > > Inferior 1 [process 19427] will be killed. > > Quit anyway? (y or n) unfortunally there are no backtrace infos, so it's difficult to say that syscall make this 'Broken pipe'. Can you please check http://wiki.debian.org/HowToGetABacktrace to get a proper backtrace from this crash? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
