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: gdb: bad backtrace with interrupted write call Date: Wed, 24 Jul 2002 17:01:53 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1027522942 25781 127.0.0.1 (24 Jul 2002 15:02:22 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 24 Jul 2002 15:02:22 +0000 (UTC) Cc: Emacs developers Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17XNef-0006hi-00 for ; Wed, 24 Jul 2002 17:02:21 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17XNtW-0006YP-00 for ; Wed, 24 Jul 2002 17:17:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17XNen-0003Dd-00; Wed, 24 Jul 2002 11:02:29 -0400 Original-Received: from pot.cnuce.cnr.it ([146.48.83.182]) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17XNeG-0003BZ-00 for ; Wed, 24 Jul 2002 11:01:56 -0400 Original-Received: from pot by pot.cnuce.cnr.it with local (Exim 3.35 #1 (Debian)) id 17XNeD-0007hK-00; Wed, 24 Jul 2002 17:01:53 +0200 Original-To: Debian Bug Tracking System X-Debbugs-CC: Francesco Potorti` 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:6011 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:6011 Package: gdb Version: 5.2.cvs20020401-6 Severity: normal While running Emacs under gdb, it got a SIGPIPE (this is the consequence of an unknown bug in Emacs). The debugger then showed this backtrace: 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) which made me think that the stack was smashed, so I continued the process, expecting to see it abort. Instead, it continued and Emacs went on, handling the problem by itself. In similar conditions, Emacs later on crashed, but not this time. Richard Stallman thus commented this information: It looks to me like GDB has got confused by some legitimate stack contents. Perhaps the `write' function does not set up a normal stack frame. It would be good to change GDB to handle what `write' actually does on the stack. So I am writing this bug report, however poor of information it may be. -- System Information Debian Release: 3.0 Kernel Version: Linux pot.cnuce.cnr.it 2.4.18 #1 Fri May 17 13:44:40 CEST 2002 i686 unknown Versions of the packages gdb depends on: ii libc6 2.2.5-10 GNU C Library: Shared libraries and Timezone ii libncurses5 5.2.20020112a- Shared libraries for terminal handling ii libreadline4 4.2a-5 GNU readline and history libraries, run-time