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
Segfault on weird but plain Perl in eval on 5.10.0 on Windows #9503
Comments
From ebhanssen@cpan.orgCreated by ebhanssen@cpan.org While tracking down the reasons for Test-Trap FAIL reports from perl -le "eval q{ BEGIN{*CORE::GLOBAL::exit=sub{print q{Passed}}}if(fork){wait;exit}else{*CORE::GLOBAL::exit=sub{print q{Okay}};exit;CORE::exit()} }" It passes on Unix with 5.8.8 or 5.10.0. It passes with ASPerl 5.8.8 and Cygwin perl 5.8.8. I don't have a Strawberry perl installation, but chorny was helpful It passed with Strawberry perl 5.8.8. It segfaulted with Strawberry perl 5.10.0. I do know know if this is specific to Strawberry perl, or if it (I expect the code sample can be reduced further -- the prints are Thanks, Perl Info
|
From @steve-m-hayOn Tue Sep 30 12:46:44 2008, ebhanssen@cpan.org wrote:
Thanks for the report. The bug is still present in bleadperl, and can be reduced to this: perl -eeval(q{if(!fork){exit}}) That crashes in perl-5.8.9 and perl-5.10.0, but not in perl-5.8.8. (All |
The RT System itself - Status changed from 'new' to 'open' |
From @steve-m-hayOn Thu May 28 01:20:39 2009, shay wrote:
Here's the stack trace from bleadperl:
The isIDFIRST_lazy(name) call causes the crash: name is okay (that's |
From @nwc10Dave notes: crashes on 5.10.0 win32; okay on 5.8.8 or 5.10.0 unix |
From @steve-m-hayOn Thu May 28 04:02:39 2009, shay wrote:
I've tracked down the change that caused this bug: http://perl5.git.perl.org/perl.git/commitdiff/7c4baf4 |
From @steve-m-haySee also 58468. |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#59498 (status was 'resolved')
Searchable as RT59498$
The text was updated successfully, but these errors were encountered: