Hi Piotr, If you set debugging to 512 (-v 512) the tiles will not be removed when a read error occurs. Then you can examine the tile file for possible problems. A common problem (but I don't think it is the one you are having) is that the host returns a 404 when the tile is not found on the server. The resulting .png file in that case is a text file and not an image file.
The png.c file is not a part of Xastir, so the error is being reported from a library. It will help to know which distribution you are using, which graphics library (Imagemagick or Graphicsmagick) and whether your build is configured to used curl or wget. Given that the error messages are memory related it would also be good to know how much memory your system has available and the window size you are using for xastir. 73, ...jerry KA6HLD On Mon, Aug 9, 2010 at 2:41 PM, Piotr Gluszenia Slawinski <[email protected]> wrote: > Hello. I've just synced to cvs and i try to use tiled version > of OSM maps. > > unfortunatelly, i get errors like : > > xastir: memory allocation failed > `/home/curious/.xastir/OSMtiles/cycle/10/552/341.png' @ > error/png.c/ReadOnePNGImage/1781. > xastir: corrupt image `/home/curious/.xastir/OSMtiles/cycle/10/552/341.png' > @ error/png.c/ReadPNGImage/3043. > Removing /home/curious/.xastir/OSMtiles/cycle/10/552/341.png > > tangogps works fine. i am getting same error no matter if sharing > with tangogps is enabled or not. tangogps works fine. > > > -- > _______________________________________________ > Xastir mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
