Fwd: kprinter crashes with KDE 3.1.1 + woody

Stephan Johach lucardus at onlinehome.de
Wed Mar 26 16:20:41 GMT 2003

Am Mittwoch, 26. März 2003 14:39 schrieb Thiago Macieira:
> >Am Montag, 24. März 2003 16:03 schrieb George Staikos:
> >> Try this patch to see if it helps.  In any case it means that your
> >> printer in not available.
> >
> >Doesn't help. I'm recompiling kdebase with debuginfo and post a
> >backtrace if I get one ...
> Please try the patches provided in
> http://bugs.kde.org/show_bug.cgi?id=56424 before reporting errors. I
> believe to have fixed the problem. If you do find them, though, post your
> errors there.

I don't understand. What patches? The report talks about 

"automatic reload configurable for distinct adresses (wishlist) "

there are no patches.

> One other thing: kdelibs with debuginfo would be much more appreciated;
> kdebase doesn't impact here.

Sorry. I meant I already had kdelibs with full debug info and now recompiling
kdebase to get a full trace ...

Ok, here is the kdelibs backtrace without kdebase info.

[New Thread 1024 (LWP 346)]
0x410380e9 in __wait4 () at __wait4:-1
	in __wait4
#0  0x410380e9 in __wait4 () at __wait4:-1
#1  0x410b2b74 in __DTOR_END__ () from /lib/libc.so.6
#2  0x40ea1a83 in waitpid () from /lib/libpthread.so.0
#3  0x4064dc88 in KCrash::defaultCrashHandler(int) (sig=138101200)
    at ../../kdelibs/kdecore/kcrash.cpp:235
#4  <signal handler called>
#5  KExtendedSocketLookup::freeresults(kde_addrinfo*) (res=0x0)
    at ../../kdelibs/kdecore/kextsock.cpp:382
#6  0xbfffd6c4 in ?? ()



More information about the kde-core-devel mailing list