On 2016-05-30 00:47, Otto Moerbeek wrote:
On Sun, May 29, 2016 at 06:48:53PM +0200, Tinker wrote:
On 2016-05-29 18:24, Otto Moerbeek wrote:
> Hi,
>
> running analog on current sparc64 gives more coredumps coming from
> libpng (via gd). At the moment I do not have time to investigate this,
> so if anyone wants to give it a shot, I'd really appreciate it,
>
> #0 0x0000000f68e018c0 in ?? () from /usr/local/lib/libpng.so.17.2
> #1 0x0000000f688f4fa4 in png_create_write_struct ()
> from /usr/local/lib/libpng.so.17.2
> #2 0x0000000ffc0c1ab0 in gdImagePngCtxEx () from
> /usr/local/lib/libgd.so.21.1
> #3 0x0000000ffc0c2784 in gdImagePng () from
> /usr/local/lib/libgd.so.21.1
> #4 0x0000000d4a44c270 in piechart_write () from /usr/local/bin/analog
> #5 0x0000000d4a44dfa0 in piechart () from /usr/local/bin/analog
> #6 0x0000000d4a4413d0 in genrep () from /usr/local/bin/analog
> #7 0x0000000d4a44450c in output () from /usr/local/bin/analog
> #8 0x0000000d4a426688 in main () from /usr/local/bin/analog
>
> -Otto
Otto,
Does this mean that what you have encountered is the realization that
libpng
is actually *BROKEN* on sparc64 currently?
(Or maybe gd, we don't know;) How frequent are the crashes?
Thanks!
Tinker
It's 100% reproducable.
-Otto
Ouch. Ok so libpng (maybe also libgd) is broken currently on sparc64.
Did it ever work in the past for you?
