Your message dated Sun, 03 Aug 2025 16:47:53 -0400
with message-id <[email protected]>
and subject line Closing bug
has caused the Debian Bug report #154154,
regarding gdb: bad backtrace with interrupted write call
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
154154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=154154
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
This bug is more than 20 years old; GDB has been almost completely
rewritten since then, and I don't recall seeing a similar problem
recently.
I'm taking the liberty to close this bug. Feel free reopen if it's
still applicable.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
signature.asc
Description: PGP signature
--- End Message ---
