-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault while parsing incorrect code #14438
Comments
From thecrux@gmail.comGot interesting SIGSEGV case $ perl -e '$1=eval{a:}' SIGSEGV reproduced for Perl 5.16, 5.18, 5.20, blead. Perl 5.8.9 seems not affected When debugging enabled i've got SIGABRT instead of SIGSEGV $ perlbrew use perl-5.21.6-thr-dbg $(gdb) bt (gdb)frame 4 |
From @jkeenanOn Thu Jan 22 06:15:40 2015, crux wrote:
Confirmed; see attachment. -- |
From @jkeenan[perl] 88 $ ./perl -e '$1=eval{a:}' [perl] 89 $ gdb --args ./perl -e '$1=eval{a:}' Program received signal SIGABRT, Aborted. Summary of my perl5 (revision 5 version 21 subversion 9) configuration: Characteristics of this binary (from libperl): |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Thu Jan 22 06:15:40 2015, crux wrote:
5.21.4 is unaffected. 5.14.4 crashes. Your subject is slightly wrong. The code is not invalid. (It just dies at run time because $1 is read-only.) You can have a label at the end of a block. I’ll run a bisect. -- Father Chrysostomos |
From @cpansproutOn Thu Jan 22 21:56:06 2015, sprout wrote:
$ ../perl.git/Porting/bisect.pl --target=miniperl --start=v5.12.0 --end=v5.14.4 -e 'eval{$1=eval{a:}}' refactor and regularise label/statement grammar -- Father Chrysostomos |
From @jkeenanOn Thu Jan 22 21:56:06 2015, sprout wrote:
So, can we have the attempt to assign to $1 throw a more tidy exception? -- |
From @cpansproutFixed in 2f465e0. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
@cpansprout - Status changed from 'resolved' to 'pending release' |
From thecrux@gmail.comOn Sat, Jan 24, 2015 at 05:23:34PM -0800, Father Chrysostomos via RT wrote:
Great, thank you. Whether this fix will be ported to stable 5.20 branch? |
From @steve-m-hayOn Sat Jan 24 23:39:31 2015, crux wrote:
It looks like a suitable candidate for backporting, so I've just added it to the voting file, and it will be in 5.20.2 if a couple of other committers agree: http://perl5.git.perl.org/perl.git/commit/f10d2881c7 |
From @khwilliamsonThanks for submitting this ticket The issue should be resolved with the release today of Perl v5.22, available at http://www.perl.org/get.html -- |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#123652 (status was 'resolved')
Searchable as RT123652$
The text was updated successfully, but these errors were encountered: