GNU bug report logs - #71177
30.0.50; crash when opening and closing many TTY frames in succession

Previous Next

Full log

Message #17 received at 71177 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Daniel Clemente <n142857 <at> gmail.com>
Cc: luangruo <at> yahoo.com, 71177 <at> debbugs.gnu.org
Subject: Re: bug#71177: 30.0.50; crash when opening and closing many TTY
 frames in succession
Date: Sat, 25 May 2024 15:43:24 +0300

merge 71177 71176
thanks

> From: Daniel Clemente <n142857 <at> gmail.com>
> Date: Sat, 25 May 2024 11:04:39 +0000
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 71177 <at> debbugs.gnu.org
> 
> > That's a red herring.  It's because Daniel is running Emacs under GDB
> > that his backtrace ends with a SIGPIPE, while the backtrace for the
> > crash lies elsewhere.
> 
> True, this was a SIGPIPE (still not a crash), and gdb was stopping here. By running "cont" I could make it
> continue.
> After running "handle SIGPIPE noprint pass", and continuing the same behaviour for ~30 seconds, I saw the
> real crash (SIGSEGV).
> 
> The cause of the crash is the other bug I reported, bug#71176 (tty-set-up-initial-frame-faces,
> face_at_buffer_position, default_face = 0x0), so I posted the new backtrace there.
> 
> So in here we just discovered that opening+closing frames is a way to reproduce bug#71176, but I think the
> bug is 71176 and this one can be closed.

OK, I'm merging them.

Previous Next

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