From: Matthew S. <mts...@gm...> - 2015-05-26 23:56:28
|
I just did a couple test builds, and it looks like this issue was introduced somewhere between 1.2.8 and 1.2.9. I won't be able to do a proper bisect tonight, but I might be able to get one sometime tomorrow. -Matt Stickney On Tue, May 26, 2015 at 7:35 PM, Matthew Stickney <mts...@gm...> wrote: > I'm not sure if this is the sort of regression that ought to be fixed > before the next release, but I've just noticed a problem in 32-bit > builds on windows. > > As of 1.2.11, running a 32-bit sbcl in a console window and pressing > ctrl-c causes the SB-SYS:INTERACTIVE-INTERRUPT condition to be > signalled, the debugger is entered, and shortly thereafter sbcl > crashes. The delay between entering the debugger and crashing varies a > little; the error occurs on both 32-bit and 64-bit windows installs, > and does not occur with 64-bit 1.2.11 sbcl build; and the error also > doesn't occur if I run it in a msys console (just in the native > windows console), which makes me think it has to do with signal > handling on windows. > > This wasn't an issue in the previous windows build, 1.2.7, and is > still an issue with current master. I haven't tried to track down a > more precise version for the error yet, and I don't have any useful > logs or anything; I'm happy to supply them if somebody can tell me how > to generate them. > > -Matt Stickney |