Bug#837081: Re%3A Bug#837081%3A netbeans%3A Crashes due to assertion failure in GLib

Tobias Wich tobias.wich at electrologic.org
Thu Mar 23 15:22:26 UTC 2017


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170323/09ff2e97/attachment.html>


More information about the pkg-java-maintainers mailing list