in reply to Re^2: Why would a Perl script stop with no informatives?
in thread Why would a Perl script stop with no informatives?

Oh, I got fooled by your mention of signals. Windows doesn't have signals*. Seeing as I was trying to figure out which signal killed your app, ignore my request.

It also preempts the other ideas I had, sorry.

* — Well, you could consider Ctrl-C and Ctrl-Break signals, but that's it. Windows apps use messages instead, and they aren't deadly. You can't even send one to a console app unless it creates a Window.

  • Comment on Re^3: Why would a Perl script stop with no informatives?

Replies are listed 'Best First'.
Re^4: Why would a Perl script stop with no informatives?
by Anonymous Monk on Dec 22, 2009 at 01:17 UTC

    yup - but thanks for looking, anyhow....

    I just set the sig handlers just in case there was something to discover with them... didn't work on the minimalist sig support that Active could get into the interp... and I of course was not making a message loop...

    guess I'll have to get familiar with the debugger, and hope that something shows there. Hate to have to write off such a neat language as unusable - especially if the fault is mine. Unless I can develop a (or leverage someone else's) feel for the quirks and fixes, this kind of impenetrability is a deal breaker for someone who gets paid by the hour, like me...

    Thanks for your time, everyone!

    Dick