Recent crashes when searching on device
Hi There have now been a few reports of problems searching on some devices with the latest version of mkgmap. It seems that it occurs when a gmapsupp.img is created directly by mkgmap and sent to the device. In other words the index itself has nothing to do with the problem, if this is correct. This is probably good news since there are not too many changes to stuff outside of the index itself. So could people confirm that when they see crashes they are not installing via mapsource, and what GPS device they are using? ..Steve
On Wed, Mar 02, Steve Ratcliffe wrote:
There have now been a few reports of problems searching on some devices with the latest version of mkgmap.
It seems that it occurs when a gmapsupp.img is created directly by mkgmap and sent to the device. In other words the index itself has nothing to do with the problem, if this is correct.
I see this with --index and without --index. So yes, it looks like the index itself has nothing to do with the problem. Going back to mkgmap-r1866 solved the problem for both cases for me.
So could people confirm that when they see crashes they are not installing via mapsource, and what GPS device they are using?
Yes, I'm not installing via mapsource, but copy the gmapsupp.img file directly to the device. It's a GPSmap 62s. I can try the 60CSx tonight, too, haven't done yet. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
On Wed, Mar 02, Thorsten Kukuk wrote:
On Wed, Mar 02, Steve Ratcliffe wrote:
So could people confirm that when they see crashes they are not installing via mapsource, and what GPS device they are using?
Yes, I'm not installing via mapsource, but copy the gmapsupp.img file directly to the device. It's a GPSmap 62s. I can try the 60CSx tonight, too, haven't done yet.
The 60CSx does not crash, only the 62s. But while it finds all Citys, it doesn't find any address or street. Looks like instead of crashing it ignores the data completly. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
On 02.03.2011 21:29, Thorsten Kukuk wrote:
On Wed, Mar 02, Thorsten Kukuk wrote:
On Wed, Mar 02, Steve Ratcliffe wrote:
So could people confirm that when they see crashes they are not installing via mapsource, and what GPS device they are using? Yes, I'm not installing via mapsource, but copy the gmapsupp.img file directly to the device. It's a GPSmap 62s. I can try the 60CSx tonight, too, haven't done yet. The 60CSx does not crash, only the 62s. But while it finds all Citys, it doesn't find any address or street. Looks like instead of crashing it ignores the data completly. Well that is 100% expected behaviour. Address search only works when sending with Mapsource. Thorsten
Hi, On Wed, Mar 02, Thorsten Kukuk wrote:
On Wed, Mar 02, Steve Ratcliffe wrote:
There have now been a few reports of problems searching on some devices with the latest version of mkgmap.
It seems that it occurs when a gmapsupp.img is created directly by mkgmap and sent to the device. In other words the index itself has nothing to do with the problem, if this is correct.
I see this with --index and without --index. So yes, it looks like the index itself has nothing to do with the problem. Going back to mkgmap-r1866 solved the problem for both cases for me.
If this helps: with mkgmap-r1863 from the index branch the 62s is already crashing. Is there any special version I should test to help to find out, when this problem was introduced? Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
Hi
I see this with --index and without --index. So yes, it looks like the index itself has nothing to do with the problem. Going back to mkgmap-r1866 solved the problem for both cases for me.
If this helps: with mkgmap-r1863 from the index branch the 62s is already crashing.
OK, that is fairly close to the current version in areas that I expect might make a difference so I'm not too surprised. Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar Sorry, this is going to be a difficult one to solve as nothing unusual happens on my Legend. Thanks,
On Fri, Mar 04, Steve Ratcliffe wrote:
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
Build is running.
Sorry, this is going to be a difficult one to solve as nothing unusual happens on my Legend.
No problem, I can help bisecting this if time permits. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
On Fri, Mar 04, Thorsten Kukuk wrote:
On Fri, Mar 04, Steve Ratcliffe wrote:
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
Build is running.
Ok: - No Crash - City-Search is working fine - Address-Search in the limited range is working as before What's not working: The TYP file is ignored :(. gmt shows it is there and everything is correct, but still it is not used. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
Hi
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
Build is running.
Ok:
- No Crash - City-Search is working fine - Address-Search in the limited range is working as before
What's not working: The TYP file is ignored :(. gmt shows it is there and everything is correct, but still it is not used.
Thanks. By the way that was actually 1852 not 1825 If you would be so good to try out 1853 that would be helpful (it is particular suspicion I have - if its not that then I will go back to bisecting properly :) http://files.mkgmap.org.uk/download/10/mkgmap-index-1853.jar Thanks ..Steve
On Fri, Mar 04, Steve Ratcliffe wrote:
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
Build is running.
Ok:
- No Crash - City-Search is working fine - Address-Search in the limited range is working as before
What's not working: The TYP file is ignored :(. gmt shows it is there and everything is correct, but still it is not used.
Thanks.
By the way that was actually 1852 not 1825
If you would be so good to try out 1853 that would be helpful (it is particular suspicion I have - if its not that then I will go back to bisecting properly :)
Sorry, took a little bit longer since I did a retest with 1852 first, since the TYP file problem didn't looked correct. Now that is working again. Now I have: 1852: everything works fine, no crash, city search works correct, address search in the known limited range 1853: Searching for a special city either leads immeaditly to a crash, or no city at all is displayed/found. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
Thorsten Kukuk <kukuk@suse.de> wrote:
On Fri, Mar 04, Steve Ratcliffe wrote:
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
Build is running.
Ok:
- No Crash - City-Search is working fine - Address-Search in the limited range is working as before
What's not working: The TYP file is ignored :(. gmt shows it is there and everything is correct, but still it is not used.
Thanks.
By the way that was actually 1852 not 1825
If you would be so good to try out 1853 that would be helpful (it is particular suspicion I have - if its not that then I will go back to bisecting properly :)
Sorry, took a little bit longer since I did a retest with 1852 first, since the TYP file problem didn't looked correct. Now that is working again.
Now I have:
1852: everything works fine, no crash, city search works correct, address search in the known limited range 1853: Searching for a special city either leads immeaditly to a crash, or no city at all is displayed/found.
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi That's great. It's a very small change so clear what the problem is. As for what to do about it is a different matter since that change is essential in some circumstances. Anyway - progress. Thanks Steve
Hi So the change that breaks it places two numbers that are associated with the SRT and/or index file. On thinking about it for a bit it is easy enough to add the SRT file into the gmapsupp and maybe that is all that is needed. Attached is a patch against trunk to add it to the gmapsupp.img file and a pre-built mkgmap at http://files.mkgmap.org.uk/download/11/mkgmap.jar ..Steve
On 05/03/11 16:28, Steve Ratcliffe wrote:
Hi
So the change that breaks it places two numbers that are associated with the SRT and/or index file.
On thinking about it for a bit it is easy enough to add the SRT file into the gmapsupp and maybe that is all that is needed.
Attached is a patch against trunk to add it to the gmapsupp.img file and a pre-built mkgmap at http://files.mkgmap.org.uk/download/11/mkgmap.jar
..Steve
City and address search now seem to work as before i.e. no crashes and sensible results Cheers Paul
On Sat, Mar 05, Steve Ratcliffe wrote:
Hi
So the change that breaks it places two numbers that are associated with the SRT and/or index file.
On thinking about it for a bit it is easy enough to add the SRT file into the gmapsupp and maybe that is all that is needed.
Attached is a patch against trunk to add it to the gmapsupp.img file and a pre-built mkgmap at http://files.mkgmap.org.uk/download/11/mkgmap.jar
It's working fine or me, no crashes, citys are all available. Thanks for the work! Now I only need to find out why with random map builds the TYP file will not be used by the GARMIN device, while it is there :( That's something I only saw until now after the merge with the index branch and with some of the index branch build tests yesterday. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
Thorsten Kukuk (kukuk@suse.de) wrote:
On Sat, Mar 05, Steve Ratcliffe wrote:
Hi
So the change that breaks it places two numbers that are associated with the SRT and/or index file.
On thinking about it for a bit it is easy enough to add the SRT file into the gmapsupp and maybe that is all that is needed.
Attached is a patch against trunk to add it to the gmapsupp.img file and a pre-built mkgmap at http://files.mkgmap.org.uk/download/11/mkgmap.jar
It's working fine or me, no crashes, citys are all available. Thanks for the work!
Now I only need to find out why with random map builds the TYP file will not be used by the GARMIN device, while it is there :(
That's something I only saw until now after the merge with the index branch and with some of the index branch build tests yesterday.
Thorsten
I know it's obvious, and may not be the cause of your problem, but in my case *every* time the TYP has failed to be associated with the gmapsupp.img is because either I had failed to put the TYP where it should have been, or because it was open in another programme locked for access, or because it had the wrong family ID. Just a thought. -- Charlie
On Sun, Mar 06, charlie@cferrero.net wrote:
Thorsten Kukuk (kukuk@suse.de) wrote:
Now I only need to find out why with random map builds the TYP file will not be used by the GARMIN device, while it is there :(
That's something I only saw until now after the merge with the index branch and with some of the index branch build tests yesterday.
Thorsten
I know it's obvious, and may not be the cause of your problem, but in my case *every* time the TYP has failed to be associated with the gmapsupp.img is because either I had failed to put the TYP where it should have been, or because it was open in another programme locked for access, or because it had the wrong family ID. Just a thought.
I ruled that already out. My script checks that this all is ok, and re-running the script again without modifying something creates a working map. The next time I see this I will diff the resulting map (by the way, do we store the date or anything else, which changes from build to build in the map?) and verify, that this is not again one of the caching problems of the 62s which bit me already more than once. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
On 04/03/11 19:02, Steve Ratcliffe wrote:
Hi
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
Build is running.
Ok:
- No Crash - City-Search is working fine - Address-Search in the limited range is working as before
What's not working: The TYP file is ignored :(. gmt shows it is there and everything is correct, but still it is not used.
Thanks.
By the way that was actually 1852 not 1825
If you would be so good to try out 1853 that would be helpful (it is particular suspicion I have - if its not that then I will go back to bisecting properly :)
http://files.mkgmap.org.uk/download/10/mkgmap-index-1853.jar
Thanks
..Steve
Your suspicion would seem to be correct. With index-1853 city search crashes my 605 and the address search returns no results Cheers Paul
Hi, can you build a small map and you provide this map for download. I could/would like to test this map on my oregon. Cheers Martin Am 04.03.2011 um 18:45 schrieb Steve Ratcliffe <steve@parabola.me.uk>:
Hi
I see this with --index and without --index. So yes, it looks like the index itself has nothing to do with the problem. Going back to mkgmap-r1866 solved the problem for both cases for me.
If this helps: with mkgmap-r1863 from the index branch the 62s is already crashing.
OK, that is fairly close to the current version in areas that I expect might make a difference so I'm not too surprised.
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
Sorry, this is going to be a difficult one to solve as nothing unusual happens on my Legend.
Thanks, _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
OK, that is fairly close to the current version in areas that I expect might make a difference so I'm not too surprised.
Knowing if 1825 breaks might be a good clue, I've built a version at: http://files.mkgmap.org.uk/download/9/mkgmap-index-r1825.jar
This seems to work ok for me. No crashes with city search and address search produces sensible results as normal Cheers Paull
So could people confirm that when they see crashes they are not installing via mapsource, and what GPS device they are using?
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I copy and paste the gmapsupp.img direct on to my Edge 605. I have never used Mapsource or the basemap on my 605 Cheers Paul
1. If you have this error, please also check if link-pois-to-ways switch was used. According to a post here: http://forum.openstreetmap.org/viewtopic.php?pid=146242#p146242 the address search breaks down on Oregon once --link-pois-to-ways is used. 2. Check that the mgkmap version you are using to compile the maps, is the same or newer than the one that was used to create the maps. If you create the index with an older version than 1871 (also if it is from the index branch) against maps created with rev 1871, then Mapsource crashes on selecting maps. Hence very probable that if you create gmapsupp with mkgmap but the mkgmap version is older than the one used to build the maps, the GPS will choke too in some way or another. On 02.03.2011 13:37, Steve Ratcliffe wrote:
Hi
There have now been a few reports of problems searching on some devices with the latest version of mkgmap.
It seems that it occurs when a gmapsupp.img is created directly by mkgmap and sent to the device. In other words the index itself has nothing to do with the problem, if this is correct.
This is probably good news since there are not too many changes to stuff outside of the index itself.
So could people confirm that when they see crashes they are not installing via mapsource, and what GPS device they are using?
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Wed, Mar 02, Felix Hartmann wrote:
1. If you have this error, please also check if link-pois-to-ways switch was used. According to a post here: http://forum.openstreetmap.org/viewtopic.php?pid=146242#p146242 the address search breaks down on Oregon once --link-pois-to-ways is used.
It's used, rebuilding my map currently without that option and with mkgmap 1875
2. Check that the mgkmap version you are using to compile the maps, is the same or newer than the one that was used to create the maps.
I always rebuild everything with the same mkgmap version. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
On Wed, Mar 02, Felix Hartmann wrote:
1. If you have this error, please also check if link-pois-to-ways switch was used. According to a post here: http://forum.openstreetmap.org/viewtopic.php?pid=146242#p146242 the address search breaks down on Oregon once --link-pois-to-ways is used.
Removing --link-pois-to-ways doesn't make a difference. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
On 03/02/2011 01:37 PM, Steve Ratcliffe wrote:
This is probably good news since there are not too many changes to stuff outside of the index itself.
So could people confirm that when they see crashes they are not installing via mapsource, and what GPS device they are using?
My eTrex Legen HCx crashes under these circumstances: I have made 133 OSM map tiles and 82 SRTM tiles, built with r1733. If I combine the southern 58 OSM + 58 SRTM into a gmapsupp.img with mkgmap (no Mapsource involved) it doesn't crash. If I combine the northern 84 + 17 SRTM it doen't crash. But if I combine all 133 OSM + 82 SRTM tiles it crashes when doing a "Search for city". The big map is 2.3 GB, if that might matter. Yes, 58 + 84 is more than 133, there is an overlap ;-)
participants (7)
-
charlie＠cferrero.net -
Felix Hartmann -
Martin -
Paul -
Ralf Kleineisel -
Steve Ratcliffe -
Thorsten Kukuk