Most worthy Monks-

When using Win32::OLE in XP SP2 and ActiveState perl (5.8.8), forking always results in a null pointer exception on the death of the child thread. Example: 
use strict;
use warnings;
use Win32::OLE;
Win32::OLE->Option(Warn => 3);

my $pid = fork;
if($pid == ){
  sleep 5;
  exit;
}
warn "Waiting on $pid";
waitpid($pid, 0);

[download]


This will throw an error of the type:
The instruction at "0xsomeaddr" referenced memory at "0x00000000". The memory could not be "written".

Does anyone know of a workaround for this problem? It's thrown a real wrench in my port of our VB reporting application.

In reply to Win32::OLE and fork causes null pointer exception by jrsimmon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.