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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1621002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
