perl on windows - possible bug?

[lililevy]

Hello,

I'm using perl58.dll (version 5.8.4, build 810) in a c++ application
with several threads that runs on win2000SP4.
Every thread creates a perl interpreter that runs a perl script from an
arbitrary file.
After a while I'm experiencing a deadlock.
I can see that I have a thread that is stack in the function
_alloc_osfhnd (Microsoft function from the msvcrt.dll that is called
from the _open function).

I found this link http://bugs.mysql.com/bug.php?id=12071 that describes
a Microsoft bug in _alloc_osfhnd that might cause this deadlock.

I can also see that in the perl source win32.c there's an
implementation to the function _alloc_osfhnd with the following
description, but I'm not sure it has something to do with my problem.

/*
* we fake up some parts of the CRT that aren't exported by MSVCRT.dll
* this lets sockets work on Win9X with GCC and should fix the problems
* with perl95.exe
* -- BKS, 1-23-2000
*/

Has anyone experienced this problem before?
Is it really a Microsoft bug that affects perl?
Can another version of perl solve the problem?
Can another version of OS solve the problem?

Thanks in advance,
Lily.

 

[Dr.Ruud]

(e-mail address removed) schreef:

I'm using perl58.dll (version 5.8.4, build 810) in a c++ application
with several threads that runs on win2000SP4.
Every thread creates a perl interpreter that runs a perl script from
an arbitrary file.
After a while I'm experiencing a deadlock.

Maybe the perl5.porters mailing list is a better place for this
question.

 

[Sisyphus]

Hello,

I'm using perl58.dll (version 5.8.4, build 810) in a c++ application
with several threads that runs on win2000SP4.
Every thread creates a perl interpreter that runs a perl script from an
arbitrary file.
After a while I'm experiencing a deadlock.
I can see that I have a thread that is stack in the function
_alloc_osfhnd (Microsoft function from the msvcrt.dll that is called
from the _open function).

I found this link http://bugs.mysql.com/bug.php?id=12071 that describes
a Microsoft bug in _alloc_osfhnd that might cause this deadlock.
..
..

Has anyone experienced this problem before?
Is it really a Microsoft bug that affects perl?
Can another version of perl solve the problem?
Can another version of OS solve the problem?

If you don't find an answer here, try posting to perlmonks. There's a guy
there (BrowserUk) who is particularly knowledgeable on threads issues with
Win32.

If you could provide some (minimal) code that demonstrates the problem (and
that others can run on their own machines), it would improve your chances of
getting assistance - both here and on perlmonks ... and on any other forum
to which you post.

(I acknowledge that it's not always feasible to provide such code

Cheers,
Rob