Hello,
>
> Yep, it seems valgrind outputs bunch of invalid reads and writes with
> this test.
Seems any test with valgrind generates invalid reads and writes... Probably
it depends on macros-usage: probably they are not properly handled by
valgrind
It just seems a bit strange to first calculate a
On 1/14/19 12:51 PM, Sergii Romantsov wrote:
Usage test 'depthstencil-render-miplevels 200 s=z24_s8' causes
core dump on exit.
Fixed: array of pointers is allocated to size max_miplevel, but
used as max_miplevel + 1.
Yep, it seems valgrind outputs bunch of invalid reads and writes with
this t