Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » "Program received signal SIGSEGV, Segmentation fault" all over in Luna under Ubuntu 13.10
icon5.gif  "Program received signal SIGSEGV, Segmentation fault" all over in Luna under Ubuntu 13.10 [message #1231979] Wed, 15 January 2014 23:23 Go to next message
Denis Golovin is currently offline Denis GolovinFriend
Messages: 18
Registered: July 2009
Junior Member
I was trying to figure out what is wrong with my local environment, which is Ubuntu 13.10, x86_64, Xfce4, Oracle Java 1.7.0_45 x86_64 in relation with Eclipse crashes in Import Maven Projects after Browse button is pressed and noticed I am getting many "Program received signal SIGSEGV, Segmentation fault." messages in gdb.

More segmentation fault errors I see the slower eclipse starts. It explains why Luna M4 is so unstable under Linux.

Kepler SR1 seems to be fine and it doesn't have problems like this.

Is it in some way related to SWT using GTK3 in latest Luna?

Update 1:

Tested with SWT_GTK3=0 and it doesn't help.

Update 2:

Luna M6 released and nothing changed, I am still getting the same problems.

Thanks

[Updated on: Wed, 26 March 2014 18:30]

Report message to a moderator

Re: "Program received signal SIGSEGV, Segmentation fault" all over in Luna under Ubuntu 13 [message #1239353 is a reply to message #1231979] Tue, 04 February 2014 02:02 Go to previous messageGo to next message
Denis Golovin is currently offline Denis GolovinFriend
Messages: 18
Registered: July 2009
Junior Member
Luna M5 is out and it has the same problem. Many segmentation faults in native GTK related code is still there, so eclipse crashes and UI tests hangs randomly.

gdb output shows:

[Thread 0x7f4a284e0700 (LWP 30386) exited]
[New Thread 0x7f4a284e0700 (LWP 30387)]
[Thread 0x7f4a284e0700 (LWP 30387) exited]
[New Thread 0x7f4a284e0700 (LWP 30388)]
[Thread 0x7f4a284e0700 (LWP 30388) exited]
[New Thread 0x7f4a284e0700 (LWP 30389)]

Program received signal SIGSEGV, Segmentation fault.
0x00007f4a5043bcbf in ?? ()
(gdb) continue
Continuing.
[Thread 0x7f4a284e0700 (LWP 30389) exited]
[New Thread 0x7f4a284e0700 (LWP 30392)]
[New Thread 0x7f4a44ba6700 (LWP 30393)]
[New Thread 0x7f4a285e1700 (LWP 30394)]
[Thread 0x7f4a285e1700 (LWP 30394) exited]
[New Thread 0x7f4a285e1700 (LWP 30395)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f4a206b9700 (LWP 27183)]
0x00007f4a502d54f8 in ?? ()
(gdb) continue
Continuing.
[Thread 0x7f4a285e1700 (LWP 30395) exited]
[Thread 0x7f4a44ba6700 (LWP 30393) exited]
[New Thread 0x7f4a44ba6700 (LWP 30398)]
[Thread 0x7f4a44ba6700 (LWP 30398) exited]
[New Thread 0x7f4a44ba6700 (LWP 30399)]
[Thread 0x7f4a44ba6700 (LWP 30399) exited]
[New Thread 0x7f4a44ba6700 (LWP 30400)]
[Thread 0x7f4a44ba6700 (LWP 30400) exited]
[New Thread 0x7f4a44ba6700 (LWP 30401)]
[Thread 0x7f4a44ba6700 (LWP 30401) exited]




icon5.gif  Re: "Program received signal SIGSEGV, Segmentation fault" all over in Luna under Ubuntu 13 [message #1277973 is a reply to message #1239353] Wed, 26 March 2014 18:32 Go to previous messageGo to next message
Denis Golovin is currently offline Denis GolovinFriend
Messages: 18
Registered: July 2009
Junior Member
I am stuck with this problem and have to restart eclipse every hour.
Does anyone else experience something similar?
Re: "Program received signal SIGSEGV, Segmentation fault" all over in Luna [message #1278325 is a reply to message #1231979] Thu, 27 March 2014 07:11 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1397
Registered: July 2009
Senior Member
On 16/01/2014 00:23, Denis Golovin wrote:
> I was trying to figure out what is wrong with my local environment,
> which is Ubuntu 13.10, x86_64, Xfce4, Oracle Java 1.7.0_45 x86_64 in
> relation with https://bugs.eclipse.org/bugs/show_bug.cgi?id=425692 and
> noticed I am getting many "Program received signal SIGSEGV, Segmentation
> fault." messages in gdb.
> More segmentation fault errors I see the slower eclipse starts. It
> explains why Luna M4 is so unstable under Linux.
>
> Kepler SR1 seems to be fine and it doesn't have problems like this.
>
> Is it in some way related to SWT using GTK3 in latest Luna?
>

If I remember correctly, currently, if you run luna in Linux you must
make sure to disable GTK3... the latest M6 should do that automatically
when run in Linux.

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: "Program received signal SIGSEGV, Segmentation fault" all over in Luna [message #1291066 is a reply to message #1278325] Thu, 10 April 2014 17:33 Go to previous message
Denis Golovin is currently offline Denis GolovinFriend
Messages: 18
Registered: July 2009
Junior Member
Probably M6 does, but it doesn't help. Mo matter how eclipse Luna M6 started w/ or w/o GTK3 it crashes every half an hour.
Previous Topic:Restoring Default Preferences for all preferences
Next Topic:Modernising actionSetPartAssociation
Goto Forum:
  


Current Time: Thu Nov 27 22:30:38 GMT 2014

Powered by FUDForum. Page generated in 0.05225 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software