[Zope] zope_msg.log Message

[Peter Sabaini]

On Sat, 25 Mar 2000, Michel Pelletier wrote:

:Pavlos Christoforou wrote:
:> 
:> On Fri, 24 Mar 2000, Michel Pelletier wrote:
:> 
:> >
:> > > As soon as I'm able to collect more info I'll forward it to you.  Is
:> > > there anywhere else I should be posting this information?
:> >
:> > The list.  just keep ccing me.
:> >
:> 
:> Some good news at last ...
:> 
:> When I set DEBUG in asyncore.py to 1 so I could view the lists going into
:> select, ZServer stabilised and hasn't crashed since. Smells like a race
:> condition and somehow the extra time it takes to print the list contents
:> stabilises things.
:
:This might be a seperate problem than The Mysterious Segment Violation. 
:Can race conditions cause SEG faults? , I guess they can like any other
:piece of code.  but I would expect a race condition to just spin the
:process.  Can someone who I've spoken with about their SIGSEV problem
:reproduce Pavlos' cure?

i set DEBUG=1 in 
$ZOPEHOME/ZServer/medusa/asyncore.py

deleted asyncore.pyc and restartet my zope but had SIGSEV
nevertheless. can i somehow verify that that DEBUG did anything at
all?

peter.
 
-- 

_________________________________________________
peter sabaini, mailto: sabaini@niil.at
-------------------------------------------------