Totally odd kde vs print problem

Goffioul Michael goffioul at imec.be
Tue Jun 29 09:56:37 CEST 2004


> >[General]
> >PrintSystem=lpr
> >
> I did the edit after restoreing those two files to the 
> ~/kde3.2.3/config dir, and got this for the backtrace:

Note that using "lpr" as print system should avoid to use the CUPS
library, hence the problem should not appear.

> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1094566432 (LWP 5466)]
> 0x407c8317 in fREe () from /root/kde3.2.3/lib/libkdecore.so.4
> (gdb) bt
> #0  0x407c8317 in fREe () from /root/kde3.2.3/lib/libkdecore.so.4
> #1  0x407c7725 in free () from /root/kde3.2.3/lib/libkdecore.so.4
> #2  0x41b1de3e in httpClose () from /usr/lib/libcups.so.2
> #3  0x41adc153 in IppRequest::doFileRequest(QString const&, QString 
> const&) ()

That's really baaaaaad. Basically, it looks like the problem is
out of my control, because it appears in the reimplementation of
the memory allocation routines in the core of KDE. Is it possible
for you to compile CUPS and kdelibs/kdecore/ with debug enable,
and produce the same backtrace?

Michael.



More information about the kde-print mailing list