Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

seg fault while opening maps #17

Open
GoogleCodeExporter opened this issue Jul 1, 2015 · 2 comments
Open

seg fault while opening maps #17

GoogleCodeExporter opened this issue Jul 1, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Setting OZEX_LAT and OZEX_LON inside the area covered by a map
causes ozex to crash at startup with segmentation fault. If OZEX_LAT and 
OZEX_LON points to outside the area coverded by map - ozex start OK, of course 
no map image is displayed.
2. Test done without gps device, OZEX_USE_LOG set to 0
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
Ubuntu both 32 and 64 bit

Please provide any additional information below.

First thought that it depends on Map Datum - I had o lot of maps in Pulkovo 
1942, but further test with maps in different datums gave same effect.

Szubi

Original issue reported on code.google.com by gimbus...@gmail.com on 6 Feb 2011 at 9:57

@GoogleCodeExporter
Copy link
Author

Forgotten to say - OS is Ubuntu 10 current - all updates installed (on both 32 
bit and 64 bit)

Original comment by gimbus...@gmail.com on 6 Feb 2011 at 10:10

@GoogleCodeExporter
Copy link
Author

After some more tests: it depends on ozf2 file, sometimes ozex (and swampex) 
crashes with segmentation fault, sometimes it opens the map. It seems like some 
ozf2 files do not follow the specification (or the specification is not 100% 
correct). 

Original comment by gimbus...@gmail.com on 9 Feb 2011 at 5:45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant