[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: usr1-signal, usr2-signal, etc.
From: |
Richard Stallman |
Subject: |
Re: usr1-signal, usr2-signal, etc. |
Date: |
Tue, 05 Dec 2006 19:46:38 -0500 |
I'm concerned about the case that kbd_buffer_store_event_hold is
called from the signal-handler context while it is also executed in
the normal context. This has already existed for SIGUSR1 and SIGUSR2
before your change, though.
Since people hardly ever use SIGUSR1 and SIGUSR2,
a bug that happens only a small fraction of the time when they
are called might never have happened. But if it happens for
signals that are more common, it will start to occur.
So it is good that you noticed this.
We should fix it now.
- Re: usr1-signal, usr2-signal, etc., (continued)
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/13
- Re: usr1-signal, usr2-signal, etc., YAMAMOTO Mitsuharu, 2006/12/14
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/14
- Re: usr1-signal, usr2-signal, etc., Chong Yidong, 2006/12/18
- Re: usr1-signal, usr2-signal, etc., YAMAMOTO Mitsuharu, 2006/12/18
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/19
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/19
- Re: usr1-signal, usr2-signal, etc., Richard Stallman, 2006/12/20
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/20
- Re: usr1-signal, usr2-signal, etc., Richard Stallman, 2006/12/12
- Re: usr1-signal, usr2-signal, etc.,
Richard Stallman <=
- Re: usr1-signal, usr2-signal, etc., Johan Bockgård, 2006/12/06