Bug 148431 - Crashed and cause signal 11 SIGSEGV
Summary: Crashed and cause signal 11 SIGSEGV
Status: RESOLVED NOT A BUG
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-01 20:17 UTC by Luiz Bruscato
Modified: 2007-08-02 22:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luiz Bruscato 2007-08-01 20:17:45 UTC
Version:           v0.8.5 (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
OS:                Linux

After the update on qt3 3.3.7-16 kget starts but after a while spawns a Crash
Here is the output of the KDE Crash handler

System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib64/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)
[Thread debugging using libthread_db enabled]
[New Thread 47077418950688 (LWP 15131)]
(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)
[KCrash handler]
#5  0x000000000043a758 in QWidget::setUpdatesEnabled ()
#6  0x00000000004413fa in QWidget::setUpdatesEnabled ()
#7  0x00002ad10c213adc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#8  0x00002ad10c2147b3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#9  0x00002ad10c232e35 in QTimer::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#10 0x00002ad10c1bceb5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#11 0x00002ad10c1bdc40 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002ad10b9c5e38 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#13 0x00002ad10c1b350f in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#14 0x00002ad10c17369d in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#15 0x00002ad10c1d1963 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002ad10c1d1812 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00000000004203d1 in QWidget::setUpdatesEnabled ()
#18 0x00002ad10d054ae4 in __libc_start_main () from /lib64/libc.so.6
#19 0x000000000041b429 in QWidget::setUpdatesEnabled ()
#20 0x00007fffa008fbb8 in ?? ()
#21 0x0000000000000000 in ?? ()
Comment 1 Bram Schoenmakers 2007-08-01 20:34:48 UTC
Please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports in order to improve this bug report. There's not much we can do with this amount of information.
Comment 2 Luiz Bruscato 2007-08-02 17:21:24 UTC
Yes,
 I've reported the bug but unfortunately I don't have enough info for you to 
debug it (debug package installed). next time I will provide more info.
Thanks
On Wednesday 01 August 2007 15:34, Bram Schoenmakers wrote:
[bugs.kde.org quoted mail]
Comment 3 Bram Schoenmakers 2007-08-02 22:51:53 UTC
Then I'll close this ticket. Reopen whenever you find out more.