[GRASS5] bug reports for GRASS 5.7

[Glynn Clements]

Scott Mitchell wrote:

> So you start the program within the debugger using
> 
> gdb program_name (which is the full path to the grass module, in this 
> case probably something like 
> /usr/local/grass57-13_02_2004/bin/g.mapsets)

The actual program would be in etc/bin/cmd, e.g.

	/usr/local/grass57-13_02_2004/etc/bin/cmd/g.mapsets

Almost everything in the bin directory is a hard link to
etc/front.end.

> which will put you in to a gdb prompt.  From there, enter
> run -l
> 
> to start the program with -l as the argument.  When you get to the 
> error, it will put you back at the gdb prompt, and you can enter the 
> command "where" to get a traceback of where it happened in the program. 
>   Use "quit" to get out to your shell.
> 
> Actually, you can probably skip all that, because I decided to test my 
> instructions before sending, and my machine generates the error too.  
> So keep this for future reference, and Glynn, here are the results, I 
> wish they meant something to me:
> 
> (gdb) run -l
> Starting program: /usr/local/grass57-13_02_2004/bin/g.mapsets -l
> Reading symbols for shared libraries +++.. done
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x8fe1a528 in __dyld__dyld_start ()

This is a red herring; can you continue until you get the actual
SIGBUS signal?

-- 
Glynn Clements <glynn.clements at virgin.net>