On Fri, 11 Apr 2008, Bill Janssen wrote:
On Thu, 10 Apr 2008, Bill Janssen wrote:
Now I can generate the wrappers, and call initVM on GoodStuff, but not
actually run it. This is Python 2.5.1 running both "lucene" and
"goodstuff", both wrapped with --shared, using Java 6 on CentOS Linux.
Can this raise a (Python) exception which can be caught and handled
rather than aborting the process?
You say 'can this raise a (Python) exception....' but what is 'this' ?
In particular, what is happening at build/_goodstuff/__wrap__.cpp:6166 ?
It's calling newObject(), pretty much what the stack trace says.
Yes, that much I saw too. But I need to know what is calling to be able to
answer your question as to why it's crashing and not reporting a python
error.
It turned out to be another missing class issue, referenced by one of
the types implementing GoodStuff, and not on my classpath. If I fire
up Python interactively, and try creating an instance of GoodStuff by
hand, I get the Java exception and stack trace. I'm not sure why it
doesn't work inside a program...
If you tell me what's at that line of code (__wrap__.cpp:6166) I can give
you an answer.
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
