Re: [Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-13 Thread Joseph Wayne Norton
Matt - Ok, I installed everything and the system is running fine (or no worse). However, we still faced one restart so far. I have included the debug information below. This looks similiar to the problem report on sourceforge:

Re: [Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-12 Thread Joseph Wayne Norton
Matt - Well, your patch seems fine in our testing environment. Unfortunately, we do not see any restarts in the testing environment ... always in production. I had to rebuild our entire software base because we are using other products that use extensions class and they are not included under

Re: [Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-12 Thread Matthew T. Kromer
Joseph Wayne Norton wrote: Matt - Well, your patch seems fine in our testing environment. Unfortunately, we do not see any restarts in the testing environment ... always in production. I had to rebuild our entire software base because we are using other products that use extensions class and

Re: [Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-12 Thread Florent Guillaume
(gdb) print *((PyObject *) gc)-ob_type $1 = {ob_refcnt = 18213696, ob_type = 0x2d70b0, ob_size = 0, tp_name = 0x1 T, tp_basicsize = 1328272, tp_itemsize = 4156348, tp_dealloc = 0x125865c, tp_print = 0x3c1b04, tp_getattr = 0, tp_setattr = 0, tp_compare = 0x29, tp_repr = 0x3adeb0,

Re: [Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-12 Thread Matthew T. Kromer
Florent Guillaume wrote: (gdb) print *((PyObject *) gc)-ob_type $1 = {ob_refcnt = 18213696, ob_type = 0x2d70b0, ob_size = 0, tp_name = 0x1 T, tp_basicsize = 1328272, tp_itemsize = 4156348, tp_dealloc = 0x125865c, tp_print = 0x3c1b04, tp_getattr = 0, tp_setattr = 0, tp_compare = 0x29,

Re: [Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-11 Thread Matthew T. Kromer
Hi Joe, The problem you're seeing is that the fault is happening on a different thread than the receiver of the signal; that truss syntax is interesting though (I have an old SPARC around to test on but its painfully slow) so I'm wondering if first you needed to do an 'info thread' in gdb and

Re: [Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-11 Thread Joseph Wayne Norton
At Tue, 11 Dec 2001 10:42:46 -0500, Matthew T. Kromer wrote: #0 0xef5b9810 in _lwp_sema_wait () (gdb) info threads 19 Thread 10 0xef5b9810 in _lwp_sema_wait () 18 Thread 9 0xef5b9810 in _lwp_sema_wait () 17 Thread 8 0xef5b9810 in _lwp_sema_wait () 16

[Zope-dev] recipe for trapping SIGSEGV and SIGILL signals on solaris

2001-12-10 Thread Joseph Wayne Norton
Hello. We are facing zope restarts on the solaris 5.6 platform with zope 2.4.3 and python 2.1.1. I put together a script based some information on an old posting to the apache mailing list. The following shell/perl script allows one to get a core file from a dying zope child process and also