Custom Query (1030 matches)
Results (427 - 429 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #879 | fixed | Exceptions occur at the time of a disconnection | ||
| Description |
On Win32 (Windows XP SP3), it seems CCL r14647 and later cause exceptions at the time of a disconnection. This is the quote from *inferior-lisp* buffer: %eax = 0x00000001 %ecx = 0x77bdc2e3 %edx = 0x00570608 %ebx = 0x012bb2b8 %esp = 0x015af510 %ebp = 0x015af528 %esi = 0x7ffaee88 %edi = 0x012bd320 %eip = 0x00026612 %eflags = 0x00010246 %cs = 0x001b %ds = 0x0023 %ss = 0x0023 %es = 0x0023 %fs = 0x003b %gs = 0x0000 Exception on foreign stack %eax = 0x012b8998 %ecx = 0x015aee98 %edx = 0x00000001 %ebx = 0x7ffaee88 %esp = 0x015aeed0 %ebp = 0x015aeee8 %esi = 0x7ffdce88 %edi = 0x00000000 %eip = 0x00027255 %eflags = 0x00010287 %cs = 0x001b %ds = 0x0023 %ss = 0x0023 %es = 0x0023 %fs = 0x003b %gs = 0x0000 Exception on foreign stack ... Can I ignore it? |
|||
| #688 | invalid | ignore-errors doesn't | ||
| Description |
The following sequence of events produces a memory fault and a trip to a nonfunctioning debugger. (load "jpeg.lisp") ;supplied (jpeg::read-file "128.jpg") ;also supplied If you wrap the latter in ignore-errors, you still get the trip to the debugger. I tried this in the windows 32 bit 1.5 release as well as in the linux x86 64bit trunk (checked out as of this morning). |
|||
| #701 | fixed | kernel crash in 64 bit trunk build under 64 bit linux while gc'ing after creating large vector | ||
| Description |
I just checked all active tickets and didn't see any report like this. I also updated to the trunk and rebuilt to make sure this bug still exists there. (setq *print-array* nil) (setq foo (make-array 1000000000)) (length foo) (setq foo nil) 1 2 3 4 (gc) (the extra expressions/values were to get rid of pointers to the vector in *, and *) results in a sigsegv! |
|||
