John Bowler

Nope: no bug that I can see. pngfix, pngcp both handle the files correctly (they error out before they even attempt to call zlib). libpng_read_fuzzer actually manages to read a...

So the printout shows that the pointer values are correct, except that the first of this pair of lines in your code is clearly wrong: ``` printf("b = *(%p)\n", prev_row...

@ctruta; I put a review on https://github.com/libpng/libpng/pull/3 Summary is that there is some work to be done but the code apparently only works with __linux__ and probably doesn't work on...

There is no memory leak here, the program has exited with a fatal error (and this is the correct behavior). I.e. pngfix is behaving as designed; it exits with an...

There is no memory leak here, the program has exited with a fatal error (and this is the correct behavior).

There is no memory leak here, the program has exited with a fatal error (and this is the correct behavior).

Either disable the hardware options completely or don't try to build libpng yourself - rely on the Apple provided functionality.

> > Is there any known workarounds? > > My initial bug report literally contains a workaround. This is a possible xv-backdoor response. @seanm responded within a few minutes of...

My apologies @seanm , that was brusque and inappropriate particularly as I did exactly the same thing myself. Cross compilation is not environment specific and not architecture specific; it needs...

This seems to be a duplicate of #264, albeit a lot better bug report since it seems to correctly explain the problem.