Author Topic: V21.0.0.9 - unprompted? crash  (Read 548 times)

astromme

  • Community Member
  • Posts: 89
  • Hero Points: 0
V21.0.0.9 - unprompted? crash
« on: September 28, 2016, 02:12:38 am »
Linux, brief emulation.  It seems like I don't do anything, it just happens.. not sure if there's something in the background running that causes it.

Not sure if https://community.slickedit.com/index.php/topic,13759.msg54122.html is related - we have brief in common.

Code: [Select]
find ~/.slickedit/21.0.0/ -name "*crash*" returns nothing


SlickEdit Pro 2016 (v21.0.0.9 64-bit)
Build Date: September 22, 2016
Emulation: Brief

OS: Linux
OS Version: Linux Mint 17.3 Rosa
Kernel Level: 3.19.0-32-generic
Build Version: #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015
Processor Architecture: x86_64

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 821
  • Hero Points: 47
Re: V21.0.0.9 - unprompted? crash
« Reply #1 on: September 28, 2016, 01:39:57 pm »
I'm wondering if a core file got dropped anywhere.  If your ulimits allow them, cores get dropped in the working directory of the process.  If you had a project open, that would probably be in the root directory of the project.   (running the pwd command in the SlickEdit command line will tell you the working directory).

The other possibility for that version of Ubuntu is that apport is enabled, and handled the crash.  Take a look in /var/crash, and see if there is a file for vs_exe. 

If you find a core or crash file, upload it to http://support.slickedit.com, using 14079 as the case number.

If you can't find a core or crash, and you can get the crash to happen regularly, probably the way to get the stack trace of the crash is to run SlickEdit under gdb.   In a terminal window, run "gdb YOUR_INSTALL_DIR/bin/vs_exe".  When you get the gdb prompt, just type in run, SlickEdit should start as usual.  When the crash happens, you should be able to go back to the gdb prompt and type in "bt" to get a stack trace of the crash location, which you can post on the forum. 

astromme

  • Community Member
  • Posts: 89
  • Hero Points: 0
