After installing kdemultimedia-dbg I could use a running kmix instance to get more information from the files posted here. To do so, I compared the maps attached here with that of the running process in order to relocate the addresses mentioned in the backtrace to the corresponding addresses in the running process. Using the list command in gdb I could get function name and source file information about these addresses. As the addresses represent return addresses from the call stack, they seem to correspond to the command immediately after the one currently executing.
With this information I could get more details for two important stack frames: #12 0xb7a1057a in ?? () from /usr/lib/libsolid.so.4 Solid::DeviceManagerPrivate::_k_deviceAdded(QString const&) (kde4libs-4.1.2/solid/solid/devicemanager.cpp:165) #13 0xb7a1087f in ?? () from /usr/lib/libsolid.so.4 Solid::DeviceManagerPrivate::qt_metacall(QMetaObject::Call, int, void**) (kde4libs-4.1.2/obj-i486-linux-gnu/solid/solid/devicemanager_p.moc:76) So what happens is that the first assertion in _k_deviceAdded failed, which reads Q_ASSERT(dev->backendObject()==0); See http://websvn.kde.org/tags/KDE/4.1.2/kdelibs/solid/solid/devicemanager.cpp?view=markup >From there on things get a bit tricky to debug, as I don't have the moc files generated here, only the sources unpacked, and as I can't get deeper in the stack, because debugging qt4 is impossible due to bug 261380. On the other hand, "_k_deviceAdded SIGABRT" give pretty good keywords for a web search, which yielded http://bugs.kde.org/show_bug.cgi?id=171499 about kmix, which got duped to http://bugs.kde.org/show_bug.cgi?id=160221 about solid in general, affecting other apps as well. -- kmix crashes with SIGABRT https://bugs.launchpad.net/bugs/293126 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
