Editing FAQ
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 119: | Line 119: | ||
*# 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. | *# 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 that prompt, run `gdb -p <em>PID</em>` where <em>PID</em> is the process ID noted previously. | ||
*# at the gdb prompt, | *# 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: | * 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. | *# 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 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. | *# 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`.) | *# 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. | ||
==I do not see any output of my script until it has finished?== | ==I do not see any output of my script until it has finished?== |