Tux Commander / Discussion / Open Discussion: Segmentation fault with TuxCmd

Raoul Snidjik - 2004-09-26

I've tried three different releases of TuxCmd, and each one gives me this message when I try to launch the program:

Runtime error 230 at 08060E05
Segmentation fault

Then back to the prompt.

Any ideas? This file manager looks great, but for some reason I can't get it to start.

Thanks.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Raoul Snidjik - 2004-09-26
  
  Oh, I forgot: I'm running Fedora Core 2.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Tomas Bzatek - 2004-11-20
  
  The other people reported this issue too, however the problem exists on Fedora Core 2 only. I suspect NPTL-enabled kernel and NPTL compiled glibc, which causes problems also on the other distros.
  
  Could you please test it on Fedora Core 3, which has been released recently?
  
  I have no solution for this at the moment, this is a bug in Kylix compiler, which generates badly linked binaries.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Sebastian Lempert - 2005-01-20
  
  Tux Commander 0.5.93 development version (http://prdownloads.sourceforge.net/tuxcmd/tuxcmd-dev-0.5.39-bin.tar.bz2?download) works fine for me - I am using Fedora Core 3.
  
  Thank you for this great file manager. I am curious about your next release at the end of january. For me the most wanted feature is the find file function ... I hope it will be integrated in your next release!
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Tomas Bzatek - 2005-01-24
    
    Yes, it will be integrated in the upcoming release :-)
    
    I've been testing Tux Commander with Fedora Core 3 and it seems to be working smooth even with the binary gnome-vfs module. The segfault probably affects only Fedora Core 2.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Milan Horák - 2005-01-31
  
  Hi :o)
  
  Using slackware-current, tuxcmd -> Segmentation fault with no additional info. With --debug it's the same.
  Any ideas ? 0.5.64 binary
  
  Stranger
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Tomas Bzatek - 2005-02-04
    
    Could you please report your kernel version, glibc version, gcc version, if you have NPTL enabled or do if you're use any SELINUX or grsec extensions? Also, please check the binary with ldd if there are no missing libraries.
    
    You can also try to export LD_ASSUME_KERNEL=2.4 and then run the binary.
    
    This is caused by the incompatibility of Kylix compiler and I can hardly fix these issues. I am considering of making tuxcmd compatible with FPC, which could hopefully fix all these issues.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Segmentation fault with TuxCmd

Forums

Help

Segmentation fault with TuxCmd

Segmentation fault with TuxCmd

Forums

Help

Segmentation fault with TuxCmd document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Segmentation fault with TuxCmd