-
Notifications
You must be signed in to change notification settings - Fork 529
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
Fwd: [rt.cpan.org #124722] NULL pointer dereference in Perl_runops_standard #16457
Comments
From bug-Perl-Core@rt.cpan.orgThis is forward of transaction #1775448 of a ticket #124722 |
From bug-Perl-Core@rt.cpan.orgMessage RFC822: /perl-5.27.9/perl -le 'BEGIN{$SIG{DIE} =sub{exit(0)}}unshift' ==95151==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000000abccbd bp 0x00000119cb28 sp 0x7ffdbda5a550 T0) AddressSanitizer can not provide additional info. |
From bug-Perl-Core@rt.cpan.org/perl-5.27.9/perl -le 'BEGIN{$SIG{__DIE__} =sub{exit(0)}}unshift' ==95151==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000000abccbd bp 0x00000119cb28 sp 0x7ffdbda5a550 T0) AddressSanitizer can not provide additional info. |
From @iabynOn Thu, Mar 08, 2018 at 12:51:53AM -0800, via RT wrote:
The unshift is a syntax error, so compilation triggers the __DIE__ I don't think its a security issue, as it involves feeding code with I'm not very confident about how to fix it though: the whole exit In particular, in perl_parse() there is this: case 2: #2754 is: From a CHECK{}, you cannot exit(0) which had a fix from Zefram in Dec 2017, which was reverted because |
The RT System itself - Status changed from 'new' to 'open' |
From @tonycozOn Thu, 08 Mar 2018 03:39:36 -0800, davem wrote:
I agree, now public. Tony |
From zefram@fysh.orgDave Mitchell wrote:
It *was* fixed in 5.27.7, as part of [perl #2754]. 5.27.7 doesn't crash -zefram |
I believe this is fixed as of Perl 5.37.4. Likely by 375d68c |
Bisect said it was 197bb3f |
Migrated from rt.perl.org#132953 (status was 'open')
Searchable as RT132953$
The text was updated successfully, but these errors were encountered: