Xprint segfault: init function missing
Drew Parsons
dparsons at debian.org
Fri Dec 23 06:19:06 PST 2005
Last month I described an error running an Xprt binary
(http://lists.x.org/archives/xorg-modular/2005-November/000800.html)
After patching xorg/Xprint/ddxinit.c to invoke PrinterInitOutput(), the
error Xprt gave was:
Couldn't open RGB_DB '/opt/xorg-modular//share/X11/rgb'
Xp Extension: Can't load driver XP-POSTSCRIPT
init function missing
Segmentation fault
I'm not sure that the RGB_DB error is a problem since it wasn't occuring
in November's CVS. I've got a backtrace for the segfault, which I think
is related to the XP-POSTSCRIPT missing init function.
The backtrace is:
Program received signal SIGSEGV, Segmentation fault.
0x08056c75 in XpGetMaxWidthHeightRes (printer_name=0x8132468 "colourlw",
vpr=0x0, width=0xbf89380c, height=0xbf893808, resolution=0xbf893804)
at mediaSizes.c:705
705 pool_msss = XpOidMediumSSNew(value,
(gdb) bt
#0 0x08056c75 in XpGetMaxWidthHeightRes (
printer_name=0x8132468 "colourlw", vpr=0x0, width=0xbf89380c,
height=0xbf893808, resolution=0xbf893804) at mediaSizes.c:705
#1 0x08054fb0 in InitPrintDrivers (index=0, pScreen=0x813f1c8, argc=10,
argv=0xbf893a44) at Init.c:1687
#2 0x08074936 in AddScreen (pfnInit=0x8054f10 <InitPrintDrivers>,
argc=10,
argv=0xbf893a44) at main.c:781
#3 0x08056102 in PrinterInitOutput (pScreenInfo=0x812d280, argc=10,
argv=0xbf893a44) at Init.c:1530
#4 0x08073de6 in main (argc=10, argv=0xbf893a44, envp=0xbf893a70)
at main.c:372
(colourlw is the name of the first printer detected by Xprint from CUPS)
I don't think this is happening due to my ddxinit.c patch, since
PrinterInitOutput() here is invoked from Init.c, not from InitOutput()
in ddxinit.c.
All clues welcome.
Drew
More information about the xorg-modular
mailing list