Debugging Octave: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Emacs) |
||
| Line 16: | Line 16: | ||
== Emacs == | == Emacs == | ||
[http: link to emacs manual | |||
In short: | |||
To start Octave in debug mode within emacs type | |||
<code> | |||
M-x gud-gdb | |||
<code> | |||
then change the command in the minibuffer to | |||
<code> | |||
Run gud-gdb (like this): /path/to/octave/source/tree/run-octave -gud | |||
</code> | |||
For more info use this | |||
[http://www.gnu.org/software/emacs/manual/html_node/emacs/Debuggers.html#Debuggers link] | |||
to the emacs manual section on debuggers operation | |||
== ddd == | == ddd == | ||
Revision as of 10:41, 18 July 2012
Preliminaries
Since compilation of all the source from scratch can take long it is good to have a source folder where most of the source has been compiled. To do this ...
Workflow
- Clone the repository
- Regenerate the scripts
- Configure
Basic debugging processes
Error & trace the stack
Tools for debugging
GBD
Most used commands
Emacs
In short:
To start Octave in debug mode within emacs type
M-x gud-gdb
then change the command in the minibuffer to
Run gud-gdb (like this): /path/to/octave/source/tree/run-octave -gud
For more info use this
link
to the emacs manual section on debuggers operation
ddd