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

Markus Koschany apo at debian.org
Thu Mar 23 17:58:06 UTC 2017


On Thu, 23 Mar 2017 16:22:26 +0100 Tobias Wich <tobias.wich at electrologic.org> wrote:
> 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?
> 

Hi,

you could try setting

(gdb) handle SIGSEGV nostop noprint pass

then "cont" and when it crashes "bt full"

I'm no gdb expert either but if you get something useful from gdb it could be helpful.

Regards,

Markus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170323/b9ebddf1/attachment.sig>


More information about the pkg-java-maintainers mailing list