Skip Menu |
 

This queue is for tickets about the Perl-Dist-Strawberry CPAN distribution.

Report information
The Basics
Id: 116746
Status: open
Priority: 0/
Queue: Perl-Dist-Strawberry

People
Owner: Nobody in particular
Requestors: kfm [...] plushkava.net
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)



Subject: Ctrl+C reliably triggers crash in perl.exe interpreter
Download (untitled) / with headers
text/plain 1.7k
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: 5.24.0.1, 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.
Subject: strawberry-sigint-crashes.PNG
strawberry-sigint-crashes.PNG
Subject: Re: Ctrl+C reliably triggers crash in perl.exe interpreter
From: kfm [...] plushkava.net
Attaching screenshot of crash dialog.
Subject: perl-interpreter-crash-dialog.PNG
perl-interpreter-crash-dialog.PNG
Subject: Re: [rt.cpan.org #116746] Ctrl+C reliably triggers crash in perl.exe interpreter
Date: Sat, 6 Aug 2016 21:39:46 +0200
To: bug-Perl-Dist-Strawberry [...] rt.cpan.org
From: kmx <kmx [...] volny.cz>
Download (untitled) / with headers
text/plain 250b
Hello Kerin, I am afraid this issue is more related to perl core than specifically to strawberry perl. Therefore it might be a better idea to discuss this issue in perl5porters mailing list or to create perl core's bug report via perlbug -- kmx
Subject: Re: [rt.cpan.org #116746] Ctrl+C reliably triggers crash in perl.exe interpreter
Date: Sat, 6 Aug 2016 22:17:15 +0100
To: bug-Perl-Dist-Strawberry [...] rt.cpan.org
From: Kerin Millar <kfm [...] plushkava.net>
Download (untitled) / with headers
text/plain 580b
On Sat, 6 Aug 2016 15:40:10 -0400 "kmx via RT" <bug-Perl-Dist-Strawberry@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=116746 > > > Hello Kerin, > > I am afraid this issue is more related to perl core than specifically to > strawberry perl. > > Therefore it might be a better idea to discuss this issue in perl5porters > mailing list or to create perl core's bug report via perlbug
Indeed, I tried the ActiveState distribution last night and ran into exactly the same problem. I'll report the matter with perlbug, as suggested. Thank you. --Kerin


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.