[kde-linux] kicker crash

artem artem at ininfo.com.ua
Wed Feb 22 08:19:12 UTC 2006


Bram Schoenmakers wrote:

>Op dinsdag 21 februari 2006 11:48, schreef artem:
>
>  
>
>>When my CPU load is 100% kicker always crash.
>>Can anybody tell me what is happening?
>>    
>>
>
>No. You didn't provide enough information. Can you produce a backtrace of the 
>crash?
>
>  
>
>>And the second question is: when 
>>I'm copying files from one place to another my CPU load is 100% (it's
>>seems strange on Duron 1200MGz)
>>    
>>
>
>That's normal behaviour.
>
>Kind regards,
>
>  
>
The point is that not always I can see a backtrace,it's crashing without 
any information, but sometimes it is window of crashing:

@@@@
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents 
creation of proper backtraces, or the stack frame was seriously 
corrupted in the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208743456 (LWP 2244)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbf958f88 in ?? ()
#2  0x00000000 in ?? ()


@@@
So how I can show you a real backtrace?



More information about the kde-linux mailing list