With the patch, now. (sorry) 2011/6/6 Guilhem Bonnefille <[email protected]>: > 2011/6/5 Radek Polak <[email protected]>: >> Guilhem Bonnefille wrote: >> >>> Here is the backtrace. >>> >>> Program received signal SIGSEGV, Segmentation fault. >>> 0x40a3c414 in QDBusAbstractInterface::isValid() const () from >>> /opt/qtmoko/lib/libQtDBus.so.4 >>> (gdb) where >>> #0 0x40a3c414 in QDBusAbstractInterface::isValid() const () from >>> /opt/qtmoko/lib/libQtDBus.so.4 >>> #1 0x403e16b8 in bool QBluetoothDbusIface::btcall<void>(QString >>> const&, QDBusReply<void>&, QList<QVariant>, bool, QObject*, char >>> const*, char const*) () from /opt/qtmoko/lib/libqtopiacomm.so.4 >>> #2 0x403eb1e0 in ?? () from /opt/qtmoko/lib/libqtopiacomm.so.4 >>> #3 0x403eb1e0 in ?? () from /opt/qtmoko/lib/libqtopiacomm.so.4 >>> Backtrace stopped: previous frame identical to this frame (corrupt stack?) >> >> Hmm this looks quite strange since it segfaults in the Qt call >> (QDBusAbstractInterface). I cant tell more just from the stacktrace. It would >> be best if i could debug this locally. Hmm and i will probably rework the >> whole bluetooth library after experience with FSO, e.g. so that the BT dbus >> bindings are autogenerated. > > Reading traces and code, I think I found at least one aspect of the > bug. Here is a small patch. As I'm not yet able to compile and test my > modifications, this is a "blind" patch. Can you give me feedback, > please? > > -- > Guilhem BONNEFILLE > -=- JID: [email protected] MSN: [email protected] > -=- mailto:[email protected] > -=- http://nathguil.free.fr/ >
-- Guilhem BONNEFILLE -=- JID: [email protected] MSN: [email protected] -=- mailto:[email protected] -=- http://nathguil.free.fr/
fix-bluetooth.patch
Description: Binary data
_______________________________________________ Openmoko community mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/community
