Good catch! I've seen this in the past due to uninitialised variables. With optimisation, the compiler gets more aggressive about register re-use, so a bug can manifest under optimisation when the uninitialised variable ends up in a register that had a previous value in it. (In debug mode, the variable often picks up a zero value instead.)
Not sure if there is an easy way to track down whether this is the case or if this is a genuine code generation problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1621002 Title: Mediascanner2 test failure on yakkety/{armhf,arm64,ppc64el} with latest dbus-cpp Status in dbus-cpp package in Ubuntu: New Status in mediascanner2 package in Ubuntu: New Bug description: When trying to build a new mediascanner2 release, tests failed on a number of architectures when building under Yakkety. Some relevant logs: https://launchpadlibrarian.net/281862518/buildlog_ubuntu-yakkety-armhf.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/282074929/buildlog_ubuntu-yakkety-arm64.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/281862178/buildlog_ubuntu-yakkety-ppc64el.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz The failure is occurring in code not touched by the changes in the silo, and I suspect that this is related to dbus-cpp or possibly GCC 6. The segfault doesn't occur on x86, but I was able to reproduce it on my Chromebook. Attached is a stacktrace from the test_dbus test program. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1621002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
