> On Mar 30, 2021, at 10:35 AM, Thiago Macieira via subsurface
> wrote:
>> I wonder why I didn't find this with Valgrind. Given that my professional
>> software developer career started writing a memory debugger 27 years ago...
>> I find Valgrind frustratingly inconsistent to use.
Hmm. A
On Tuesday, 30 March 2021 08:30:31 PDT Dirk Hohndel via subsurface wrote:
> I wonder why I didn't find this with Valgrind. Given that my professional
> software developer career started writing a memory debugger 27 years ago...
> I find Valgrind frustratingly inconsistent to use.
>
> /D
Try ASan
> On Mar 30, 2021, at 12:26 AM, Berthold Stoeger
> wrote:
>
> On Dienstag, 30. März 2021 05:32:37 CEST Dirk Hohndel via subsurface wrote:
>> 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
On Dienstag, 30. März 2021 05:32:37 CEST Dirk Hohndel via subsurface wrote:
> 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
