|
| From: | Paul Eggert |
| Subject: | Re: Some experience with the igc branch |
| Date: | Sun, 29 Dec 2024 11:09:47 -0800 |
| User-agent: | Mozilla Thunderbird |
On 12/28/24 21:47, Eli Zaretskii wrote:
Yes, that's the purpose of the global lock: a Lisp thread can only run if it acquires the lock.
OS signals are therefore ignored if a non-main Lisp thread is buggy and holds that global lock indefinitely. I assume this is the expected fallout from such a bug.
I don't see this issue documented explicitly in doc/elisp/threads.texi. Should it be?
| [Prev in Thread] | Current Thread | [Next in Thread] |