search

Vitalts / golangide

Automatically exported from code.google.com/p/golangide
0 stars 0 forks source link

Segfault in startup #40

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Download latest liteide x86_64 for linux
2. extract the tarball
3. execute liteide/bin/liteide

What is the expected output? What do you see instead?
I expect the program to start but instead i get a segfault with the message:
I/O error : No such file or directory
/usr/share/mime/inode/directory.xml:1: parser error : Extra content at the end 
of the document

^
Segmentation fault

What version of the product are you using? On what operating system?
Latest at submit date

Please provide any additional information below.
The directory.xml exists and is readable by normal users.

Original issue reported on code.google.com by dahankz...@gmail.com on 15 Oct 2011 at 8:11

Attachments:

GoogleCodeExporter commented 8 years ago 
Same problem with my system I am running
fedora 15 uname: 2.6.40.6-0.fc15.i686 #1 SMP Tue Oct 4 00:51:19 UTC 2011 i686 
i686 i386 GNU/Linux

Original comment by dle.ev...@gmail.com on 24 Oct 2011 at 1:37

GoogleCodeExporter commented 8 years ago 
Performed a strace on the program on start up of the liteide command, at the 
tail end of the strace file it looks like liteide tries to read in 8192 bytes 
from the /usr/share/mime/inode/directory.xml file, it then reads in 2174 bytes 
then
tries to read 6018 bytes. the rest of the 8192 bytes? I attached the strace 
file to this comment.

Original comment by dle.ev...@gmail.com on 26 Oct 2011 at 12:07

Attachments:

GoogleCodeExporter commented 8 years ago 
Seem the reason is QT runtime library

Original comment by Visua...@gmail.com on 26 Oct 2011 at 6:37

GoogleCodeExporter commented 8 years ago 
Yeah, I figure it was something within the Qt library, the fix for
this problem at least for the Fedora Core 15 (32-bit) is to simply compile
the source files on the targeted system. After compiling from source code,
the binaries run perfectly. Perhaps its just some slight inconsistencies with
some other distros in the Fedora header files?

Original comment by dle.ev...@gmail.com on 5 Nov 2011 at 11:08

GoogleCodeExporter commented 8 years ago 
After some experimentation, I found that the segmentation fault has something 
to do with the rpath.

Using elfhack, set the rpath to "" and it will magically begin working again.

I suspect this is something you can fix upstream?

Original comment by sunderp...@googlemail.com on 31 Dec 2011 at 6:16

GoogleCodeExporter commented 8 years ago 
Is system have qt libraty, remove liteide/lib qt*.so

Original comment by Visua...@gmail.com on 9 Jan 2012 at 7:04

GoogleCodeExporter commented 8 years ago 
"Is system have qt libraty, remove liteide/lib qt*.so"

well, that does in fact work. Would be nice if it weren't necessary though.

Have you tried statically linking Qt into the main application binary? Other Qt 
apps I've used which offer a Linux binary tarball seemed to have done it that 
way, and they didn't have this problem. 

Only problem with doing it that way is that it looks ugly because it's stuck 
using the default Qt theme instead of the one that's set system-wide. But I 
think that's a fair price to pay for convenience, and for not-crashing by 
default on a system with its own Qt (that is, most of them).

Original comment by nbur...@purdue.edu on 11 Aug 2013 at 7:54