[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#60144: 30.0.50; PGTK Emacs crashes after signal
From: |
Po Lu |
Subject: |
bug#60144: 30.0.50; PGTK Emacs crashes after signal |
Date: |
Sun, 18 Dec 2022 14:22:04 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
> You cannot require that from note_mouse_highlight, since it looks up
> text and overlay properties, and those can signal an error if the
> position is outside the valid/reachable range of buffer positions.
How about simply wrapping those calls in
internal_catch_all/internal_condition_case?
> Do you understand why note_mouse_highlight was called in this
> scenario? The backtrace seems strange: why should GTK care about our
> mouse highlight?
What happens here is that Emacs is reading input through GTK, either
inside xg_select or the read_socket_hook. GTK then detects some mouse
motion and calls the motion event handler for the frame's widget, which
in turn calls note_mouse_movement.
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Karl Otness, 2022/12/16
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Po Lu, 2022/12/17
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Eli Zaretskii, 2022/12/18
- bug#60144: 30.0.50; PGTK Emacs crashes after signal,
Po Lu <=
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Eli Zaretskii, 2022/12/18
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Po Lu, 2022/12/18
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Eli Zaretskii, 2022/12/18
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Po Lu, 2022/12/18
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Eli Zaretskii, 2022/12/18
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Po Lu, 2022/12/18
- bug#60144: 30.0.50; PGTK Emacs crashes after signal, Eli Zaretskii, 2022/12/18