Re: V21.0.0.9 - unprompted? crash
« Reply #2 on: September 28, 2016, 05:45:30 pm »
Code: [Select]
(gdb) r
Starting program: /opt/slickedit-pro2016/bin/vs_exe
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffecd96700 (LWP 15538)]
[New Thread 0x7fffe6021700 (LWP 15540)]
[New Thread 0x7fffe5f20700 (LWP 15541)]
[New Thread 0x7fffe5e1f700 (LWP 15542)]
[New Thread 0x7fffe5d1e700 (LWP 15543)]
[New Thread 0x7fffe5c1d700 (LWP 15544)]
[New Thread 0x7fffe5b1c700 (LWP 15545)]
[New Thread 0x7fffe5a1b700 (LWP 15546)]
[Thread 0x7fffe6021700 (LWP 15540) exited]
[New Thread 0x7fffe6021700 (LWP 15547)]
[Thread 0x7fffecd96700 (LWP 15538) exited]
[New Thread 0x7fffecd96700 (LWP 15548)]
[Thread 0x7fffecd96700 (LWP 15548) exited]
[New Thread 0x7fffecd96700 (LWP 15563)]
[Thread 0x7fffecd96700 (LWP 15563) exited]
[New Thread 0x7fffecd96700 (LWP 15564)]
[New Thread 0x7fffe5255700 (LWP 15565)]
[New Thread 0x7fffe4a54700 (LWP 15566)]
[Thread 0x7fffecd96700 (LWP 15564) exited]
[Thread 0x7fffe5255700 (LWP 15565) exited]
[Thread 0x7fffe4a54700 (LWP 15566) exited]
[New Thread 0x7fffecd96700 (LWP 15567)]
[New Thread 0x7fffe8b81700 (LWP 15568)]
[Thread 0x7fffe8b81700 (LWP 15568) exited]
[Thread 0x7fffecd96700 (LWP 15567) exited]
[New Thread 0x7fffecd96700 (LWP 15569)]
[Thread 0x7fffecd96700 (LWP 15569) exited]
[New Thread 0x7fffecd96700 (LWP 15571)]
[Thread 0x7fffecd96700 (LWP 15571) exited]
[New Thread 0x7fffecd96700 (LWP 15574)]
[Thread 0x7fffecd96700 (LWP 15574) exited]
[New Thread 0x7fffecd96700 (LWP 15575)]
[Thread 0x7fffecd96700 (LWP 15575) exited]
[New Thread 0x7fffecd96700 (LWP 15577)]
[Thread 0x7fffecd96700 (LWP 15577) exited]
[New Thread 0x7fffecd96700 (LWP 15618)]
[Thread 0x7fffecd96700 (LWP 15618) exited]
[New Thread 0x7fffecd96700 (LWP 15619)]
[Thread 0x7fffecd96700 (LWP 15619) exited]
[New Thread 0x7fffecd96700 (LWP 15621)]
[Thread 0x7fffecd96700 (LWP 15621) exited]
[New Thread 0x7fffecd96700 (LWP 15645)]
[Thread 0x7fffecd96700 (LWP 15645) exited]
[New Thread 0x7fffecd96700 (LWP 15646)]
[Thread 0x7fffecd96700 (LWP 15646) exited]
[New Thread 0x7fffecd96700 (LWP 15647)]
[Thread 0x7fffecd96700 (LWP 15647) exited]
[New Thread 0x7fffecd96700 (LWP 15648)]
[Thread 0x7fffecd96700 (LWP 15648) exited]
[New Thread 0x7fffecd96700 (LWP 15650)]
[Thread 0x7fffecd96700 (LWP 15650) exited]
[New Thread 0x7fffecd96700 (LWP 15695)]
[Thread 0x7fffecd96700 (LWP 15695) exited]
[New Thread 0x7fffecd96700 (LWP 15741)]
[Thread 0x7fffecd96700 (LWP 15741) exited]
[New Thread 0x7fffecd96700 (LWP 15765)]
[Thread 0x7fffecd96700 (LWP 15765) exited]
[New Thread 0x7fffecd96700 (LWP 15805)]
[Thread 0x7fffecd96700 (LWP 15805) exited]
[New Thread 0x7fffecd96700 (LWP 15831)]
[Thread 0x7fffecd96700 (LWP 15831) exited]
[New Thread 0x7fffecd96700 (LWP 15865)]
[Thread 0x7fffecd96700 (LWP 15865) exited]
[New Thread 0x7fffecd96700 (LWP 15866)]
[Thread 0x7fffecd96700 (LWP 15866) exited]
[New Thread 0x7fffecd96700 (LWP 15867)]
[Thread 0x7fffecd96700 (LWP 15867) exited]
[New Thread 0x7fffecd96700 (LWP 15869)]
[Thread 0x7fffecd96700 (LWP 15869) exited]
[New Thread 0x7fffecd96700 (LWP 15904)]
[Thread 0x7fffecd96700 (LWP 15904) exited]
[New Thread 0x7fffecd96700 (LWP 15912)]
[Thread 0x7fffecd96700 (LWP 15912) exited]
[New Thread 0x7fffecd96700 (LWP 15935)]
[Thread 0x7fffecd96700 (LWP 15935) exited]
[New Thread 0x7fffecd96700 (LWP 15958)]
[Thread 0x7fffecd96700 (LWP 15958) exited]
[New Thread 0x7fffecd96700 (LWP 15982)]
[Thread 0x7fffecd96700 (LWP 15982) exited]
[New Thread 0x7fffecd96700 (LWP 15983)]
[Thread 0x7fffecd96700 (LWP 15983) exited]
[New Thread 0x7fffecd96700 (LWP 16007)]
[Thread 0x7fffecd96700 (LWP 16007) exited]
[New Thread 0x7fffecd96700 (LWP 16087)]
[Thread 0x7fffecd96700 (LWP 16087) exited]
[New Thread 0x7fffecd96700 (LWP 16092)]
[Thread 0x7fffecd96700 (LWP 16092) exited]
[New Thread 0x7fffecd96700 (LWP 16178)]
[Thread 0x7fffecd96700 (LWP 16178) exited]
[New Thread 0x7fffecd96700 (LWP 16179)]
[Thread 0x7fffe5e1f700 (LWP 15542) exited]
[Thread 0x7fffe5a1b700 (LWP 15546) exited]
[Thread 0x7fffe5f20700 (LWP 15541) exited]
[Thread 0x7fffe5c1d700 (LWP 15544) exited]
[Thread 0x7fffe5d1e700 (LWP 15543) exited]
[Thread 0x7fffe5b1c700 (LWP 15545) exited]
[Thread 0x7fffe6021700 (LWP 15547) exited]
[Thread 0x7fffecd96700 (LWP 16179) exited]
[Inferior 1 (process 15537) exited normally]
(gdb) bt
No stack.

Will turn on cores and see if I get anything useful.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 821
  • Hero Points: 47
Re: V21.0.0.9 - unprompted? crash
« Reply #3 on: September 28, 2016, 05:58:39 pm »
That doesn't look like a crash, it looks like the process just called exit().  (still weird, but not something gdb would give us any info for) Was the crash behavior the same for that run or did it act differently?

astromme

  • Community Member
  • Posts: 89
  • Hero Points: 0
Re: V21.0.0.9 - unprompted? crash
« Reply #4 on: September 28, 2016, 06:25:53 pm »
Agreed.  Yes it was - it just closed on me.. in the other issue I originally referenced there was some reference to reloading plain text files.. I think I have some .lnt files that get regenerated from time to time.. could this be crashing on Windows and just exiting on Linux?

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 821
  • Hero Points: 47
Re: V21.0.0.9 - unprompted? crash
« Reply #5 on: September 28, 2016, 07:22:33 pm »
I'm not sure yet.  I can't tell if there's any relation to the post you linked either.

We can try to get a system call trace, that might lead us to where it's exiting.

From a terminal, you can start SlickEdit via strace like this: 
Code: [Select]
strace -f -o /tmp/trace.txt YOUR_INSTALL_DIR/bin/vs_exe +new
Run it till it exits on you.  /tmp/trace.txt will be fairly large, so gzip it, and then upload it on the http://support.slickedit.com page, with 14079 as the case number.  And update the post to let us know you uploaded it.