On Tue, May 09, 2000 at 08:49:15PM -0400, [EMAIL PROTECTED] wrote:
> #0 0xef546b6c in _watcher_priority ()
> (gdb) bt
> #0 0xef546b6c in _watcher_priority ()
> #1 0xef54eda8 in XS_Event__idle_min ()
> #2 0x73fa8 in Perl_pp_entersub ()
> #3 0x6cfb8 in Perl_runops_standard ()
> #4 0x240c4 in S
> "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
JNP> On Tue, May 09, 2000 at 05:51:21PM -0400, [EMAIL PROTECTED] wrote:
>>
>> this is the current event.pm .76 on solaris 2.6 perl 5.6 and gcc.
JNP> That's strange. I'm using exactly the same combo. Can you post
JNP> perl
On Tue, May 09, 2000 at 05:51:21PM -0400, [EMAIL PROTECTED] wrote:
> i am having a bitch of a time getting 5.6 working with event on my old
> solaris 2.6 box. first 5.6 and cpan don't like each other which is well
> known but this is my first experience with that combo. second, i just got
> event
i am having a bitch of a time getting 5.6 working with event on my old
solaris 2.6 box. first 5.6 and cpan don't like each other which is well
known but this is my first experience with that combo. second, i just got
event installed and it core dumps on my first use of it in stem.
this is the cu
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
> > You are aware that signal handlers are not safe?
>
> I assume you mean Perl signal handlers. I'd always assumed that the
> Event signal handling was all in C and therefore safe.
Yes and yes. I was asking because the core dump (see the mailing list
archives) was happenin
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_kil
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
11 matches
Mail list logo
