FAQ: Difference between revisions

* '''Collecting gdb backtrace information''' The following instructions can help you gather troubleshooting information that may help developers identify the problem if the above steps are ineffective:

** if Octave is 'hanging' (the process is remaining open):

**# attempt to start the Octave GUI  

**# with the program stalled (either at the GUI, or with the black terminal window), open the Task Manager (right click on taskbar, select Task manager), switch to the "Details" tab, find `octave-gui.exe` on that list, ad take note of the corresponding PID (process ID)

**# Open the folder where Octave is installed. You should find a file called `cmdshell.bat` in the main folder. Run that file, which should open a MSYS2 bash (command line) window.

**# At that prompt, run `gdb -p <em>PID</em>` where <em>PID</em> is the process ID noted previously.

**# at the gdb prompt, execute `thread apply all bt`.  (If this returns a list longer than one page you may need to 'continue' by typing `c`.)

**# copy and paste that output into a text file and append it to your trouble report at octave.discourse.group or bug report at bugs.octave.org.

** if Octave is immediately crashing and closing:

**# Open the folder where Octave is installed. You should find a file called `cmdshell.bat` in the main folder. Run that file, which should open a MSYS2 bash (command line) window.

**# At that prompt, run `gdb octave`. (that will start gdb attached to the octave executable.)

**# At the gdb prompt, execute `r --gui`.  That should attempt to start the Octave in GUI mode.  The gdb prompt should stay unresponsive as long as octave is running.

**# If octave crashes, the gdb prompt should become responsive again. execute `thread apply all bt`.  (If this returns a list longer than one page you may need to 'continue' by typing `c`.)

**# copy and paste that output into a text file and append it to your trouble report at octave.discourse.group or bug report at bugs.octave.org.