[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6
From: |
Eli Zaretskii |
Subject: |
bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6 |
Date: |
Thu, 24 Nov 2022 09:14:30 +0200 |
> 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.
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, German Pacenza, 2022/11/21
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, Po Lu, 2022/11/21
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, German Pacenza, 2022/11/22
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, Po Lu, 2022/11/22
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, German Pacenza, 2022/11/23
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, Eli Zaretskii, 2022/11/23
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, German Pacenza, 2022/11/23
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, Eli Zaretskii, 2022/11/23
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, Po Lu, 2022/11/23
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6,
Eli Zaretskii <=
- bug#59452: 29.0.50; [PGTK] SIGSEV Args out of range: 6, 6, Po Lu, 2022/11/24