From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Clemente <n142857@gmail.com>
Cc: luangruo@yahoo.com, 71177@debbugs.gnu.org
Subject: bug#71177: 30.0.50; crash when opening and closing many TTY frames in succession
Date: Sat, 25 May 2024 15:43:24 +0300 [thread overview]
Message-ID: <865xv2yscz.fsf@gnu.org> (raw)
In-Reply-To: <CAJKAhPCu1M8oiV_x43uw51y1SKhKiZOnUvZrepApv34T6BoGQQ@mail.gmail.com> (message from Daniel Clemente on Sat, 25 May 2024 11:04:39 +0000)
merge 71177 71176
thanks
> From: Daniel Clemente <n142857@gmail.com>
> Date: Sat, 25 May 2024 11:04:39 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>, 71177@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.
prev parent reply other threads:[~2024-05-25 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 17:47 bug#71177: 30.0.50; crash when opening and closing many TTY frames in succession Daniel Clemente
2024-05-24 19:31 ` Eli Zaretskii
2024-05-25 0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25 11:04 ` Daniel Clemente
2024-05-25 12:43 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=865xv2yscz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71177@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=n142857@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).