Jef Driesen 39aad6bb52 Report an error for invalid ringbuffer pointers
Previously, invalid ringbuffer pointers were always handled during the
second pass. But that changed after the previous commit. If the invalid
pointer is located in the first logbook entry, this is now handled as
"no dives present". Fixed by returning the correct error code instead.
2020-02-24 09:21:33 +01:00
..
2019-06-21 16:13:27 +02:00
2019-06-21 16:13:27 +02:00
2018-12-05 10:21:09 +01:00
2018-12-17 16:44:48 +01:00
2012-06-21 21:39:24 +02:00
2018-12-06 08:34:29 +01:00
2017-08-18 23:26:45 +02:00
2017-08-18 23:26:45 +02:00
2020-02-04 08:41:55 +01:00
2020-01-06 13:44:07 +01:00
2019-11-21 11:07:07 +01:00
2014-03-14 09:44:10 +01:00
2013-08-22 09:15:55 +02:00
2018-01-30 22:00:41 +01:00
2017-08-18 23:26:45 +02:00
2020-01-06 13:44:07 +01:00
2019-11-21 11:07:07 +01:00
2018-02-04 21:21:42 +01:00
2014-03-19 09:16:07 +01:00
2014-03-19 09:16:07 +01:00
2019-04-13 11:37:15 +02:00
2017-08-18 23:26:45 +02:00
2018-06-22 23:21:51 +02:00
2018-03-05 08:44:14 +01:00