[Zope] Another Aiieee.....

[Jon Prettyman]

I am once again encountering the mysterious Aiieee error with core
dumps from Zope/Python on a Solaris boxen.

SunOS sparky 5.7 Generic_106541-08 sun4m sparc SUNW,SPARCstation-20
Python 1.5.2 (#1, Oct 24 2000, 11:56:43)  [GCC 2.8.1] on sunos5
Zope-2.2.2
DCOracle 1.3.2
448M ram

I get the following in my STUPID_LOG
2000-11-03T20:42:10 ERROR(200) zdaemon zdaemon: Fri Nov  3 14:42:10 2000: Aiieee! 17537 exited with error code: 139

/usr/include/sys/errno.h looks like this:
#define ECONNABORTED    130     /* Software caused connection abort */
#define ECONNRESET      131     /* Connection reset by peer */
#define ENOBUFS         132     /* No buffer space available */
#define EISCONN         133     /* Socket is already connected */
#define ENOTCONN        134     /* Socket is not connected */
/* XENIX has 135 - 142 */
#define ESHUTDOWN       143     /* Can't send after socket shutdown */
#define ETOOMANYREFS    144     /* Too many references: can't splice */
#define ETIMEDOUT       145     /* Connection timed out */
#define ECONNREFUSED    146     /* Connection refused */
#define EHOSTDOWN       147     /* Host is down */
#define EHOSTUNREACH    148     /* No route to host */

What is a 139 error code?  Is it an errno?  I do get core dumps but
for some reason I can't get gdb to read it.  Arghhh.

Crashes appear random.  The box has at most two people accessing
Zope.  It appears ``manage'' related, but I can't be sure.

There is an identical instance of this Zope application running on a
Linux box that does not have this problem.  It is very stable.  We'd
like to use this Solaris boxen for our development work.
-jon