Author Topic: Red Hat 64 bit And SlickEdit  (Read 2163 times)

dathree

  • Community Member
  • Posts: 22
  • Hero Points: 1
Red Hat 64 bit And SlickEdit
« on: August 08, 2013, 09:09:24 pm »
Hello,
I am running Red Hat:
Hlnx3:142> uname -a
Linux Hlnx3 2.6.32-358.6.1.el6.x86_64 #1 SMP Fri Mar 29 16:51:51 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux

And when I attempt to start either the 64 or 32 bit version of SlickEdit, I get the following error:

./vs: line 38: 18711 Segmentation fault      (core dumped) "$VS_LAUNCH_BIN_PATH/$VS_LAUNCH_BIN_NAME"_exe "$@"

It's trying to tell me something, I am just not sure what.

Any help would be appreciated.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 881
  • Hero Points: 57
Re: Red Hat 64 bit And SlickEdit
« Reply #1 on: August 09, 2013, 03:43:01 pm »
Are you on version 17 or 18?

If you have gdb installed, see if you can find the core file it says it dumped.  (it should be in whatever the working directory of the editor at the time of the crash, which could be your home directory, or the root of your workspace if you have a workspace or project open).     Run the following to load the core file into gdb:  gdb YOUR_VS_INSTALL_PATH/bin/vs_exe PATH_TO_CORE_FILE

Once in gdb, type "bt" and press return, it should produce a stack trace.  Paste that stack trace into a reply, and I'll take a look and see if I can make any sense of it. 

The other alternative is to open a support issue, and then upload your core file, and we'll try to debug it from there. 

dathree

  • Community Member
  • Posts: 22
  • Hero Points: 1
Re: Red Hat 64 bit And SlickEdit
« Reply #2 on: August 09, 2013, 06:29:51 pm »
The backtrace is as follows:

Core was generated by `/work/apps/slickedit-32/bin/vs_exe'.
Program terminated with signal 11, Segmentation fault.
#0  0x0818ec0b in adjust_read_heap() ()
Missing separate debuginfos, use: debuginfo-install expat-2.0.1-11.el6_2.i686 fontconfig-2.8.0-3.el6.i686 freetype-2.3.11-14.el6_3.1.i686 glib2-2.22.5-7.el6.i686 glibc-2.12-1.107.el6.i686 libICE-1.0.6-1.el6.i686 libSM-1.2.1-2.el6.i686 libX11-1.5.0-4.el6.i686 libXau-1.0.6-4.el6.i686 libXcursor-1.1.13-2.el6.i686 libXext-1.3.1-2.el6.i686 libXfixes-5.0-3.el6.i686 libXi-1.6.1-3.el6.i686 libXinerama-1.1.2-2.el6.i686 libXrandr-1.4.0-1.el6.i686 libXrender-0.9.7-2.el6.i686 libXt-1.1.3-1.el6.i686 libuuid-2.17.2-12.9.el6_4.3.i686 libxcb-1.8.1-1.el6.i686 nss-softokn-freebl-3.12.9-11.el6.i686
(gdb) bt
#0  0x0818ec0b in adjust_read_heap() ()
#1  0x08182268 in read_state(VSLSTR*, m_s**, int*, unsigned char*, int, slickedit::SEArray<SIHvarConstruct>&) ()
#2  0x081980df in load_module(VSLSTR*, m_s**, int*, unsigned char*, int, int, slickedit::SEArray<SIHvarConstruct>&) ()
#3  0x0830e64b in execute_command(VSLSTR*, int, int*, slickedit::SEString const&) ()
#4  0x0830f864 in pshell_op() ()
#5  0x081a688f in run_proc(int) ()
#6  0x081914c7 in run_proc_immediate2 ()
#7  0x081923ac in run_proc_immediate(int, int, VSARGTYPE*, int, int) ()
#8  0x0830dc37 in se_call_proc(filewindow_t*, char const*, int, int, VSARGTYPE*) ()
#9  0x0824ac91 in se_init(VSINIT*) ()
#10 0x0820d9af in vsInit ()
#11 0x080d775c in vmain(int, char**) ()
#12 0x08d6b11a in xmain ()
#13 0x080b4457 in main ()
(gdb)

Thanks.

dathree

  • Community Member
  • Posts: 22
  • Hero Points: 1
Re: Red Hat 64 bit And SlickEdit
« Reply #3 on: August 09, 2013, 06:30:45 pm »

Yes, I am running version 18.  No hotfixes, as I have not been able to apply them yet.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 881
  • Hero Points: 57
Re: Red Hat 64 bit And SlickEdit
« Reply #4 on: August 09, 2013, 06:37:35 pm »
Ok, I'll start looking at this. 

If you rename ~/.slickedit/18.0.0/vslick.stu to something like vslick.bak, does it still crash when you try to start it up?

dathree

  • Community Member
  • Posts: 22
  • Hero Points: 1
Re: Red Hat 64 bit And SlickEdit
« Reply #5 on: August 09, 2013, 06:40:30 pm »

I tried your suggestion and it does still crash.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 881
  • Hero Points: 57
Re: Red Hat 64 bit And SlickEdit
« Reply #6 on: August 12, 2013, 01:41:18 pm »
Ok.  I haven't been able to reproduce anything like this so far.  I'm assuming from the stack trace that v18 has never started for you, is that correct? 

Does it make a difference if you launch it with a new config directory, like so:  SEINSTALLPATH/bin/vs +new -sc /tmp/empty_config

If launching with a clean config directory works, I'll probably have to look at some of your existing configuration from some previous version of SlickEdit to figure out what's going.

If launching from a clean config does not work, then:

1) Check the syslogs for messages about the recent crash.  There's probably just a generic "segfault at ..." message, but if there's anything that seems related above that message, post it.

2) System call trace, to give me a better idea of what's happening at the time of the crash.  To get the trace, run it like this, and then post the trace.txt file it produces:  strace -f -o trace.txt SEINSTALLPATH/bin/vs_exe +new

dathree

  • Community Member
  • Posts: 22
  • Hero Points: 1
Re: Red Hat 64 bit And SlickEdit
« Reply #7 on: August 12, 2013, 02:22:38 pm »
Setting the new config directory worked.  Unfortunately, this is a new OS install so there is not previous version to look at.  I am suspecting that the default for the config directory is the problem; though not with SE.  With this machine, my ~ (home directory) lives in a cloud.  And it does not have very much disk space.  Though, the config files are small, there must be some issue with writing it to the cloud.  If you would like to investigate that further, I am willing to help.

Also, the same command line worked for the 64-bit too.

How do I permanently set the config directory?  Will the application always work now that I ran the command above? Or do I need to do that every time?

Thank you for your help.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 881
  • Hero Points: 57
Re: Red Hat 64 bit And SlickEdit
« Reply #8 on: August 12, 2013, 03:11:17 pm »
While we usually don't recommend having the config directory on a network directory for speed reasons, it shouldn't crash. 

How much disk space do you have left?  Enough room to copy the new configuration directory you created to your home directory?  If you type in "mount", what sort of network mount is your home directory mounted as?  (NFS, AFS, etc...)

If you want to put the config directory on a local drive, either as a temporary workaround or a permanent change, you either have to pass it the -sc PATH command line argument everytime you start SlickEdit, or you can set the environment variable SLICKEDITCONFIG to point to the config directory you want in your dotfiles.  The config directory holds all of your preferences and other settings, so you don't want to have it in /tmp, otherwise you'll lose your settings every time the system reboots.