On 26.06.2014 12:22, Philip Martin wrote: > Philip Martin <philip.mar...@wandisco.com> writes: > >>> Can you please send the JVM stack trace file, too? Thanks. >> I don't think it is much use as the exact crash varies from run to run. >> It happens after different numbers of dots in the test output and the >> stack trace varies. Some examples: > Here is an Java log file from one crash:
Thanks, this is extremely helpful. Results from valgrind or a debugger are pretty much useless because there appear to be cases where the JVM /expects/ segfaults to happen, and handles them itself ... but valgrind doesn't know enough to ignore them. Since they happen in different threads, the timing is not predictable. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
