>>>>> "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>> #5 0x5b328 in Perl_sighandler ()
>> #6 <signal handler called> **** Yikes! ****
JNP> Hm, an event handler died and the recovery was interrupted by a signal.
i canceled the write event but i never made any signal handler. maybe a
sigpipe or something got triggered? any way of determining what signal
happened? maybe just make all signals call an event.pm handler?
JNP> Sure. I've never seen the code for an async connect.
i will send it to you next letter.
JNP> You are aware that signal handlers are not safe?
as i said, i am not doing any signal stuff in this code. and i will use
event.pm signal events when i do.
JNP> Correct, the default behavior is to trap the error and try to continue
JNP> looping. If you want to exit, just set up your own handler:
JNP> $Event::DIED = \&my_exception_handler;
JNP> You can adapt the code from default_exception_handler in Event.pm if you
JNP> like.
sounds good.
expect a 3 file email to you next. i will preface it with how to use it.
thanx,
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
