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
Loading Data::Dumper corrupts PL_sv_yes, or changes semantics of !0 at the least #12397
Comments
From @demerphqCreated by @demerphqThis is a bug report for perl from demerphq@gmail.com, ----------------------------------------------------------------- The aritificially high REFCNT demonstrates that we get PL_sv_yes and $ ~/bleadperl/bin/perl5.17.4 -MDevel::Peek -le'Dump(sub{ \@_ }->(!1, Now we load Data::Dumper first, and we see that the !0 case magically changes: $ ~/bleadperl/bin/perl5.17.4 -MDevel::Peek -MData::Dumper A closer inspection of both: Shows that other than the refcount and the fact that it is no longer sv == &PL_sv_yes which stops happening if DD is loaded early. Full Devel::Peek output is here: $ ~/bleadperl/bin/perl5.17.4 -MDevel::Peek -le'Dump(sub{ \@_ }->(!1, !0))' Perl Info
|
From @demerphqOn 11 September 2012 12:09, yves orton <perlbug-followup@perl.org> wrote:
I can reduce this down further and eliminate Data::Dumper: $ ~/bleadperl/bin/perl5.17.4 -MDevel::Peek -le'BEGIN { Dump(sub{ \@_ I have no idea what is going on. This only happens under threads. Cheers, -- |
From @cpansproutOn Tue Sep 11 03:25:41 2012, demerphq wrote:
If you show the full Devel::Peek output, you will see that the immortals There is this awful piece of code in op.c:S_finalize_op: case OP_CONST: See also -- Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutFixed in 82b84d0. -- Father Chrysostomos |
From [Unknown Contact. See original ticket]Fixed in 82b84d0. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#114838 (status was 'resolved')
Searchable as RT114838$
The text was updated successfully, but these errors were encountered: