Re: [hatari-devel] ASAN issues with tests

[Nicolas Pomarède <npomarede@xxxxxxxxxxxx>]

Le 29/07/2022 à 20:20, Nicolas Pomarède a écrit :
> Le 29/07/2022 à 20:18, Eero Tamminen a écrit :
> > Hi,
> >
> > On 29.7.2022 17.20, Nicolas Pomarède wrote:
> > > but tests are still failing for me (many more than in your cases). 
> > > They all report this :
> > >
> > > Direct leak of 920 byte(s) in 5 object(s) allocated from:
> > >      #0 0x7f562d0b8757 in calloc (/lib64/libasan.so.8+0xb8757)
> > >      #1 0x7f562bacb4df 
> > > (/home/npomarede/src/hatari.git/src/hatari+0x78984df)
> > ...
> > > Indirect leak of 24 byte(s) in 1 object(s) allocated from:
> > >      #0 0x7f562d0b8d6f in __interceptor_malloc 
> > > (/lib64/libasan.so.8+0xb8d6f)
> > >      #1 0x7f562baddae5 
> > > (/home/npomarede/src/hatari.git/src/hatari+0x78aaae5)
> > >
> > > unfortunately, there's no indication of what part of th code it is.
> >
> > Maybe your ASAN version is configured differently from mine, and does 
> > not report leak backtraces by default?
> >
> > ASAN has huge amount of options, which can be set in its env var, and 
> > which you can see with:
> >      ASAN_OPTIONS=help=1 src/hatari
> >
> > You could try something like:
> > ASAN_OPTIONS=malloc_context_size=8:detect_leaks=1:leak_check_at_exit=1
>
> it did report the context for other error (png, load configuration) but 
> not theses ones ; I will try later your options.

Even with these options, the context / position in sources files is 
still not shown.
So I get some leaks, but I can't tell where they come from.

Nicolas