On Wed, 19 Jan 2000, Joshua N Pritikin wrote:
> On Wed, Jan 19, 2000 at 10:33:03PM -0500, [EMAIL PROTECTED] wrote:
> > > "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
> >
> > >> #5 0x5b328 in Perl_sighandler ()
> > >> #6 Yikes!
> >
> > JNP> Hm, an ev
On Wed, Jan 19, 2000 at 10:33:03PM -0500, [EMAIL PROTECTED] wrote:
> > "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>
> >> #5 0x5b328 in Perl_sighandler ()
> >> #6 Yikes!
>
> JNP> Hm, an event handler died and the recovery was interrupted by a signal.
> "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>> #5 0x5b328 in Perl_sighandler ()
>> #6 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
sigpip
On Wed, Jan 19, 2000 at 06:30:04PM +, [EMAIL PROTECTED] wrote:
> Joshua N Pritikin <[EMAIL PROTECTED]> wrote
> > On Wed, Jan 19, 2000 at 12:19:34AM -0500, [EMAIL PROTECTED] wrote:
> > > i am wondering what signal is being handled there as well. sigpipe?
> >
> > You are aware that signal handl
Joshua N Pritikin <[EMAIL PROTECTED]> wrote
> On Wed, Jan 19, 2000 at 12:19:34AM -0500, [EMAIL PROTECTED] wrote:
> > i am wondering what signal is being handled there as well. sigpipe?
>
> You are aware that signal handlers are not safe?
I assume you mean Perl signal handlers. I'd always assum
On Wed, Jan 19, 2000 at 12:19:34AM -0500, [EMAIL PROTECTED] wrote:
> well, i said i would hammer event.pm and i just got a core dump. here is
> the stack trace from gdb:
>
> (gdb) bt
> #0 0xff216870 in _kill ()
> #1 0x99ac4 in Perl_apply ()
> #2 0x92e20 in Perl_pp_kill ()
> #3 0x9ef6c in Perl
well, i said i would hammer event.pm and i just got a core dump. here is
the stack trace from gdb:
(gdb) bt
#0 0xff216870 in _kill ()
#1 0x99ac4 in Perl_apply ()
#2 0x92e20 in Perl_pp_kill ()
#3 0x9ef6c in Perl_runops_standard ()
#4 0x27000 in perl_call_sv ()
#5 0x5b328 in Perl_sighandler
