in reply to Re^6: "Thread already joined at..." and "A thread exited while x threads were running" errors
in thread "Thread already joined at..." and "A thread exited while x threads were running" errors

That was XP/ActiveState 810, and I get the same results with my home-built 5.8.5. 

P:\test>perl -v

This is perl, v5.8.4 built for MSWin32-x86-multi-thread
(with 3 registered patches, see perl -V for more detail)

Copyright 1987-2004, Larry Wall

Binary build 810 provided by ActiveState Corp. http://www.ActiveState.
+com
ActiveState is a division of Sophos.
Built Jun  1 2004 11:52:21

[download]

I'm not sure what to suggest. There is no obvious reason why 2K would be the cause of failure.

Post the -V (not -v as above) from your copy of perl...maybe something will show up?

Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon
  • Comment on Re^7: "Thread already joined at..." and "A thread exited while x threads were running" errors
  • Download Code

Replies are listed 'Best First'.
Re^8: "Thread already joined at..." and "A thread exited while x threads were running" errors
by nickos (Initiate) on Sep 07, 2004 at 13:41 UTC

    Here we go:

    C:\benchmarker>perl -V
    Summary of my perl5 (revision 5 version 8 subversion 4) configuration:
  Platform:
    osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread
    uname=''
    config_args='undef'
    hint=recommended, useposix=true, d_sigaction=undef
    usethreads=undef use5005threads=undef useithreads=define usemultip
+licity=define
    useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
    use64bitint=undef use64bitall=undef uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='cl', ccflags ='-nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 -D
+_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT  -DNO_HASH_SEED -DPERL_IMPLICI
+T_CONTEXT -DPERL_IMPLICIT_SYS -DUSE_PERLIO -DPERL_MSVCRT_READFIX',
    optimize='-MD -Zi -DNDEBUG -O1',
    cppflags='-DWIN32'
    ccversion='', gccversion='', gccosandvers=''
    intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
    d_longlong=undef, longlongsize=8, d_longdbl=define, longdblsize=10
    ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='__int64
+', lseeksize=8
    alignbytes=8, prototype=define
  Linker and Libraries:
    ld='link', ldflags ='-nologo -nodefaultlib -debug -opt:ref,icf  -l
+ibpath:"C:\Perl\lib\CORE"  -machine:x86'
    libpth=C:\PROGRA~1\MICROS~3\VC98\lib
    libs=  oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib
+  comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib  netap
+i32.lib uuid.lib wsock32.lib mpr.lib winmm.lib  version.lib odbc32.li
+b odbccp32.lib msvcrt.lib
    perllibs=  oldnames.lib kernel32.lib user32.lib gdi32.lib winspool
+.lib  comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib  n
+etapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib  version.lib odbc3
+2.lib odbccp32.lib msvcrt.lib
    libc=msvcrt.lib, so=dll, useshrplib=yes, libperl=perl58.lib
    gnulibc_version='undef'
  Dynamic Linking:
    dlsrc=dl_win32.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
    cccdlflags=' ', lddlflags='-dll -nologo -nodefaultlib -debug -opt:
+ref,icf  -libpath:"C:\Perl\lib\CORE"  -machine:x86'


Characteristics of this binary (from libperl):
  Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL
+_IMPLICIT_CONTEXT PERL_IMPLICIT_SYS
  Locally applied patches:
        ActivePerl Build 810
        22751 Update to Test.pm 1.25
        21540 Fix backward-compatibility issues in if.pm
  Built under MSWin32
  Compiled at Jun  1 2004 11:52:21
  @INC:
    C:/Perl/lib
    C:/Perl/site/lib
    .

    [download]

    Thanks for all the help so far BTW.

[reply]
[d/l]

      Nope, that's identical to mine. Do you have access to another box with perl installed? XP maybe?

      Examine what is said, not who speaks.
      "Efficiency is intelligent laziness." -David Dunham
      "Think for yourself!" - Abigail
      "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon
[reply]
[d/l]

        No, I'm afraid not - and the finished script will need to be able to run on Win2k amongst others.

        What else could be causing the problem? If there was a general problem with threads with Perl on Win2k it would be reasonably well known wouldn't it? It's not like I'm not doing anything really complicated. I'm stumped :(

        What should I do next? Perhaps I should reduce the code to the bare minimum that causes this problem and post it to a more general place...

[reply]

In Section Seekers of Perl Wisdom