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 ?
Ok, gcc 3.4.5 doesn't get the abort, so I guess there's a regression in
the 4.1 tree. Thanks for the idea; I don't really have a reasonable
test case for demonstrating this bug yet, but I'll work on it. Thanks!
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
