Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upSegmentation fault while parsing incorrect code #14438
Comments
This comment has been minimized.
This comment has been minimized.
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 |
This comment has been minimized.
This comment has been minimized.
From @jkeenanOn Thu Jan 22 06:15:40 2015, crux wrote:
Confirmed; see attachment. -- |
This comment has been minimized.
This comment has been minimized.
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): |
This comment has been minimized.
This comment has been minimized.
The RT System itself - Status changed from 'new' to 'open' |
This comment has been minimized.
This comment has been minimized.
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 |
This comment has been minimized.
This comment has been minimized.
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 |
This comment has been minimized.
This comment has been minimized.
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? -- |
This comment has been minimized.
This comment has been minimized.
From @cpansproutFixed in 2f465e0. -- Father Chrysostomos |
This comment has been minimized.
This comment has been minimized.
@cpansprout - Status changed from 'open' to 'resolved' |
This comment has been minimized.
This comment has been minimized.
@cpansprout - Status changed from 'resolved' to 'pending release' |
This comment has been minimized.
This comment has been minimized.
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? |
This comment has been minimized.
This comment has been minimized.
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 |
This comment has been minimized.
This comment has been minimized.
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 -- |
This comment has been minimized.
This comment has been minimized.
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#123652 (status was 'resolved')
Searchable as RT123652$