[Octave-bug-tracker] [bug #41817] UI crash adding a comment line to an Octave .m file.

[John W. Eaton]

Follow-up Comment #7, bug #41817 (project octave):

The problem with debugging is that /usr/local/bin/octave is just a small
wrapper program that gives up the controlling terminal and then execs the
GUI.

You can either debug the octave-gui binary (but that won't always work
properly because it will still have a controlling terminal) or you can run a
command like this at the Octave prompt to start gdb in a separate terminal
window and attach it to the octave-gui process:


cmd = sprintf ("gnome-terminal --command 'gdb -p %d'", getpid ());
system (cmd, false, "async");


Once the "(gdb)" prompt appears in the terminal window, type


continue


to allow Octave to resume execution, then generate the crash.  At that point,
you should be able to get a stack trace in the gdb window.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41817>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/