I'll add a little to this. One can abuse unpack to cause a core dump, but that is probably not what is happening here.

The easiest way to get a "Dr. Watson" w/ Perl is to use fork (under Win32). So, if you are doing that, you might want to look at (tye)Re: How to multiprocess in Win32?.

The original seeker mentioned using lots of memory. Under Win32, if you run out of swap space, a dialogue pops up telling you that you are running low on memory. Once that happens, somewhere a call to malloc() (etc.) has failed. Many things don't check for failure of malloc() and many things that do check don't deal well with the failure anyway. So once you see that dialogue, just about any program, and indeed the operating system itself, is suspect and may fail in unusual ways.

Even if we assume that Perl is perfect at remaining sane in the face of a failed malloc(), the Win32 libraries that Perl uses certainly aren't perfect in that respect and so Perl could certainly "Dr. Watson" after the "low memory" dialogue appeared.

But if you haven't seen the "low memory" dialogue, then Perl using lots of memory should not be a reason for a "Dr. Watson".

        - tye (but my friends call me "Tye")