Looking for hints on DC import debugging

[Lutz Vieweg]

Hi,

since "just trying to find external conditions that trigger the import failure"
did not get me anywhere, I intend to attach with gdb next time and find the
place in the code where the decision is made to not use the data coming from the DC.

Can you hint me at which function I should start setting a break point?

Does subsurface process dive data while importing, one-dive-at-a-time, or
is there more like a place in the code where the whole of one DC import
(multiple dives) is passed back from libdivecomputer to the application?

Regards,

Lutz Vieweg


On 12/26/2013 04:08 PM, Lutz Vieweg wrote:
> The symptom is: The whole import process looks normal while
> it runs - the progress bar progresses, if one enables libdc
> logging those logs look completely normal, but once the progress
> has reached 100% and the import seems finished, there ist just
> not any single dive log entry added to the list!
> (I tested this starting with an empty dive log.)
>
> No error message or alike is emitted, there are just no dives imported.