Bug #318

Segfault in uthread_create.c _thread_start() SMP

Added by aphor about 8 years ago. Updated over 5 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Initial:
To recreate this bug (Sorry no C test code yet) install Zope29 from pkgsrc, and
Plone-2.5 into a zope instance Products. Add a "Plone Site" in the ZMI, and then
try to load the Plone site root. Python will immediately segfault attempting to
create a thread to handle the new connection. Corefile available. Backtrace
results attached.

DragonFlyPloneBT.txt Magnifier (12.5 KB) aphor, 09/13/2006 01:44 PM

python2.4.core.bz2 (14 MB) aphor, 09/13/2006 01:50 PM

History

#1 Updated by aphor about 8 years ago

Corefile attached.
DragonFly rabbit 1.6.1-RELEASE DragonFly 1.6.1-RELEASE #6: Sat Aug 19 16:14:40
CDT 2006 :/usr/obj/usr/src/sys/DUALPIII i386
This system was compiled from CVS 1.6.1 RELEASE tag.

#2 Updated by corecode about 8 years ago

We would at least require the python binary itself to investigate.

But actually it looks like the fault happens in the python code
(select_select()) as I can't see thread_start() anywhere in the traces.

#3 Updated by corecode almost 8 years ago

does this still happen?

#4 Updated by alexh over 5 years ago

No answer from original reporter in 2 years since follow-up so I'm closing this
bug report.

Also available in: Atom PDF