Author Topic: Losing recorded macros  (Read 2095 times)

warnerrs

  • Senior Community Member
  • Posts: 114
  • Hero Points: 4
Losing recorded macros
« on: October 06, 2015, 03:28:11 pm »
If I record a macro and save it, it appears in the List Macros.. dialog and it works. But when I exit and restart, it no longer shows up in the List Macros.. dialog. I see that SE is seg faulting on exit, so I'm guessing that's the problem.


patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1092
  • Hero Points: 100
Re: Losing recorded macros
« Reply #1 on: October 06, 2015, 03:47:38 pm »
Haven't seen any crashes on exit yet.  If core dumps are enabled on your system, did it produce a core dump?  (it would be in whatever the working directory of the process at the time it crashed, which is usually the project root if you've got a project open).

warnerrs

  • Senior Community Member
  • Posts: 114
  • Hero Points: 4
Re: Losing recorded macros
« Reply #2 on: October 06, 2015, 05:43:09 pm »
Sorry no core. Disabled by IT.


patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1092
  • Hero Points: 100
Re: Losing recorded macros
« Reply #3 on: October 06, 2015, 06:27:40 pm »
No problem.  Do you have gdb installed on that system?  If so I can tell you how to launch it from there, and then get a stack backtrace if it crashes for you again.

warnerrs

  • Senior Community Member
  • Posts: 114
  • Hero Points: 4
Re: Losing recorded macros
« Reply #4 on: October 06, 2015, 07:18:44 pm »
Yes gdb is installed.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1092
  • Hero Points: 100
Re: Losing recorded macros
« Reply #5 on: October 06, 2015, 07:37:48 pm »
Ok, instructions below.  And note that for step 1, it does really mean vs_exe, not the vs script that you usually run.

  • In a terminal window, run the following.  This will start up gdb, but not start SlickEdit: gdb SE_INSTALL_DIR/bin/vs_exe
  • You should be at a prompt that says (gdb).  The following command will run SlickEdit, feel free to add any parameters you usually pass to SlickEdit on the command line after the "+new": run +new
  • SlickEdit should be running.  Once a crash occurs, the (gdb) prompt should re-appear in the terminal window.  At the prompt, type in: bt
  • Copy and save any output from the bt command to send to us, and then exit gdb with the quit command.

warnerrs

  • Senior Community Member
  • Posts: 114
  • Hero Points: 4
Re: Losing recorded macros
« Reply #6 on: October 08, 2015, 08:40:49 pm »
Quote
#0  0x00000000005d6a33 in index_callable(int) ()
#1  0x00000000005bac1f in p_delete_unused_op() ()
#2  0x00000000005daf95 in run_proc(int) ()
#3  0x00000000005cb27e in run_proc_immediate2 ()
#4  0x00000000005cbf54 in run_proc_immediate(int, int, VSARGTYPE*, int, int) ()
#5  0x000000000078196b in execute_command(VSLSTR*, int, int*, slickedit::SEString const&) ()
#6  0x0000000000709e02 in vsaexecutelstr(unsigned char*, int, VSLSTR*) ()
#7  0x000000000070a1f2 in vsaExecute(char const*, char const*) ()
#8  0x000000000070b15b in vsExecute ()
#9  0x000000000051d6fc in vsCtlMainMdi::menuItemTriggered(int) ()
#10 0x0000000000514ac0 in vsCtlMainMdi::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) ()
#11 0x00007ffff6ed51c1 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtCore.so.4
#12 0x00000000013b5812 in vsCtlMenuBar::vsctlmenubar_triggered(QAction*) ()
#13 0x00007ffff6ed51c1 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtCore.so.4
#14 0x00007ffff7427b62 in QAction::triggered(bool) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#15 0x00007ffff7427d23 in QAction::activate(QAction::ActionEvent) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#16 0x00007ffff78db128 in ?? () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#17 0x00007ffff78e0d82 in ?? () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#18 0x00000000013b5cb6 in vsCtlMenu::mouseReleaseEvent(QMouseEvent*) ()
#19 0x00007ffff747ffc4 in QWidget::event(QEvent*) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#20 0x00007ffff78e231b in QMenu::event(QEvent*) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#21 0x00007ffff742dab4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#22 0x00007ffff7432b1e in QApplication::notify(QObject*, QEvent*) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#23 0x00007ffff6ec188c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtCore.so.4
#24 0x00007ffff742ea82 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
   from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#25 0x00007ffff74acc94 in ?? () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#26 0x00007ffff74ab3ea in QApplication::x11ProcessEvent(_XEvent*) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#27 0x00007ffff74d2bb2 in ?? () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#28 0x00000030bc43feb2 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#29 0x00000030bc443d68 in ?? () from /lib64/libglib-2.0.so.0
#30 0x00000030bc443f1c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#31 0x00007ffff6eef91f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtCore.so.4
#32 0x00007ffff74d284e in ?? () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtGui.so.4
#33 0x00007ffff6ec02d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtCore.so.4
#34 0x00007ffff6ec0527 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtCore.so.4
#35 0x00007ffff6ec57e7 in QCoreApplication::exec() () from /user/ryanw/apps/slickedit/20.0.0.4/bin/libQtCore.so.4
#36 0x000000000053d830 in vmain(int, char**) ()
#37 0x00000000013b4b09 in xmain ()
#38 0x00000000004fa649 in main ()

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4791
  • Hero Points: 388
Re: Losing recorded macros
« Reply #7 on: October 08, 2015, 08:51:13 pm »
Looks like it's crashing accessing some data in the state file. Try deleting the "vslick.stu" file in your config directory (back it up first just in case). It will get recreated after applying your config changes the next time your run SlickEdit. Hopefully, that will fix your problem.

warnerrs

  • Senior Community Member
  • Posts: 114
  • Hero Points: 4
Re: Losing recorded macros
« Reply #8 on: October 09, 2015, 02:25:32 pm »
That worked. Thanks.