>> #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 

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

I've got serious wonders about that:

1. The full stack trace had more than 350 frames, which is excessive
   even for Zope <0.9 wink>.

2. Line 171 of selectmodule.c in Python branch release23-maint is the
   closing curly brace of internal function set2list().  When a
   debugger dies pointing to a function's closing curly, it can mean
   that the generated return-from-function C code is blowing up
   due to stack corruption.

But not enough info to say for sure ...

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to