search for: printhexarray

...ng with same stack trace over and over again (piping the output to file a results in a file that is 259 MiB). I've attached the compressed log. Hopefully this will be a useful starting point in determining the issue. At a glance it looks like we are derefencing a nullptr somewhere in ``fuzzer::PrintHexArray()`` which ASan then catches but then the handler for the ASan detected nullptr derefence calls ``fuzzer::PrintHexArray()`` again and so we get stuck in a loop. Some how we are managing to break out of this loop but I'm guessing this probably racey which would probably also explain the very vari...

...and over again (piping the output > to file a results in a file that is 259 MiB). I've attached the > compressed log. > > Hopefully this will be a useful starting point in determining the > issue. At a glance it looks like we are derefencing a nullptr > somewhere in ``fuzzer::PrintHexArray()`` which ASan then catches but > then the handler for the ASan detected nullptr derefence calls > ``fuzzer::PrintHexArray()`` again and so we get stuck in a loop. Some > how we are managing to break out of this loop but I'm guessing this > probably racey which would probably also e...

...the output >> to file a results in a file that is 259 MiB). I've attached the >> compressed log. >> >> Hopefully this will be a useful starting point in determining the >> issue. At a glance it looks like we are derefencing a nullptr >> somewhere in ``fuzzer::PrintHexArray()`` which ASan then catches but >> then the handler for the ASan detected nullptr derefence calls >> ``fuzzer::PrintHexArray()`` again and so we get stuck in a loop. Some >> how we are managing to break out of this loop but I'm guessing this >> probably racey which would...