Re: [bdbxml] Crash in dbxml_javaJNI.XmlResults_next__SWIG_0

> Hi, thanks for your help, I do understand this now.
> I rewrote the testcase so that all threads are
> sharing the same XmlManager and XmlContainer and
> these don't get closed before all Threads are finished.
> But even with the latest testcase (ftp://ftp.suse.com/pub/people/ 
> freitag/dbxml/MultithreadingTestCase.java)
> dbxml crashes here in native code either in  
> XmlContainer.getAllDocuments() or
> XmlResults.next().
> So my question is: can you reproduce this crash, or may it be caused
> by a local (compile-)fault at our machines here?
> I compiled dbxml with standard options: "buildall.sh --enable-java"
>
> Greetings, Thomas

Thoma,

I cannot, in fact reproduce the error with the rewritten code.
The behavior you are seeing is what I was able to reproduce
with the old code.  I don't think it's a build issue.

Because the crash occurs when deleted memory is referenced,
a memory-checking tool, such as valgrind can help debug
the problem.  Can you try running under valgrind to see
if it can be further isolated?

Regards,

George



------------------------------------------
To remove yourself from this list, send an
email to [email protected]