Sandor Palfy wrote at 2004-2-24 09:48 -0600:
>I followed Jeremy's instructions to get the trace from python.core.
>Here's the script:
> ...
>$ gdb /zope/python23/bin/python ./python.core GNU gdb 4.16.1

Almost surely, your "gdb" is far too old to analyse the core
of a multi-threaded program (such as Zope).

The indicator for this is that "gdb" reports just the main
thread (which usually does not have any problem).
You need a gdb version 5.x (with "x" as high as possible).

>Copyright 1996 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you

Please do not send a complete script the next time!
Remove unintesting parts. E.g. we are not interested which
shared object were loaded and we are only interested in
the first 20 to 40 stack frames and only of the thread that
got the signal.
>#0  0x6257255 in select_select (self=0x0, args=0x3d641f7c)
>    at /usr/local/src/python_release23-maint/Modules/selectmodule.c:171
>171     }
>(gdb) bt
>#0  0x6257255 in select_select (self=0x0, args=0x3d641f7c)
>    at /usr/local/src/python_release23-maint/Modules/selectmodule.c:171

It is almost surely not this thread that got the SIGSEGV (unless
it is a C runtime stack overflow, quite common on BSD systems).


Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to