comment on

Well, very mysterious!

First, what is your Perl version?

If you are usign Perl 5.8.0, disable the signal ALARM:
$SIG{ALARM} = undef ;
to avoid some wrong signal from the OS. I don't know if you need this for 5.6.0+ too! Well, this problem with alarm is very specific.

I saw that you uses sockets. Don't forget to close a socket after use it, or at least lose the $variable with the socket. Because the system, specially on Win32, has a limit for sockets to be opned.

You have to monitore the memory used by the process too! Maybe it wasn't coleting the garbage of unused variables and objects!

If you don't need the prompt window, run your script using the wperl.exe! This way doesn't open a console (pipe) for the process, and was 1 thing less to create problems!

Good luck! ;-P

Graciliano M. P.
"The creativity is the expression of the liberty".

In reply to Re: Mysterious script crash in win2k and ActivePerl by gmpassos
in thread Mysterious script crash in win2k and ActivePerl by jhanna

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks