On Tue, 09 Jan 2007 17:26:31 -0500, Malcolm Nooning
<[EMAIL PROTECTED]> wrote:
>It seems that the mere presence of a "use Win32::Process::Info"
>statement, along with even an empty fork(), causes a perl interpreter
>crash. As it turns out, there are a number of "use xxxx" things that
>will result in a perl interpreter crash, if there is a Windows fork
>involved.
I don't know about Win32::Process::Info, but you definitely cannot use
Win32::OLE in a program that uses (pseudo-)fork. It is a long
outstanding issue, and not trivial to implement. Maybe I'll get around
to it sometime this year, but I've been saying this for a while now...
Cheers,
-Jan
>If you have a windows 2K or XP machine, please run the code snippet
>below, after uncommenting each "use" statement, one at a time, in turn,
>to see if your machine, too, exhibits the perl interpreter crash. On my
>machine, any of the last four will cause it. I find it hard to believe
>that such an important problem would never have been reported before. I
>need to know if it is particular to my machine.
>
>Thanks
>
>----------------------paste
>#!/usr/bin/perl -w
>
>#use Win32::API;
>#use Win32API::Registry;
>#use Win32::OLE;
>#use Win32::OLE::Const;
>#use Win32::OLE::Variant;
>#use Win32::Process::Info;
>
>if (my $pid = fork()) {
> print "Parent\n";
>}
>elsif(defined $pid) {
> print "Child\n";
> exit;
>} else {
> print "Failed to fork:$!:\n";
>}
>--------------------------end paste
