From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Francesco Potorti` Newsgroups: gmane.emacs.devel Subject: SIGPIPE Date: Wed, 03 Jul 2002 15:07:20 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1025701726 20529 127.0.0.1 (3 Jul 2002 13:08:46 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 3 Jul 2002 13:08:46 +0000 (UTC) Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17PjsD-0005L0-00 for ; Wed, 03 Jul 2002 15:08:45 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17Pjxk-0001JZ-00 for ; Wed, 03 Jul 2002 15:14:28 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17PjsZ-0003Or-00; Wed, 03 Jul 2002 09:09:07 -0400 Original-Received: from pot.cnuce.cnr.it ([146.48.83.182]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17Pjqq-0003KL-00 for ; Wed, 03 Jul 2002 09:07:21 -0400 Original-Received: from pot by pot.cnuce.cnr.it with local (Exim 3.35 #1 (Debian)) id 17Pjqq-0005SW-00 for ; Wed, 03 Jul 2002 15:07:20 +0200 Original-To: Emacs developers X-fingerprint: 4B2 6187 5C3 D6B1 2E31 7666 9DF 2DC9 BE21 6115 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:5401 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:5401 While running Emacs (pretest version) under gdb, I got this: Program received signal SIGPIPE, Broken pipe 0x403a83e4 in write () from /lib/libc.so.6 (gdb) bt #0 0x403a83e4 in write () from /lib/libc.so.6 #1 0x00000000 in ?? () (gdb) This has occasionally happened to me since version 21 when signing a meail messagge with mailcrypt (which uses gpg). >From the backtrace it seemed to me that the stack was smashed, so I continued the process, expecting to see it abort. Instead, it continued and displayed a message: mc-gpg-process-region: SIGPIPE raised on process *GPG*; closed it