Hello, Yura.

its pretty weird. I still has this bug with Debian Linux kernel 2.6.11, but code
work fine with RedHat Linux 2.4.

Any ideas?

YS> Hello, Andi.

YS> I use gcc of 4.0.1 version for PyLucene. Should I build Python with
YS> CVS version of GCC?

AV>> It could be that you're using the wrong version of the compiler. It needs 
to
be version >>> 3.4.1 ?

AV>> Andi..

>>> Hello, Andi.
>>>
>>> Yeah, I know that code is not OS specific... But I have checked again
>>> this bug. It appears on Debian linux and on Red Hat it works likes a
>>> charm.
>>> I have tested code on 2 Debian boxes and 3 RedHat ones.
>>>
>>> I am wondering, maybe I miss something?.. Or could differences exist
>>> in any behavior of operation systems?
>>>
>>> I know, that my question is very weird and maybe.. a little stupid :)
>>> I am confused about this bug.
>>>
>>> AV> The reason this bug was happening was because of a deadlock situation 
>>> between
>>> AV> python threads who call into java and back into python and threads 
>>> created
>>> AV> from java (ParallelMultiSearcher does that) that call into python.
>>> AV> This was fixed in 0.9.8 where all calls from python to java release the 
>>> python
>>> AV> GIL (global interpreter lock) and reacquire it when calling back from 
>>> java
>>> AV> into python. This is not OS specific.
>>>
>>> AV> Andi..
>>>
>>> AV> On Wed, 20 Apr 2005, Yura Smolsky wrote:
>>>
>>>>> Hello, Andi Vajda.
>>>>>
>>>>> AV> Great, this would get us one step closer to a 1.0 release !
>>>>>
>>>>> Andi, I have that problem appeared again. It works great on Windows
>>>>> platform, and it worked good on RedHat Linux.
>>>>> But when we migrated to Debian with kernel 2.6.11 the problem has 
>>>>> appeared again.
>>>>>
>>>>> Can you suggest us how to detect the real reason of this bug with hits
>>>>> on Debian Linux?
>>>>>
>>>>> ---------- Forward Message ----------
>>>>> From:   Yura Smolsky <[EMAIL PROTECTED]>
>>>>> To:     [email protected]
>>>>> CC:
>>>>> Time:   Mon, 28 Feb 2005 09:28:04 -0600
>>>>> Subj:   [pylucene-dev] ParallelMultiSearcher and Hits.doc(i)
>>>>> Attach: RemoteSearcherBad.py, ?????.txt
>>>>>
>>>>> Hello.
>>>>>
>>>>> I have noticed that ParallelMultiSearcher does not return correct Hits
>>>>> object when we use custom implemented Searchable, but
>>>>> MultiSearcher return correct one.
>>>>> "Correct" object Hits object means that it can return documents more
>>>>> than 100th.
>>>>>
>>>>> So, I cannot get documents more than 100th from Hits object returned
>>>>> by ParallelMultiSearcher (with custom implemented Searchable object).
>>>>> When It cannot return needed object it loops forever, it does not
>>>>> return control outside Hits.doc(i) method.
>>>>>
>>>>> I provide attach file which can easily reproduce the situation.
>>>>>
>>>>> Yura Smolsky.
>>>>>
>>>>>
>>>>> ---------- End of Forward ----------
>>>>>
>>>>> Yura Smolsky,
>>>>>
>>>
>>>
>>>
>>>
>>> Yura Smolsky.
>>>
>>>
>>>




YS> Yura Smolsky.


YS> _______________________________________________
YS> pylucene-dev mailing list
YS> [email protected]
YS> http://lists.osafoundation.org/mailman/listinfo/pylucene-dev




Yura Smolsky.


_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev

Reply via email to