On Mon, Feb 11, 2013 at 09:48:39PM +0100, Matthias Kilian wrote:
> And now to the real fun stuff: you don't need any input at all ;-)
>
> gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -dNOMEDIAATTRS
> -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -I/usr/share/cups/fonts
> -c -f -_
>
> is enough to get the segfault (and I get a backtrace very similar
> to what you wrote).
While getting bleeding eyes reading ghostscript code and getting
closer to the problem, I'm really curious why it doesn't happen on
amd64 and wether it only happens on 32bit archs.
So if anyone could try the above commant on any arch other than
i386 and amd64 and report back wether it segfaults with a backtrace
similar to the one below, I'd be very happy:
#0 0x01467844 in gsicc_set_device_profile (pdev=0x84fec034, mem=0x863a2200,
file_name=0x2132d2c6 "default_gray.icc", pro_enum=gsDEFAULTPROFILE) at
./base/gsicc_manage.c:1134
#1 0x016270b2 in cups_set_color_info (pdev=0x84fec034) at cups/gdevcups.c:4237
#2 0x01624829 in cups_put_params (pdev=0x84fec034, plist=0xcfbbc34c) at
cups/gdevcups.c:3213
#3 0x0163def4 in gs_putdeviceparams (dev=0x84fec034, plist=0xcfbbc34c) at
./base/gsdparam.c:479
#4 0x013eceec in zputdeviceparams (i_ctx_p=0x842632c0) at ./psi/zdevice.c:407
FWIW, wether ghostscript-9.05 on 5.2 or ghostscript-9.06 on current
doesn't matter.
Ciao,
Kili
