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
threads panic in del_backref #9979
Comments
From @jdheddenCreated by @jdheddenThe following: use threads; sub foo { my $bar = threads->create(\&foo)->join(); threads->create(sub { })->join(); produces: panic: del_backref during global destruction. This bug was introduced with change 34354 Once fixed, the following can be added to t/op/threads.t: # Test we don't get: Perl Info
|
From @obraThanks. Applied as 7c76c2a. On Tue 24.Nov'09 at 16:28:07 -0500, Jerry D. Hedden wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @jdhedden
It get trickier. With commit 789c461 |
From @nwc10On Wed, Nov 25, 2009 at 03:32:27PM -0500, Jerry D. Hedden wrote:
I can't re-create this on any platform I have access to (Linux, OS X, FreeBSD), Does this happen on any platform other than Cygwin? Is it sensitive to external factors? For example, the number of environment Nicholas Clark |
From @jdheddenJerry D. Hedden wrote:
It get trickier. With commit 789c461 Nicholas Clark wrote:
Yes. I can reproduce it with ActivePerl 5.10.1. |
From @obraOn Sat Nov 28 13:59:06 2009, jdhedden@cpan.org wrote:
At this point, should this issue still be blocking 5.12.0? |
From @jdheddenOn Tue, Dec 15, 2009 at 19:04, Jesse via RT <perlbug-followup@perl.org> wrote:
For that it's worth, my opinion is that this should be looked into and |
From @obraOn Wed, Dec 16, 2009 at 11:45:25AM -0500, Jerry D. Hedden wrote:
[resent with perlbug on cc list] I have absolutely no problem keeping it open. But it doesn't look like -- |
From @cpansproutThis was caused by change 34210/41fae7a, which simply reveals a bug A sub returned from a thread brings a lot of baggage with it, Then later on, under case SVt_PVGV: So what’s happening is that there is a glob with no back-reference in Attached is a patch to fix this, another one to remove the ‘TODO’ |
From @cpansprout |
From @cpansproutAttached is another, more reliable test for the original bug. On Dec 20, 2009, at 1:07 PM, Father Chrysostomos wrote:
|
From @cpansproutInline Patch--- blead-70748copy/t/op/threads.t 2009-12-20 12:39:51.000000000 -0800
+++ blead-70748copy2/t/op/threads.t 2009-12-20 14:29:00.000000000 -0800
@@ -16,7 +16,7 @@ BEGIN {
exit 0;
}
- plan(16);
+ plan(17);
}
use strict;
@@ -204,6 +204,15 @@ threads->create(sub { })->join();
print "ok";
EOI
+# Another, more reliable test for the same del_backref bug:
+fresh_perl_like(
+ <<' EOJ', qr/ok/, {}, 'No del_backref panic [perl #70748] (2)'
+ use threads;
+ push @bar, threads->create(sub{sub{}})->join() for 1...10;
+ print "ok";
+ EOJ
+);
+
# Simple closure-returning test: At least this case works (though it
# leaks), and we don't want to break it.
fresh_perl_like(<<'EOJ', qr/^foo\n/, {}, 'returning a closure'); |
From @rgarciaThanks, all applied as 27bca32. 2009/12/20 Father Chrysostomos <sprout@cpan.org>:
-- |
@rgs - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#70748 (status was 'resolved')
Searchable as RT70748$
The text was updated successfully, but these errors were encountered: