#55: blocked signals --------------------------------+------------------------------------------- Reporter: heller | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: Core | Version: 20c Keywords: signals interrupts | --------------------------------+------------------------------------------- I think there is a problem related to blocked signals and garbage collection:

1. Start {{{cmucl -noinit -eval '(loop (ext:gc :full t))'}}} in a terminal and let it run.

2. Under Linux, {{{cat /proc/<pid>/status}}} shows that !SigBlk is 0 i.e. no signals are blocked.

3. Interrupt the loop with C-c (SIGINT) and wait for the debugger.

4. !SigBlk is still 0.

5. Type c to continue the loop.

6. !SigBlk is now 000000001fc90000

That's a bug, right? It should again be zero.

The problem doesn't occur if the loop is empty, so I figure this has something to do with GC.