Package: clisp Version: 1:2.43-2 Starting an interactive CLISP session in a gnome-terminal window and then closing the said window causes the CLISP process to start consuming 100% CPU.
Stracing the process highlights a number of segfaults along the lines of:
mmap(0x333e43000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x333e43000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
mprotect(0x333cf8000, 4096, PROT_READ|PROT_WRITE) = 0
rt_sigreturn(0x333cf8000) = 13754138688
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
mprotect(0x333cf9000, 4096, PROT_READ|PROT_WRITE) = 0
rt_sigreturn(0x333cf9000) = 13754142840
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
mprotect(0x333d37000, 4096, PROT_READ|PROT_WRITE) = 0
rt_sigreturn(0x333d37000) = 13754397368
(etc.)
I can reproduce on i386 and amd64 machines.
Regards,
--
Chris Lamb, UK [EMAIL PROTECTED]
GPG: 0x634F9A20
signature.asc
Description: PGP signature
