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

[Tobias Wich]

Hi,

that worked well ;-)

The log is attached. I hope it helps track down the bug.
The Glib lines at the beginning of the log repeat themselves very often. My 
10000 lines terminal did not suffice to keep it all. As it's always the same, I 
omitted this crap.

Best Regards
Tobias


On Donnerstag, 23. März 2017 18:58:06 CET Markus Koschany wrote:
> 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: netbeans_bt.log
Type: text/x-log
Size: 5971 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170325/a6383f21/attachment.bin>