GNU bug report logs - #10582
Emacs under gdb stops on SIGPIPE

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ivan Kanis <ivan.kanis <at> googlemail.com>
Cc: 10582 <at> debbugs.gnu.org
Subject: bug#10582: better backtrace
Date: Sun, 01 Apr 2012 19:19:56 +0300

> From: Ivan Kanis <ivan.kanis <at> googlemail.com>
> Date: Sun, 01 Apr 2012 12:41:01 +0200
> 
> Here is the full backtrace including the exception code and the lisp
> backtrace. Let me know what I can do further to identify the problem.
> 
> Program received signal SIGPIPE, Broken pipe.
> 0x0012e416 in __kernel_vsyscall ()
> 
> #1  0x010a3523 in __write_nocancel () from /lib/libpthread.so.0
> No symbol table info available.
> #2  0x0818e0fc in emacs_write (fildes=10, buf=0xa90b91c "QUIT :\002ERC\002 Version 5.3 (IRC client for Emacs)\r\n", nbyte=48)
>     at sysdep.c:1932
>         rtnval = 139703669
>         bytes_written = 0
> #3  0x08240a3d in send_process (proc=149853781, buf=0xa90b91c "QUIT :\002ERC\002 Version 5.3 (IRC client for Emacs)\r\n", 

AFAIK, SIGPIPE means that the other side of the pipe was closed.  Is
Emacs communicating with a program or with the network directly?  If
the former, please see why does the program exit; if the latter,
perhaps you have connectivity problems?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.