[PC-BSD Testing] System Manager Crash when fetching ports

Kris Moore kris at pcbsd.com
Wed Aug 27 16:10:23 PDT 2008


Alex DiMarco wrote:
> Fetching ports collection, the app crashed with the following...
> 
> note - this was after resuming from an interrupted ports fetch...
> fetch ports - interrupt the fetch - reboot - refetch ports.
> 
> 
> Application: KDE Control Module (kcmshell4), signal SIGSEGV
> [New Thread 0x8102100 (LWP 100163)]
> [Switching to Thread 0x8102100 (LWP 100163)]
> [KCrash handler]
> #6  0x28c4cc29 in QLocalePrivate::numberToCLocale ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #7  0x28c4d2b6 in QLocalePrivate::stringToLongLong ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #8  0x28c604b5 in QString::toLongLong ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #9  0x28c605b3 in QString::toInt () from /usr/local/lib/qt4/libQtCore.so.4
> #10 0x2b4c6894 in PortsnapProgress::parseFetch ()
>    from /usr/local/kde4/lib/kde4/libkcm_pcbsdsystem.so.1.0.0
> #11 0x2b4c8c0a in PortsnapProgress::qt_metacall ()
>    from /usr/local/kde4/lib/kde4/libkcm_pcbsdsystem.so.1.0.0
> #12 0x28d099ec in QMetaObject::activate ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #13 0x28d09e22 in QMetaObject::activate ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #14 0x2b72e647 in Q3Process::readyReadStdout ()
>    from /usr/local/lib/qt4/libQt3Support.so.4
> #15 0x2b5c43f7 in Q3Process::socketRead ()
>    from /usr/local/lib/qt4/libQt3Support.so.4
> #16 0x2b72e783 in Q3Process::qt_metacall ()
>    from /usr/local/lib/qt4/libQt3Support.so.4
> #17 0x28d099ec in QMetaObject::activate ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #18 0x28d09e22 in QMetaObject::activate ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #19 0x28d42c93 in QSocketNotifier::activated ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #20 0x28d11c1f in QSocketNotifier::event ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #21 0x290c0afc in QApplicationPrivate::notify_helper ()
>    from /usr/local/lib/qt4/libQtGui.so.4
> #22 0x290c74be in QApplication::notify ()
>    from /usr/local/lib/qt4/libQtGui.so.4
> #23 0x28555ab3 in KApplication::notify (this=0xbfbfe730, receiver=0x8299300,
>     event=0xbfbfe420)
>     at /usr/ports/x11/kdelibs4/work/kdelibs-4.1.0/kdeui/kernel/kapplication.cpp:311
> #24 0x28cf9459 in QCoreApplication::notifyInternal ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #25 0x28d20363 in socketNotifierSourceDispatch ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #26 0x29bd5096 in g_main_context_dispatch ()
>    from /usr/local/lib/libglib-2.0.so.0
> #27 0x29bd8432 in g_main_context_check () from /usr/local/lib/libglib-2.0.so.0
> #28 0x29bd89b5 in g_main_context_iteration ()
>    from /usr/local/lib/libglib-2.0.so.0
> #29 0x28d204be in QEventDispatcherGlib::processEvents ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #30 0x29145475 in QGuiEventDispatcherGlib::processEvents ()
>    from /usr/local/lib/qt4/libQtGui.so.4
> #31 0x28cf85d3 in QEventLoop::processEvents ()
>    from /usr/local/lib/qt4/libQtCore.so.4
> #32 0x28cf8761 in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4
> #33 0x294b8647 in QDialog::exec () from /usr/local/lib/qt4/libQtGui.so.4
> #34 0x28085604 in kdemain (_argc=2, _argv=0xbfbfe934)
>     at /usr/ports/x11/kdebase4-runtime/work/kdebase-runtime-4.1.0/kcmshell/main.cpp:275
> #35 0x080487b2 in main (argc=1954788, argv=0x2807b600)
>     at /usr/ports/x11/kdebase4-runtime/work/kdebase-runtime-4.1.0/build/kcmshell/kcmshell4_dummy.cpp:3
> 
> 
> 

Thanks! I'll take a look into this here soon and see if I can duplicate 
/ fix it.


-- 

Kris Moore
PC-BSD Software
http://www.pcbsd.com


More information about the Testing mailing list