On Monday 30 of June 2014 17:31:39 Thiago Macieira wrote: > Em seg 30 jun 2014, às 14:14:10, Milian Wolff escreveu: > > On Monday 30 June 2014 00:05:10 šumski wrote: > > > On Thursday 26 of June 2014 12:14:49 Milian Wolff wrote: > > > > Hey, > > > > > > > > did you run it through valgrind? > > > > > > Here's what valgrind says: > > Sounds like a bug in Qt to me, I have to say. Looking at the code, > > QDBusConnectionPrivate::objectDestroyed looks pretty fragile, I mean it > > does this at the end: > > > > obj->disconnect(this); > > > > But from the code in QDBusConnectionPrivate::disconnectSignal nothing > > jumps out as dangerous directly. The fact, that valgrind is getting > > confused in the stack trace is not helping either ;-) Could you maybe > > try to compile qtbase in debug mode and reproduce the issue, such that > > we get a full stacktrace without optimizations etc.? > > > > Anyways, maybe Thiago (CC'ed) can give us some insight on whats going on > > here. > > This is happening in a global destructor during the use of a global static. > My guess would be that the global static has already been destroyed, hence > the issue. > > Try this patch, which removes it. We have QStringLiteral nowadays. Confirming that segfault no longer happens with the patch!
Cheers, Hrvoje
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
