From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
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 09:14:30 +0200 [thread overview]
Message-ID: <83cz9cygbt.fsf@gnu.org> (raw)
In-Reply-To: <87r0xt1925.fsf@yahoo.com> (message from Po Lu on Thu, 24 Nov 2022 08:37:54 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: German Pacenza <germanp82@hotmail.com>, 59452@debbugs.gnu.org
> Date: Thu, 24 Nov 2022 08:37:54 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > FTR, I didn't see any crashes, only an error message in the echo-area. But
> > I'm not on PGTK.
>
> The crash is specific to builds with GLib, where event handlers must not
> be allowed to signal.
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.
next prev parent reply other threads:[~2022-11-24 7:14 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 [this message]
2022-11-24 10:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83cz9cygbt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59452@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.