[Python-Dev] Signals, threads, blocking C functions (original) (raw)
Adam Olsen rhamph at gmail.com
Sat Sep 9 06:59:48 CEST 2006
- Previous message: [Python-Dev] Signals, threads, blocking C functions
- Next message: [Python-Dev] Signals, threads, blocking C functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/8/06, Adam Olsen <rhamph at gmail.com> wrote:
Ensuring modifications to that array are atomic would be tricky, but I think it would be doable if we use a read-copy-update approach (with two alternating signal handler functions). Not sure how to ensure there's no currently running signal handlers in another thread though. Maybe have to rip the atomic read/write stuff out of the Linux sources to ensure it's always defined behavior.
Doh, except that's exactly what sig_atomic_t is for. Ah well, can't win them all.
-- Adam Olsen, aka Rhamphoryncus
- Previous message: [Python-Dev] Signals, threads, blocking C functions
- Next message: [Python-Dev] Signals, threads, blocking C functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]