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
panic: magic_killbackrefs during global destruction. #7174
Comments
From @jlokierCreated by @jlokierThe following test case causes Perl to write "panic: The bug is sensitive to the number of variables in the environment, As this bug is so sensitive to the exact number of entries in the If the bug doesn't show with the current development version, the only Unfortunately I was unable to reduce it smaller than 6 small files. --- START OF SHELL SCRIPT WHICH UNPACKS FILES --- cat <<'END' >environ cat <<'END' >bug.pl cat <<'END' >bug1.pl cat <<'END' >bug3.pm cat <<'END' >bug4.pm --- END OF SHELL SCRIPT WHICH UNPACKS FILES --- Perl Info
|
From @iabynOn Sun, Mar 14, 2004 at 07:50:20AM -0000, Jamie Lokier wrote:
Hmm, I can't reproduce it here with any of the 5.8.x perls nor any of the I know that some bugs have been fixed recently relating to weak refs Dave. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @jlokierDave Mitchell via RT wrote:
To make the test case, I started with a large program which triggered That is, I'd delete one statement, and it would go away. I'd To reduce the program, I used a tiny script which appended "$x=1;\n" Then I deleted whole functions from the original program and ran that Eventually I got close to what you have in the bug report, except that Then I decided to trim those files some more, and see if I could When I copied the files from my test machine to the machine where I So the bug appears to be highly sensitive to numbers of something. If possible, I recommend installing Red Hat 9 i386 with all current Maybe you will have luck running it under a memory debugger -- perhaps
If it's thread related, note that Red Hat 9 and Red Hat 7.2 have -- Jamie |
From nick.ing-simmons@elixent.comJamie Lokier <perl5-porters@perl.org> writes:
Which is known to have a number of Unicode oddities, but I can't
|
From nick.ing-simmons@elixent.comDave Mitchell <davem@fdisolutions.com> writes:
If you perforce access then you could try getting the p4 sync //depot/maint-5.8/...@18379 Which is what I think RedHat's MAINT18379 "locally applied patch"
|
From @smpeters
Similarly to when this ticket was opened, I've been unable to reproduce |
@smpeters - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#27630 (status was 'resolved')
Searchable as RT27630$
The text was updated successfully, but these errors were encountered: