Debugging Octave: Difference between revisions
Jump to navigation
Jump to search
m (→Workflow) |
m (Added chapter "Debugging oct-files") |
||
| Line 11: | Line 11: | ||
= Basic debugging processes = | = Basic debugging processes = | ||
== Error & trace the stack == | == Error & trace the stack == | ||
= Debugging oct-files = | |||
= Tools for debugging = | = Tools for debugging = | ||
Revision as of 11:00, 23 August 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.
- Compile the code.
- Start debugging.
Basic debugging processes
Error & trace the stack
Debugging oct-files
Tools for debugging
GBD
To start Octave under gdb use the script run-octave at the top level of the source tree and run it with the command-line option -g like this
cd /octave/source/tree
./run-octave -g
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