From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: germanp82@hotmail.com, 59452@debbugs.gnu.org
Subject: bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6
Date: Thu, 24 Nov 2022 18:37:00 +0800 [thread overview]
Message-ID: <87y1s0zlir.fsf@yahoo.com> (raw)
In-Reply-To: <83cz9cygbt.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Nov 2022 09:14:30 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> If these handlers run Lisp or call primitives or their subroutines, it's a
> tough requirement, which is almost impossible to fulfill. The resulting
> build will be very fragile. Emacs internals signal errors all over the
> place. You could catch errors via internal_condition_case_* etc., but doing
> so will sometimes trigger an infinite loop of errors, and make Emacs
> unresponsive.
Well, we will just have to try our best. GLib gained this limitation
several years ago, and I've only seen two crash reports because of it up
until now.
prev parent reply other threads:[~2022-11-24 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 18:46 bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6 German Pacenza
2022-11-22 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-22 13:48 ` German Pacenza
2022-11-23 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-23 11:58 ` German Pacenza
2022-11-23 14:20 ` Eli Zaretskii
2022-11-23 14:52 ` German Pacenza
2022-11-23 15:17 ` Eli Zaretskii
2022-11-24 0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-24 7:14 ` Eli Zaretskii
2022-11-24 10:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87y1s0zlir.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59452@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=germanp82@hotmail.com \
--cc=luangruo@yahoo.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).