[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #41817] UI crash adding a comment line to an Octave .m file.
Date: Tue, 11 Mar 2014 04:23:01 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130917 Firefox/17.0 Iceweasel/17.0.9

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

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


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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]