Hello, I can reproduce the problem in between a few seconds and a few minutes, so it shouldn't be a problem getting the stacktraces. However it's been ages that I used gdb and I'm far from an expert in that field.
First I tried adding -XX:OnError="gdb - %p", so gdb is started when the process crashes. But I guess the assert error performs the usual exit on the process and nothing happens. I tried attaching the process with gdb --pid=..., but the java process constantly raises SIGSEGV at least once every second. Can someone tell me how these breaks can be ignored? And how I get all the necessary stack traces? Best regards Tobias
__ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
