Re: Segfault using apache / php4-gd / libpng
On Fri, Aug 30, 2002 at 11:05:05PM +1200, Mark Robinson wrote:
> Sadly however a fresh problem has emerged :
>
> [Fri Aug 30 22:39:30 2002] [notice] Apache/1.3.26 (Unix) Debian GNU/Linux configured -- resuming normal operations
> [Fri Aug 30 22:39:30 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache/suexec)
> [Fri Aug 30 22:39:30 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
> libpng warning: Application was compiled with png.h from libpng-1.2.1
> libpng warning: Application is running with png.c from libpng-1.0.12
> gd-png: fatal libpng error: Incompatible libpng version in application and library
> [Fri Aug 30 22:40:21 2002] [notice] child pid 27970 exit signal Segmentation fault (11)
> libpng warning: Application was compiled with png.h from libpng-1.2.1
> libpng warning: Application is running with png.c from libpng-1.0.12
> gd-png: fatal libpng error: Incompatible libpng version in application and library
> [Fri Aug 30 22:40:22 2002] [notice] child pid 28030 exit signal Segmentation fault (11)
>
> I don't know which package to report this against, and so I toss it into the fire here.
I've seen this in recent evolution packages as well. In that example,
the package expected to use libpng2, but was actually compiled against
libpng3. The upshot of which is that you need to file a bug against the
package at fault and ask them to re-compile against libpng2.
--Matthew
Reply to: