testing smtk2ssrf_4.6.2-33-g14971e912875_x86_64-20170224.AppImage

[Jef Driesen]

On 2017-03-08 23:58, Salvador Cuñat wrote:
> On Tue, Mar 07, 2017 at 03:30:14PM +0100, Jef Driesen wrote:
>> At first sight, it looks like the profile is truncated. (I can't 
>> really
>> confirm that, because I don't know how long the dive should be.) The 
>> last
>> sample isn't complete. The size check for the extra decompression byte
>> fails.
>> 
>> I wonder if this happens only for export from the smarttrak, or also 
>> for
>> dives downloaded directly from the dive computer. Any chance you can 
>> get me
>> a memory dump from the same dive computer?
>> 
> I don't think Alessandro has this DCs yet.
> Do you Alessandro ?
> 
> I've only seen this while importing from smarttrak. Weirdly not all
> dives are affected, just some of them.
> In my opinion the dive has just lost its last byte (may be one byte
> and a last sample).

It's difficult to tell what is going on without knowing how many bytes 
there should be. And the only way to know is to compare with the data 
downloaded from the dive computer. That's why I asked.

If Alessandro no longer has the dive computer, or those dives are long 
gone, then it will be difficult to find out. This could for example be a 
bug in an old version of smarttrak. So even if we could verify that the 
current version doesn't drop any bytes, then that's no guarantee for 
previous versions.

Jef