153
edits
FAQ: Difference between revisions
Jump to navigation
Jump to search
→Collecting gdb backtrace information
m (adjusted list level for gdb) |
|||
| Line 114: | Line 114: | ||
*# 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, execute `thread apply all bt`. (If this returns a list longer than one page you may need to 'continue' by typing `c`.) | *# at the gdb prompt, execute `set logging on` to save all output to a text file (default will be `gdb.txt`. If you want a different location or filename you can execute `set logging file C:\path\to\file.txt` first). | ||
*# | *# execute `thread apply all bt`. (If this returns a list longer than one page you may need to 'continue' by typing `c`.) | ||
*# execute `quit` to leave gdb. | |||
*# append that text file 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 `set logging on` to save all output to a text file (default will be `gdb.txt`. If you want a different location or filename you can execute `set logging file C:\path\to\file.txt` first). | |||
*# 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`.) | ||
*# | *# append the text file 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?== | ||