[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
This bug was fixed in the package mir - 2.4.1-0ubuntu2 --- mir (2.4.1-0ubuntu2) impish; urgency=medium * debian/patches/fix-UB-in-open-interposer.patch: - Cherry-pick upstream patches fixing UB in the test-suite, resulting in a FTBFS on ppc64el (LP: #1934995) * debian/patches/work-around-gcc-maybe-uninitialised-bug.patch: - Cherry-pick upstream patches working around an incorrect warning caused by a gcc bug exposed with the previous patch. -- Christopher James Halse Rogers Wed, 28 Jul 2021 11:01:36 +1000 ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Invalid ** Changed in: umockdev (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Oh, sorry, I know see how my sentence is ambiguous. I meant that the failing autopkgtests are fixed in the latest version of mir uploaded to -proposed, but that version fails to build because of this bug. So the mentioned fix is *not* for this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Simon, no fix has been uploaded yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Martin, right I thought I'd said that in my comment too about the prototype in the header but apparently I only thought it really loudly, or something :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Blocks migration to -updates as the fixed mir package FTBFSe. ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Indeed the open(2) manpage is misleading in that regard. The actual definition in fcntl.h is like this: extern int open (const char *__file, int __oflag, ...) __nonnull ((1)); (with a few variants, but they all use varargs). So I did the same in umockdev for full header compatibility. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
So I don't have the faintest idea what caused this to start failing but the issue here is in mir: int (*real_open)(char const *path, int flags, mode_t mode); *(void **)(_open) = dlsym(RTLD_NEXT, "open"); return (*real_open)(path, flags, mode); The declaration for real_open here does not match that used by the open() function call in umockdev, which uses va_args. This means that the stack frame gcc creates for mir's wrapper does not have space for a parameter save area which the code gcc generates for umockdev assumes it has, and so the stack gets stomped on. So if the prototype in mir is fixed here (also the one for open64) I bet things will start working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Ok: A list of things that it appears *not* to be: 1) binutils, valac, gcc versions. A umockdev build with the versions that hirsute's 0.15.4-1 built with. 2) The "debugedit: debian/umockdev/usr/bin/umockdev-record: Unknown DWARF DW_FORM_0x1f20" messages; building an unstripped umockdev doesn't emit this message (as it's no longer invoked by dh_strip), but the built package still results in the Mir tests failing as above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Next possible culprit: binutils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Yeah, whatever change in dependencies causes this it goes back to hirsute release. Running mir 2.3.3's tests against 0.15.4-1 from the hirsute archive works; running those tests against 0.15.4-1 rebuilt in a hirsute chroot fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Seb has rebuilt bolt in impish, which uses umockdev for some of its tests, and that apparently works ( https://matrix.to/#/!cVrEyzKyyNYOVfcQsb:libera.chat/$az_4Y_uIkZ02vMS6WjfQlkTvOH_ikJQTCkqRsAcOBfY?via=libera.chat=matrix.org=cooperteam.net ) The stack-smashing backtrace implicates LTTNG, so maybe there's some strange interaction there? I'm not sure this is an upstream bug, as rebuilding 0.15.4 makes the crash appear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)
Dang, we already found a ppc64el SIGBUS issue in 0.16.0, which got fixed in https://github.com/martinpitt/umockdev/commit/277c80243a . But this is reported against 0.16.1 already. There is a tiny chance that https://github.com/martinpitt/umockdev/commit/264cabbb will magically fix this, but otherwise this needs some investigation. I.e. not known upstream yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
