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

[Yann Chemin]

This is on my system:
857                 print_window (&window, print_flag);
(gdb)

Program received signal SIGSEGV, Segmentation fault.
0x00007f13a64e5a7e in sincos () from /usr/lib/libgdal1.5.0.so.1

break print_window gives:

(gdb)
37          ew_dist1 =
(gdb)

Program received signal SIGSEGV, Segmentation fault.
0x00007fda5b45ca7e in sincos () from /usr/lib/libgdal1.5.0.so.1

break G_distance gives:

Breakpoint 3, G_distance (e1=25.075814295277777, n1=41.64570967638889,
e2=21.946861788888889,
    n2=41.64570967638889) at distance.c:84
84      {
(gdb)
85          if (projection == PROJECTION_LL)
(gdb)
G_distance (e1=25.075814295277777, n1=41.64570967638889, e2=21.946861788888889,
    n2=41.64570967638889) at distance.c:86
86              return G_geodesic_distance (e1, n1, e2, n2);
(gdb)
0x00007f4f967239d8 in G_geodesic_distance at plt () from
/usr/local/grass-7.0.svn/lib/libgrass_gis.so
Current language:  auto; currently asm
(gdb)
Single stepping until exit from function G_geodesic_distance at plt,
which has no line number information.
0x00007f4f96722ba8 in ?? () from /usr/local/grass-7.0.svn/lib/libgrass_gis.so
(gdb)
Cannot find bounds of current function
(gdb)

hope this helps
yann

2008/7/22 Maciej Sieczka <tutey at o2.pl>:
> Glynn Clements pisze:
>
>> Below that, there isn't actually anything which can cause a segfault.
>>  So, it's very much looking like a broken system.
>
> Gotcha! I'm using GCC 4.3.1 on amd64 Debian testing. Apparently it
> doesn't like GRASS default optimisation flags "-g -O2". When I override
> them it with e.g. "-pipe" alone, the segfault is gone.
>
> On another machine (Ubuntu Gutsy amd64) where GCC is 4.1.3, "-g -O2" has
> no side effects.
>
> Should GRASS enforce any optimisation flags by default?
>
> Maciek
>
> --
> Maciej Sieczka
> www.sieczka.org
>



-- 
Yann Chemin
International Rice Research Institute
Office: http://www.irri.org/gis
Perso: http://www.freewebs.com/ychemin