On Tue, 31 Jan 2006, tsuraan wrote:
And, of course, the system details:
gcc 4.1-20051029
FreeBSD 5.4
512MB RAM, 3.2 GHz processor
On 31/01/06, tsuraan <[EMAIL PROTECTED]> wrote:
It looks like one of the indices (the first one opened, actually) is
missing its segments file. Why this causes the abort several indices
later is a bit of a mystery, but I can at least work around this.
A bug posted to the gcj bug tracker in 2000 indicated that sometimes
null exceptions weren't being propogated correctly and were just
causing aborts, but I assume this is fixed by now. Maybe the PyLucene
wrappers could have a catch-all for null pointer exceptions though, so
that aborts are prevented? I don't know how ugly that would get, but
aborts aren't good either.
In PyLucene.i there is a catch all for all java exceptions, line 2039 in
PyLucene.i, that propagates the error to python as a JavaError python
exception. If there is an abort, it probably doesn't go through that code.
How about using gcc 3.4.4 or gcc 3.4.5 ?
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
