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

[Salvador Cuñat]

Good night Jef.

On Tue, Mar 07, 2017 at 03:30:14PM +0100, Jef Driesen wrote:
> On 2017-03-03 14:08, Salvador Cuñat wrote:
> > On Fri, Mar 03, 2017 at 10:50:23AM +0100, Salvador Cuñat wrote:
> > > El 03/03/2017 09:53, "Anton Lundin" <glance at acc.umu.se> escribió:
> > > >
> > > > I guess its easiest just to modify the libdivecomputer call to dump the
> > > > profile data to a file. That way smtk2ssrf can generate the raw dive
> > > > dumps that Jef is looking for.
> > > >
> > > Probably. There shouldn't be any problem. Will try to dump 2/3
> > > affected
> > > dives, with headers and without them.
> > 
> > Attached some files. Those named "complete" includes profile and a
> > faked header (as datatrak logs imported into smarttrak lack of their
> > own).
> 
> 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).

Regards.

Salva.