> I mostly used kdbg which is a kde front-end to gdb. I would typically run
> things through valgrind to find problem spots, and then put in breakpoints
> in the relevant places in the code and step through carefully with the
> debugger.
I use ddd, another GUI interface for gdb.
When building Matt you need remove the object modules, and rebuild with
the CFLAGS (and FCFLAGS if calling Fortran routines too) including the
-g option. Then to build and install I do this
make "FCFLAGS=-g"; make install
but you could configure with these flags set as environment variables
or in your config.site. (See $STARLINK_DIR/etc/config.site).
I think Tim builds with debugging switched on all the time.
> More recently I've been having fun with newer versions of valgrind which
Which version number is that Ed?
> memory to see when/where they were allocated etc.). If you'd like more
> information on that I could dig up my notes for you...
I'd find that useful too.
Malcolm
--
Scanned by iCritical.
|