Editing Building on Ubuntu Virtual Machine
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
This page contains instructions on how to build Octave in an Ubuntu virtual machine in a Windows Host | This page contains instructions on how to build Octave in an Ubuntu virtual machine in a Windows Host. | ||
This page is both concise and self-contained to allow beginners to quickly develop code for Octave. The libraries and instructions have been tested in Ubuntu 20.04. | This page is both concise and self-contained to allow beginners to quickly develop code for Octave. The libraries and instructions have been tested in Ubuntu 20.04. | ||
Line 46: | Line 44: | ||
$ ./run-octave --gui | $ ./run-octave --gui | ||
>> system (sprintf ("gnome-terminal --command 'gdb -p %d'", getpid ()), "async"); | >> system (sprintf ("gnome-terminal --command 'gdb -p %d'", getpid ()), "async"); | ||
Apply a breakpoint at the function edit_variable (which will be hit in another thread from the current one, so apply breakpoint for all threads). | |||
(gdb) thread apply all break variable-editor.cc:1154 | |||
(gdb) thread apply all break | Continue. | ||
>> a = [1 2] | >> a = [1 2] | ||
In Octave, double click on the variable ‘a’. Now gdb should be at the breakpoint. Now backtrace 10 to show the calling information: | |||
(gdb) backtrace 10 | (gdb) backtrace 10 | ||
Apply a breakpoint at the function variable_editor_model::create (which will be hit in another thread from the current one, so apply breakpoint for all threads). | |||
(gdb) thread apply all break variable-editor-model.cc:928 | |||
(gdb) | |||
= Save and Patch = | = Save and Patch = | ||
: 8. Save your work and send patch. | : 8. Save your work and send patch. |