lock problem

Ritesh Raj Sarraf rrs at researchut.com
Fri Mar 16 03:42:09 EDT 2007


Gabriel Genellina wrote:

> En Thu, 15 Mar 2007 18:31:29 -0300, Ritesh Raj Sarraf <rrs at researchut.com>
> escribió:
> 
>> I'm not sure if there's something wrong in the code mentioned above or
>> is it
>> really a lock problem.
> 
> Try to break the code into smaller pieces to see what is wrong. It's too
> long for somebody to try to understand it.
> 

The only break I can do is to remove threading, and the it works fine.
I also noticed that when debugging the threads (when the program stops at a
breakpoint in the thread), data is written properly.

This is what made me think if this really is a locking problem.

Ritesh
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
"Stealing logic from one person is plagiarism, stealing from many is research."
"The great are those who achieve the impossible, the petty are those who
cannot - rrs"




More information about the Python-list mailing list