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
$_[0] seems to get reused inappropriately #9166
Comments
From schmorp@schmorp.deCreated by schmorp@schmorp.deHi! I cannot provide a testcase for this bug. I can only provide a description If you can't, do not hesitate to just close this bug. (I might re-try with 5.10 which I plan to install soon, but I will likely In any case, in a fairly complex (perl-wise) program, I added a Bizarre copy of ARRAY in sassign at /opt/perl/lib/perl5/Carp/Heavy.pm line 104. I prepended this code to the cluck call: for(1..10) { And got the following output: http://ue.tst.eu/7b8f67644b1cfc209f013991fac35a30.txt Note the double :: in "4". Digging with gdb showed that carp indeed tried SV = NULL(0x0) at 0x202e570 (which is not an array..., so maybe I was wrong - unfortunately gcc Now, this is during a hide method call. The hide method in question # sv_dump simply calls sv_dump (SvROK (arg) ? SvRV (arg) : arg); $self->{parent}->remove ($self) background: $self is a widget, $self->{parent} is a widget, and a side effect delete $child->{parent}; # $child == the above $self Also, $self->{parent} is a weak reference, so I do not get an unwanted When I use sv_dump on $self->{parent}, I get this: SV = PVLV(0x9c80f8) at 0x1951b50 ... This is the $self->{parent} scalar that later goes "missing". When I reformulate the hide method to: if (my $parent = $self->{parent}) { then I no longer get any crash. My theory is that somehow, $_[0] is not correctly being refcounted, or I must admit my knowledge of weak references is not too good, and I cannot My hope is that somebody else can pinpoint the bug or at least come up And again, feel free to close this report if no solution is forthcoming. Perl Info
|
From @jkeenanOn Wed Dec 26 12:09:18 2007, schmorp@schmorp.de wrote:
Well, no solution has been forthcoming in the 4+ years since this ticket I recommend that we close this ticket unless we can get a report of a Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Sat Sep 01 16:29:42 2012, jkeenan wrote:
This is bug #52610. -- Father Chrysostomos |
Migrated from rt.perl.org#49115 (status was 'open')
Searchable as RT49115$
The text was updated successfully, but these errors were encountered: