[GRASS-dev] g.region -g crashes in a latlon location

[Glynn Clements]

Maciej Sieczka wrote:

> > In any case, this doesn't help identify the real problem. Can you
> > step through the g.region code from the beginning and find where in 
> > g.region (or the GRASS libraries) that it's going out of control?
> 
> If you can tell how to do it I'd try.

$ gdb g.region
> break main
> run -g
Starting program: /usr/local/src/grass/svn/dist.i686-pc-linux-gnu/bin/g.region -g
...
Breakpoint 1, main (argc=2, argv=0xbfc241a4) at main.c:31
31		int print_flag = 0;
> next
35		int row_flag=0, col_flag=0;
> 

Then keep pressing Return (which repeats the last command) until it
crashes.

The crash will probably have occured during a call to some library
function. Set a breakpoint on that function ("break <name>") then type
"run -g" to start again. When it hits the first breakpoint (main),
type "cont". When it hits the second breakpoint, start single-stepping
(next, Return, Return ...) until it crashes.

Repeat this procedure until the crash occurs on a statement which
either isn't a function call or which isn't a GRASS function.

> Can you reproduce the crash? Anybody else?

Not me.

-- 
Glynn Clements <glynn at gclements.plus.com>