[Development] DBus signals for (dlclose'd) style plugin causing crash during application exit?

Thiago Macieira thiago.macieira at intel.com
Wed May 3 19:46:34 CEST 2017

Em quarta-feira, 3 de maio de 2017, às 08:45:42 PDT, René J.V. Bertin 
> On Wednesday May 03 2017 12:08:49 Edward Welbourne wrote:
> >https://testresults.qt.io/logs/qt/qtbase/74dfb52faa8370b61de9eb89947bfdd473
> >fe4986/LinuxUbuntu_15_04x86_64LinuxUbuntuTouch_15_04armv7GCCqtci-linux-Ubun
> >tu-15.04-x86_64-6e07ddDisableTests_OpenGLES2/85d6b000f945a84bc84a4f01f53ac6
> >5bc05cbe86/buildlog.txt.gz
> >
> >... apparently repeatably.  So Thiago is, understandably, reticent about
> >moving forward until we can make sense of it.
> Yes, but that also leaves you in a deadlock and I cannot shake the idea that
> at some point you'll have to move forward to get out of that one.

Yep. But my action might not be what you expect.

> That's on ARM, btw, does it only happen on that platform? Do you at least
> know where in qdbusxml2cpp something remains stuck (and for how long)?

You've got all of the information available to us. That's in the link above.

> For what it's worth, I cannot remember exactly how I maintained my patch
> from 5.6.x through 5.7.1 to 5.8.0 - it's possible I refactored it manually.
> So for giggles or otherwise, I'm attaching what I'm using.

There was a minor update required for 5.8. I don't remember if 5.7 required 

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list