Author Topic: Dump starting PI  (Read 4643 times)

Offline darthmagna

  • Newcomer
  • Posts: 2
Dump starting PI
« on: 2015 October 12 00:57:31 »
Hello,
this is my first msg on forum, so first of all I havo to thank you all, mostly Juan for this great piece of software.
I've just downloaded last version of PI, and installed on Slackware64-current, with GLIBC 2.22.
I get this dump message:

PixInsight 01.08.04.1185 - Critical Signal Backtrace
Signal : 11
Module : /opt/PixInsight/bin/PixInsight() [0x13c6e2d]
========================================================================================================================
8: /lib64/libpthread.so.0(+0x11340) [0x7f0ad3a30340]
7: /lib64/libc.so.6(strlen+0x2a) [0x7f0acd0e4f5a](+0x2a [0x7f0acd0e4f5a])
6: /lib64/libc.so.6(+0x39679) [0x7f0acd092679]
5: /opt/PixInsight/bin/PixInsight() [0x5bd2f7]
4: /opt/PixInsight/bin/PixInsight() [0x5ca0a0]
3: /opt/PixInsight/bin/PixInsight() [0x45cff9]
2: /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f0acd079870](+0xf0 [0x7f0acd079870])
1: /opt/PixInsight/bin/PixInsight() [0x4852e9]
========================================================================================================================
terminate called after throwing an instance of 'pcl::EUnixSegmentationViolation'
/opt/PixInsight/bin/PixInsight.sh: riga 13:  4681 Annullato               $dirname/$appname $*

Hope someone can help me :-)

Thank you

Alberto

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Dump starting PI
« Reply #1 on: 2015 October 13 12:15:45 »
Hi Alberto,

Thank you for your compliments.

We can't reproduce this problem. Does it happen each time you run the application, or has it been a sporadic problem?

The segmentation fault happens in strlen(), which is very strange to say the least...
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline darthmagna

  • Newcomer
  • Posts: 2
Re: Dump starting PI
« Reply #2 on: 2015 October 13 12:51:21 »
Hi Juan,
yes, it happen each time I start the program. Indeed very strange the seg fault in strlen...
I copied the content of the glibc 2.17 package in /opt/PixInsight/bin/lib/ folder, just to see what happens... PI starts without problems, but cannot install any upgrade. I attached some printscreen.
Maybe I've a faulty glibc package installed, I'll check.

Moreover, when I close the application, I've this message on the console:

PixInsight 01.08.04.1185 - Critical Signal Backtrace
Signal : 11
Module : /opt/PixInsight/bin/PixInsight() [0x13c6e2d]
========================================================================================================================
1: /opt/PixInsight/bin/lib/libpthread.so.0(+0xf670) [0x7f1414b38670]
========================================================================================================================
terminate called after throwing an instance of 'pcl::EUnixSegmentationViolation'
/opt/PixInsight/bin/PixInsight.sh: riga 13:  2043 Annullato               $dirname/$appname $*

Hope this can help you. If I can do some more tests, I'm ready :-)

Thank you
Alberto

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Dump starting PI
« Reply #3 on: 2015 October 13 14:42:58 »
Really strange. Glibc 2.22 should be compatible with previous versions and of course with 2.17. Those package extraction errors say that the tar/gzip and unzip utilities are not working when invoked from the PI core application. This is probably caused by mixing 2.17 and 2.22 glibc packages, and the same probably happens with libpthread. Looks like a good mess that should not happen.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline NGC7789

  • PixInsight Old Hand
  • ****
  • Posts: 391
Re: Dump starting PI
« Reply #4 on: 2015 November 05 18:41:45 »
I am getting this exact problem after updating to Fedora 23 (clean install). I am using PI .1187 which worked fine under Fedora 22.

Was any resolution found?

-Josh
« Last Edit: 2015 November 05 18:55:33 by NGC7789 »

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Dump starting PI
« Reply #5 on: 2015 November 06 01:47:25 »
Hi Josh,

This could be an incompatibility with some system libraries included in the Linux PixInsight distribution. Try removing these files on the bin/lib distribution directory:

