[GRASS5] Debugging modules ...

[David D Gray]

"Eric G . Miller" wrote:
> 
> I did the following and was able to run a module with DDD (uses gdb).
> 
> In grass/src/CMD/head/head set the following (don't use any
> optimization)
> 
> COMPILE_FLAGS       = -g
> LDFLAGS             =
> 
> Then, for whatever module delete the OBJ* dir and rerun gmake5.  Then
> run gdb (or DDD in this case) on the executable in
> <path>/grass-5.0b/etc/bin/<main | contrib>/cmd/<module> .  The
> executable in <path>/grass-5.0b/bin/ is not what you're interested in.
> 
> --

Eric,

This is mainly what I do (do you find the mouse behaviour a bit
quirky..?) In fact I have a whole tree with these flag options for
debugging : only too often you have to trace into library calls. But I
have had to run ddd through the GRASS environment, eg through the
terminal that opens GRASS. It mostly gets confused when you try to trace
into a forked process - do you have any insights on this?

Can I also suggest using a malloc debugger for some traces - I use the
preloadable NJAMD (Not Just Another Malloc Debugger) from:

http://fscked.org/proj/njamd.shtml


David

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'