Re: Eclipse crashes on Debian Jessie amd64

[Reco <recoverym4n@gmail.com>]

 Hi.

On Fri, Mar 20, 2015 at 12:58:20AM -0700, Serkan KURT wrote:
> Thanks for your response. Log file is attached.
> 
> ~$ ulimit -v
> unlimited


So it boils down to this:

> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j  org.eclipse.swt.internal.gtk.OS._g_object_get_qdata(JI)J+0
> j  org.eclipse.swt.internal.gtk.OS.g_object_get_qdata(JI)J+9
> j  org.eclipse.swt.widgets.Display.removeWidget(J)Lorg/eclipse/swt/widgets/Widget;+19
> j  org.eclipse.swt.widgets.Combo.deregister()V+21
> j  org.eclipse.swt.widgets.Widget.releaseWidget()V+1

While I'm no Java expert by any means, this seems to be the (in)famous
Eclipse bug 419729:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=419729


In particular, the workaround from the comment 34 seems to be the way to
avoid it - using SWT_GTK3 environment variable to forbid Java to use
GTK3.

Reco



> --------------------------------------------
> On Thu, 3/19/15, Reco <recoverym4n@gmail.com> wrote:
> 
>  Subject: Re: Eclipse crashes on Debian Jessie amd64
>  To: debian-user@lists.debian.org
>  Date: Thursday, March 19, 2015, 12:16 PM
>  
>   Hi.
>  
>  On
>  Thu, 19 Mar 2015 01:09:35 -0700
>  Serkan KURT
>  <ssserkkk@yahoo.com>
>  wrote:
>  
>  > # Failed to
>  write core dump. Core dumps have been disabled. To enable
>  core dumping, try "ulimit -c unlimited" before
>  starting Java again
>  
>  Start with doing what you're told to do.
>  I.e. enable core dumps in the
>  shell, and
>  post java backtrace.