https://bugs.kde.org/show_bug.cgi?id=496552
--- Comment #7 from Bill Torpey <wallstp...@gmail.com> --- Thanks again Paul -- comments follow. > I'll start with invalid reads and writes. In order for memcheck to get this > wrong it must fail to correctly redirect allocation and deallocation > functions or it must fail to have the right information on stack limits. In > this case it looks like the stack. At this point I think we're going to have to write this off as a false positive caused by the JVM doing something that confused valgrind. As mentioned earlier, we don't much care about what the JVM itself is doing, simply because there's nothing we can do about it -- not to mention that we simply don't have the time or resources to go down that particular rabbit-hole. > If you can reproduce the issues outside of your test framework I would ... We can't even reproduce the issue *with* our test framework -- it was a one-time event, out of literally thousands of test runs that were totally fine. Which, of course, is why we're even asking this question in the first place. Thanks again for all your help -- I think we're at a dead-end here. The main thing is it sounds like it *is* possible for valgrind to lose track of the stack, and that is the only explanation that I can come up with for the results we're seeing. We'll keep on eye on subsequent tests, but frankly I would be surprised if this happens again. -- You are receiving this mail because: You are watching all bug changes.
