|Subject:||Ctrl+C reliably triggers crash in perl.exe interpreter|
In every version of Strawberry Perl that I have ever tried, I can easily induce the interpreter to crash simply by invoking perl.exe with no arguments and pressing Ctrl+C. Consider the attached screenshot. This shows 17 invocations, of which 11 crashed after pressing Ctrl+C. These 11 cases are easily distinguished by the absence of any message being printed prior to the next prompt, with the sole exception of one crash which was accompanied by a rather unexpected "Out of memory!" message. What is also curious is that - where SIGINT is trapped and the interpreter exits cleanly - the message "Terminating on signal SIGINT(2)" will occasionally appear twice, instead of just once. At present, I am running the 64-bit build of v5.24.0 on Windows 10 build 1607. However, I recall running into the same problem at least two years ago, at which time I was running Windows 8.1 Update 1. I have not tested the 32-bit build. The following message is an excerpt from the event log. I realise that it's not very informative but I don't know how to get a proper trace. Faulting application name: perl.exe, version: 184.108.40.206, time stamp: 0x57323a0d Faulting module name: perl524.dll, version: 0.0.0.0, time stamp: 0x573239d2 Exception code: 0xc0000005 Fault offset: 0x0000000000088c48 Faulting process id: 0x1848 Faulting application start time: 0x01d1ef661806a176 Faulting application path: C:\Strawberry\perl\bin\perl.exe Faulting module path: C:\Strawberry\perl\bin\perl524.dll Report Id: 4207d706-9152-4c03-9d43-b43a5685cc36 Faulting package full name: Faulting package-relative application ID: If I recall correctly, the signal may also crash programs that are performing real work but I forget the details at this juncture. In any case, this issue prevents me from being able to take Strawberry seriously as a usable runtime.