[mkgmap-dev] How to solve/debug weird problem
From Johannes Formann johannes at formann.de on Sat Jan 22 14:28:24 GMT 2011
Hi Marko, Marko Mäkelä <marko.makela at iki.fi> wrote: > On Thu, Jan 20, 2011 at 10:25:27PM +0100, Johannes Formann wrote: > >> --add-pois-to-areas --adjust-turn-headings --drive-on-right > >> --check-roundabouts --remove-short-arcs=3.3 --net --route --gmapsupp > >> --tdbfile --index M0001736.TYP > >> > >> You might try removing all of them first. If it does not crash, add > >> --route (which should imply --net). > > > >Starting without those options > >java -Xms256m -Xmx2560m -ea -jar mkgmap.jar --max-jobs=1 --latin1 > >--code-page=1252 -c /home/osm/build/template.args > > It's great that it crashes even without --route. I think that you should > put back the --remove-short-arcs=3.3, so that you will get rid of the > 'zero length arc' warnings, maybe except the ones about splitting looped > ways. > > Now, what if you use a template.args where you remove all files after > the problematic tile? Try to find out which tile it is. Your sample > output mentions two different tile files around the crash: 59420055 and > 59420066. If you cannot modify the assertion message to display the file > name, you can use 'binary search' on the template.args file, removing > half the tiles until it no longer crashes. Making some binary search with java -Xms256m -Xmx2560m -ea -Dlog.config=logging.properties -jar mkgmap.jar --max-jobs=1 --latin1 --code-page=1252 --remove-short-arcs=3.3 -c /home/osm/build/template.args 47-94: crashes 70-94: won't 47-70: crashes 47-59: won't 59-70: crashes 59-64: won't 65-70: crashes 65-67: crashes 67: won't 66: crashes Put it online: http://radkarte.formann.de/59420066.osm.gz > By the way, which mkgmap version are you using? "trunk"/Checked out revision 1792. > Unrelated to this mkgmap bug (or insufficient diagnostics), is there a > reason why you are still using the osm.bz2 input? The osm.pbf is more > compact and can be split quicker. I had once tried it, but the mainline splitter hadn't support for it yet IIRC, after that forgotten to recheck, since it runs usually fully automated once a week in the night. greetings Johannes
- Previous message: [mkgmap-dev] How to solve/debug weird problem
- Next message: [mkgmap-dev] How to solve/debug weird problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list