171
edits
FAQ: Difference between revisions
Jump to navigation
Jump to search
→Where do I get additional help?: +
(→MS Windows: added gdb notes for windows troublshooting.) |
ArunGiridhar (talk | contribs) Tags: Mobile edit Mobile web edit |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 12: | Line 12: | ||
<div class="tocinline">__TOC__</div> | <div class="tocinline">__TOC__</div> | ||
=== Support expectations === | |||
See [https://octave.org/support-expectations.html Support Expectations] | |||
Also this [https://www.commitstrip.com/en/2014/05/07/the-truth-behind-open-source-apps/ CommitStrip] | |||
=General= | =General= | ||
| Line 107: | Line 112: | ||
** '''Solution 3:''' Did you install Octave on a network-drive? Do you have the execution permissions? | ** '''Solution 3:''' Did you install Octave on a network-drive? Do you have the execution permissions? | ||
** '''Solution 4:''' Is your computer managed by your company? Does your administrator prohibit script execution? | ** '''Solution 4:''' Is your computer managed by your company? Does your administrator prohibit script execution? | ||
===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 `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: | |||
*# 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. | *# 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. | |||
*# 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?== | ||