[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.

> Here's the result:

> Breakpoint 2, print_window (window=0x7fffd3fd5fe0, print_flag=3) at 
> printwindow.c:9

> (gdb)
> 37	    ew_dist1 =
> (gdb)
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007fa1ca1c369e in sincos (val=0.90594848802138783, 
> sin_val=0x7fffd37d7030, cos_val=0x7fffd37d7028) at GDapi.c:6265
> 6265	    *sin_val = sin(val);
> (gdb)

Okay, the full statement is:

    ew_dist1 =
	G_distance(window->east, window->north, window->west, window->north);

The next step would be to set a breakpoint on G_distance, and repeat.
But I already know that will lead to G_geodesic_distance().

Below that, there isn't actually anything which can cause a segfault. 
So, it's very much looking like a broken system.

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