Running Gerris through a debugger

From Gerris

(Difference between revisions)
Jump to: navigation, search
Revision as of 16:15, 9 August 2012
GeordieMcBain (Talk | contribs)
(new page)
← Previous diff
Current revision
GeordieMcBain (Talk | contribs)
(improved precision of link; corrected heading syntax)
Line 1: Line 1:
-Running Gerris through a debugger such as [http://www.gnu.org/software/gdb GDB], particularly via a graphical user interface such as [http://www.gnu.org/software/ddd DDD] as suggested in the course lesson on [[Programming the Advection Scheme]], is one way to find out what the program is doing line by line. +Running Gerris through a debugger such as [http://www.gnu.org/software/gdb GDB] particularly via a graphical front-end like [http://www.gnu.org/software/ddd DDD], as suggested in the [[Programming the Advection Scheme#simulation_run|programming course]], is one way to find out exactly what the program is doing line by line.
-== Running Gerris through GDB+==Running Gerris through GDB==
This is different to post-mortem debugging with GDB as suggested in the instructions for [[How to report bugs]]: for that GDB is called on a core-dump file. Here it's called with the binary and its arguments so the <code>--args</code> flag is needed; i.e. GDB is launched by prepending <code>gdb --args</code> to the [[Gerris]] command line; e.g. This is different to post-mortem debugging with GDB as suggested in the instructions for [[How to report bugs]]: for that GDB is called on a core-dump file. Here it's called with the binary and its arguments so the <code>--args</code> flag is needed; i.e. GDB is launched by prepending <code>gdb --args</code> to the [[Gerris]] command line; e.g.

Current revision

Running Gerris through a debugger such as GDB particularly via a graphical front-end like DDD, as suggested in the programming course, is one way to find out exactly what the program is doing line by line.

Running Gerris through GDB

This is different to post-mortem debugging with GDB as suggested in the instructions for How to report bugs: for that GDB is called on a core-dump file. Here it's called with the binary and its arguments so the --args flag is needed; i.e. GDB is launched by prepending gdb --args to the Gerris command line; e.g.

 $ gdb --args gerris2D vorticity.gfs

then start the program and execute the next line, one at a time...

 (gdb) start
 (gdb) next
Personal tools
communication