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/pa
** 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
Touch seeded packages, wh
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 yo
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
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
http
Simon, no fix has been uploaded yet?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1934995
Title:
Broken on ppc64el (toolchain bug?)
Status in glibc package in Ubuntu:
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
Touch seeded packages, which is subscribed to umockdev
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.
--
Yo
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 **)(&real_open) = dlsym(RTLD_NEXT, "open");
return (*real_open)(path, flags, mode);
The declaration for real_open here
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 em
Next possible culprit: binutils
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1934995
Title:
Broken on ppc64el (toolchain bug?)
Status in umockdev package in Ubuntu:
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
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&via=matrix.org&via=cooperteam.net
)
The stack-smashing backtrace implicates LTTNG,
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 otherw
13 matches
Mail list logo
