On Tuesday 18 January 2011 14:49:05 Pierre Rossi wrote: > Actually, I believe it was a very different issue, since the backtraces are > totally different: > http://paste.kde.org/~shadeslayer/2488/
I think that, too. > And that's not quite the conclusion I drew of this conversation, but my > attention was drawn towards the fact that we were using QWeakPointer > without a QSharedPointer, which seemed weird at first. > In any case, for those who are curious, here's where the discussion led: > > http://doc.trolltech.com/latest/qweakpointer.html#tracking-qobject > > and the commit that made this possible: > http://qt.gitorious.org/qt/qt/commit/021a116d48a1df3624ad2221a418f1585f7ec4 > f8 I started using QWeakPointer instead of QPointer because of this: http://doc.trolltech.com/latest/qweakpointer.html#details > Both are a bit of a mystery to me, but if you guys have a way of > reproducing either of those crashes, I'm willing to investigate. While I have a couple of half-ideas about the crash Rohan pointed out, I perfectly know how to reproduce my bug: just click on the set bookmark icon on the urlbar. I did not explained it before to have informations about how you treat such backtraces ;) > Cheers, > -- > Pierre Cheers, -- Andrea Diamantini, adjam GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F rekonq project WEB: http://rekonq.kde.org IRC: rekonq@freenode
_______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