libbz2.so.1
libbz2.so.1.0.6
libcrypto.so
libcrypto.so.10
libcrypto.so.1.0.1e
libexpat.so
libexpat.so.1
libexpat.so.1.6.0
libffi.so.6
libffi.so.6.0.1
libicudata.so
libicudata.so.50
libicudata.so.50.1.2
libicui18n.so
libicui18n.so.50
libicui18n.so.50.1.2
libicuuc.so
libicuuc.so.50
libicuuc.so.50.1.2
libidn.so
libidn.so.11
libidn.so.11.6.11
libpcre.so
libpcre.so.1
libpcre.so.1.2.0
libpng15.so
libpng15.so.15
libpng15.so.15.13.0
libpng.so
libssh2.so
libssh2.so.1
libssh2.so.1.0.1
libssl.so
libssl.so.10
libssl.so.1.0.1e
libuuid.so.1
libuuid.so.1.3.0
libwebp.so
libwebp.so.4
libwebp.so.4.0.2
libz.so
libz.so.1
libz.so.1.2.7


Some of these files are symbolic links - better use your graphical file manager (Nautilus, Dolphin, etc) for simplicity. DO NOT REMOVE the following files:

libmozjs-24.so
libQt*
qt-plugins

Another possibility is a conflict with the Qt5 implementation included with Fedora 23, although this should not happen normally.

Keep in mind that when using Fedora you are risking software and hardware incompatibilities, as well as support problems with existing software, especially proprietary multiplatform applications like PixInsight, VMware, etc. For this reason we have erased any trace of Fedora from our development machines. We now use Red Hat Enterprise Linux 7.1 exclusively. Fedora is very cool to keep oneself in touch with the bleeding edge of software development, but definitely a poor choice when one depends professionally on a working machine.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline NGC7789

  • PixInsight Old Hand
  • ****
  • Posts: 391
Re: Dump starting PI
« Reply #6 on: 2015 November 06 04:37:53 »
Thanks for the info Juan. Perhaps Fedora should not be on the recommended platform list. Red Hat enterprise is not for me due to cost ($50 per year).

I prefer to solve this without hacking PI. Would you recommend downgrading to Fedora 22 or going to Mint.

All of this is being triggered by abandoning Ubuntu. While Ubuntu was completely functional, I didn't like it's long term plan for desktop/phone integration.

EDIT: I think I've answered my own question: downloading Mint 17.2 KDE edition now.

-Josh

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4729
Re: Dump starting PI
« Reply #7 on: 2015 November 06 09:08:10 »
i think CentOS is a free RHE clone though - we used to use that at work...

rob

Offline NGC7789

  • PixInsight Old Hand
  • ****
  • Posts: 391
Re: Dump starting PI
« Reply #8 on: 2015 November 06 09:41:08 »
Thanks for the tip. I've got Mint-KDE 17.2 up and running. I don't think I can bear another install.


Offline eneilson

  • Newcomer
  • Posts: 6
Re: Dump starting PI
« Reply #9 on: 2015 December 22 16:57:17 »
I just upgraded to Fedora 23 here and have the same problem (No issues with F21).  I removed the libraries listed above but the problem persists.  Here is PixInsight's crash info:

PixInsight 01.08.04.1195 - Critical Signal Backtrace
Signal : 11
Module : /opt/PixInsight/bin/PixInsight() [0x14096ad]
========================================================================================================================
8: /lib64/libpthread.so.0(+0x109f0) [0x7f748a0449f0]
7: /lib64/libc.so.6(strlen+0x2a) [0x7f748369ab5a](+0x2a [0x7f748369ab5a])
6: /lib64/libc.so.6(+0x39229) [0x7f7483649229]
5: /opt/PixInsight/bin/PixInsight() [0x5c560a]
4: /opt/PixInsight/bin/PixInsight() [0x5ced03]
3: /opt/PixInsight/bin/PixInsight() [0x45deeb]
2: /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f7483630580](+0xf0 [0x7f7483630580])
1: /opt/PixInsight/bin/PixInsight() [0x487219]
========================================================================================================================
terminate called after throwing an instance of 'pcl::EUnixSegmentationViolation'
/opt/PixInsight/bin/PixInsight.sh: line 19:  8293 Aborted                 (core dumped) $dirname/$appname $*

Offline NGC7789

  • PixInsight Old Hand
  • ****
  • Posts: 391
Re: Dump starting PI
« Reply #10 on: 2015 December 22 16:59:46 »
I think the lesson from this thread is that Fedora is too cutting edge. My recommendation is to stick with a more conservative distro like Mint. I've been very happy with it.