255
edits
Debugging Octave: Difference between revisions
Jump to navigation
Jump to search
→Debugging oct-files
(→GDB) |
|||
| Line 19: | Line 19: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
start now the GNU debugger with octave | start now the GNU debugger with octave. On most Unixy systems, you can start gdb from within an Octave session by evaluating a command like | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
gdb | octave> system (sprintf ("gnome-terminal --command 'gdb -p %d'", getpid ()), "async"); | ||
</syntaxhighlight> | </syntaxhighlight> | ||
at the Octave prompt. This command will open a terminal window running gdb attached to the Octave process. At this point, Octave will be stopped. To tell Octave to continue, type | |||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
(gdb) | (gdb) continue | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Octave | at the gdb prompt. The symbols from your oct-file will only be available to gdb once the oct-file is loaded in Octave. To do that without executing any functions from the oct-file, you can ask Octave to display the help for the oct-file: | ||
<syntaxhighlight lang=" | <syntaxhighlight lang="bash"> | ||
octave | octave> help file | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Now halt execution of Octave by typing ctrl+c, you'll see again the gdb prompt. Set now a breakpoint in the line of interest | Now halt execution of Octave by typing ctrl+c, you'll see again the gdb prompt. Set now a breakpoint in the line of interest | ||
| Line 46: | Line 46: | ||
<syntaxhighlight lang="octave"> | <syntaxhighlight lang="octave"> | ||
octave | octave> x = file(y) | ||
</syntaxhighlight> | </syntaxhighlight> | ||
the debugger will stop on the above defined line and you can start debugging according to the manual of GNU debugger. | the debugger will stop on the above defined line and you can start debugging according to the manual of GNU debugger. | ||
= Tools for debugging = | = Tools for debugging = | ||