Alexander Staubo <alex@mop.no> writes:

I really, really hate to be a pest, but could somebody at DC please look this way and at least make a small attempt at helping me out?

Python 1.5.2 and Zope both compiled with gcc 2.8.1; relevant?

Were there any errors during the compile? A core dump usualy means that something went wrong in one of the C Extensions that caused a low level exception, like accessing a NULL pointer. It would be nice to find out exactly where in the code this is happening. First, I'd like to eliminate ZServer from the equation, could you go to the lib/python directory and run python1.5.2, then:

...

...

import Zope, ZPublisher ZPublisher.Main('/')

This will simulate a request for '/' (the root folder's index_html method). If this doesn't fail, then the problem is in ZServer (which I find unlikely, there being no C in ZServer). In the case of failure, it will either happen after the import or after the call to Main(). If the former, let us know that, if the latter, load python and do the import and then try:

...

...

ZPublisher.Main('/', d=1)

This will put you in the debugger (which you might want to read about a bit on python.org if you don't know how to use it) using combinations of (s)tep and (n)ext, try and narrow down right to the line of code where the core dump is happening. -Michel

-- Alexander Staubo http://www.mop.no/~alex/ "`This must be Thursday,' said Arthur to himself, sinking low over his beer, `I never could get the hang of Thursdays.'" --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_

...

-----Original Message----- From: Alexander Staubo [mailto:alex@mop.no] Sent: 25. juni 1999 16:07 To: Zope Mailing List (E-mail) Subject: RE: [Zope] Startup error Zope 2.0.0a3: Error 139

I hear rumours that error code 139 indicates memory corruption. Also I just noticed the crash below has Python producing a core dump, anybody want to look at it?

-- Alexander Staubo http://www.mop.no/~alex/ "What the hell, he thought, you're only young once, and threw himself out of the window. That would at least keep the element of surprise on his side." --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_

...

-----Original Message----- From: Alexander Staubo [mailto:alex@mop.no] Sent: 25. juni 1999 15:43 To: Zope Mailing List (E-mail) Subject: [Zope] Startup error Zope 2.0.0a3: Error 139

I just installed Zope 2.0.0a3 (no CVS patches) on a Slackware Linux 2.2 (libc6, Python 1.5.2) box. Of course, it refuses to start:

firewall:/usr/local/zope-2.0.0a3# python z2.py -d 192.168.1.1 -w 8080 -f 2121 zdeamon: Fri Jun 25 15:32:33 1999: Houston, we have forked zdeamon: Fri Jun 25 15:32:33 1999: Houston, we have forked zdeamon: Fri Jun 25 15:32:33 1999: Hi, I just forked off a kid: 24905 zdeamon: Fri Jun 25 15:32:35 1999: Aiieee! 24905 exited with error code: 139

Curiously, no tracebacks?

-- Alexander Staubo http://www.mop.no/~alex/ "What the hell, he thought, you're only young once, and threw himself out of the window. That would at least keep the element of surprise on his side." --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )