This problem started cropping up after we added the parallel processing option. The lack of error information is also because of the use of a try command - which avoids the messes that crop up from time to time (for a lot of different reasons). The work around for now is -debug T. That will give you far more information about where and when gnssir is crashing. This will be available as of version 3.6.6
This problem started cropping up after we added the parallel processing option. The lack of error information is also because of the use of a try command - which avoids the messes that crop up from time to time (for a lot of different reasons). The work around for now is -debug T. That will give you far more information about where and when gnssir is crashing. This will be available as of version 3.6.6