Re: Bug

I still get this bug even though I am using the cvs version.  With the 
patch below, I don't.

Eric

David Clymer wrote:
> On Thu, 2006-01-05 at 17:08 -0500, Eric Davis wrote:
>> Basically, the thread is trying to communicate with lyntin when you have 
>> no engine object.  I have a fix for this:
>>
>> 420 in net.py to be these 2 lines:
>>
>>       if not self._shutdownflag:
>>         self._config.change("mudecho", "on")
>>
>>         # output message so the user knows what happened.
>>         event.OutputEvent(message.Message("Lost connection to: %s\n" % 
>> self._host)).enqueue()
> 
> I believe there was a discussion of this a while ago, and the theory was
> that a race condition existed such that the engine thread could shutdown
> before the UI thread. It looks like Eugene modified things back in
> November so that the UI is the main thread (rather than the lyntin
> engine), meaning this should no longer happen. I just tried out cursesui
> and I no longer get the error. You may want to try the latest from CVS.
> 
> -davidc



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click