[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Showstopper? most KDE apps crash on exit
From:       "F () lk Brettschneider" <gigafalk () yahoo ! com>
Date:       2002-03-20 14:39:49
[Download RAW message or body]

Lubos Lunak wrote:

>
>  No, most probably not. #0 - #5 are the signal handling (KCrash etc.) after
> the crash. The crash is #6 , somewhere in the application, but it's not
> possible to say where because '??' doesn't say much. #7 - #11 are from
> kdeinit and glibc.
>  But this backtrace looks like post-mortem one from drkonqi. Instead attach
> gdb to the process while it's still running and _after_ that make it crash.
> Gdb should stop and show you exactly the place where it crashed (unless this
> is one of those really ugly crashes).

Aha. Thanks. Oh...it seems it is due the active Keramik style... hm....then it
isn't relevant, right? Because Keramik isn't part of the release.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 4125)]
__tcf_3 () at
/home/falk/Projekte/kde3src/kdelibs/kstyles/keramik/pixmaploader.cpp:222
222             static QCString c = "lcr", r = "tcb";
(gdb) bt
#0  __tcf_3 () at
/home/falk/Projekte/kde3src/kdelibs/kstyles/keramik/pixmaploader.cpp:222
#1  0x413bd2f5 in exit () from /lib/libc.so.6
#2  0x413aabb5 in __libc_start_main () from /lib/libc.so.6
(gdb)


>
>
> --
>  Lubos Lunak
>  llunak@suse.cz ; l.lunak@kde.org
>  http://dforce.sh.cvut.cz/~seli

Thanks anyway.

Cheers
F@lk




_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[prev in list] [next in list] [prev in thread] [next in thread]