-
Notifications
You must be signed in to change notification settings - Fork 559
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: deadlock occured on creation of a thread while joining others #8608
Comments
From [email protected]Created by [email protected]There seems to be a potential deadlock situation on creating a new Perl5.9.4 is much robust, but it rarely failed with SEGV when the IKEGAMI, Tsutomu ----- 8< ---------- 8< ----- snip, snip ----- 8< ---------- 8< ----- my $flag : shared = 1; my (@b, @d); for (1..N) { for (1..N) { { ----- >8 ---------- >8 ----- snip, snip ----- >8 ---------- >8 ----- ----- >8 ---------- >8 ----- snip, snip ----- >8 ---------- >8 ----- Perl Info
|
From [email protected]Tsutomu IKEGAMI reported:
I was not able to reproduce the problem using ActivePerl 5.8.8 It would be helpful to know if you can repeat this problem using the If deadlock occurs with 1.42, gdb stack traces would be helpful.
I was able to use N=50 under ActivePerl, N=350 (!) under Cyginw __________________________________________________ |
The RT System itself - Status changed from 'new' to 'open' |
From @HugmeirOn Fri Sep 22 08:20:59 2006, jdhedden@yahoo.com wrote:
I can reproduce the deadlock on 5.8.8, but not on anything newer; I even --hugmeir |
From @jkeenanOn Fri May 25 16:36:02 2012, Hugmeir wrote:
When I built a threaded perl on the Dromedary server and then tried out ######### |
From @jkeenan$ ./perl -Ilib -V Characteristics of this binary (from libperl): |
From @jkeenan |
Migrated from rt.perl.org#40382 (status was 'open')
Searchable as RT40382$
The text was updated successfully, but these errors were encountered: