The consistent trigger appears to be closing a dive file. My guess is that some 
destructor gets called twice or that in some other way we access freed memory.

I tried to figure this out by starting at valgrind output on Linux, but so far 
I haven't managed to figure it out...

Help with this one would be very welcome.

/D
-- 
from my phone
_______________________________________________
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to