[ gpsdrive ] Infinite loop when starting gpsdrive in mapnik-mode

[Hamish]

Jannis wrote:
> gpsdrive will enter an infinite loop when started in mapnik mode (CPU
> goes to 100%, can only be killed with SIGKILL).

what if you rename ~/.gpsdrive/gpsdriverc to something else so you start
with a fresh one (in case it got corrupted)

> When I edit my gpsdriverc to not use mapnik mode, gpsdrive
> starts up as normal displaying a raster-map. I can then use the
> Map Mode menu to enable mapnik and it works as expected. So this is
> probably not a problem with mapnik (it works using the
> generate_image.py-script, too).
> I'm using gpsdrive version "Version 2.10pre7.svn;
> $Id: gpsdrive.c 2297 2009-02-10 13:11:38Z rosscoe $". When I start
> gpsdrive with -D 99 it will loop enter the loop about here:
> 
> "...
> read_icon(gauge.png): FOUND    
> /usr/local/share/gpsdrive/pixmaps/gauge.png
> expose_compass()
> expose_mini_cb()
> calldrawmarker_cb()
> expose_gpsfix()
> event:ff51 key:Q
> Key pressed: ff51
> calldrawmarker_cb()
> expose_gpsfix()
> calldrawmarker_cb()
> expose_gpsfix()
> drawmacker_cb()
> rendering mapnik map ....
> expose_cb()
>   setting borderlimit to 112
>   setting size of mapview to 664x564 px
> display_status(Keine Karte für diese Position verfügbar!)
> calcxy(_,_,-38767,-28969,1) ---> 50,9.07045

          ^^^ is _,_ normal??

> map zoomed!
> expose_mini_cb()
> draw_grid()
> calcxytopos(0,0,_,_,1) ---> 48.1512,11.5588
> calcxytopos(0,564,_,_,1) ---> 48.1151,11.5588
> calcxytopos(664,0,_,_,1) ---> 48.1512,11.6014
> calcxytopos(664,564,_,_,1) ---> 48.1151,11.6014
> Draw Grid: (nan,nan) - (nan,nan) Step nan for Ef.Scale 0
> Zoom 1
> Draw Grid: (nan) Iterations for lat
> Draw Grid: (nan) Iterations for lon
> Draw Grid: (nan,nan) - (nan,nan) Step nan for Ef.Scale 0
> Zoom 1
> Draw Grid: (nan) Iterations for lat
> Draw Grid: (nan) Iterations for lon
> Draw Grid: (nan,nan) - (nan,nan) Step nan for Ef.Scale 0
> Zoom 1
> Draw Grid: (nan) Iterations for lat
> Draw Grid: (nan) Iterations for lon
> ..."
> 
> Anyone got a good idea what this may be?


check for a map scale set to 0 in your map_koords.txt file?
I don't know.

In r2309 I've just committed some code to draw_grid.c to check that
the grid line distance step is not nan or zero before it tries to
find a nice grid size in range. So no more getting stuck in the loop,
but it hasn't solved the true cause.


Hamish