sord segfaults on s390x / ppc64el - related to gcc-10.2 optimizations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-10 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
sord (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Sord has issues on these platforms if built with a recent toolchain.
I reported it upstream as I got good workarounds but failed to spot the root cause.
See: https:/
The effect in Ubuntu is that packages using sort can segfault on free.
Currently this blocks https:/
as it runs:
$ /usr/lib/
That segfaults then.
I've found that it works:
- with gcc-9
- on x86/armhf/
- with -fno-schedule-insns -fno-schedule-
This could be either gcc-10 being too aggressive or (more likely) an issue in sord that is hard to see and not triggered up to now, but exposed by the new optimizations.
I'll file this against sord (to track the mitigation upload, as well as any discussion and point to upstream) as well as gcc-10 (since we have seen a bunch of those 'fails due to new toolchain') in case there is something in the toolchain to fix.
Steps to reproduce in Hirsute-proposed
$ sudo apt install gstreamer1.
$ /usr/lib/
gst-codec-info-1.0: ../src/
Aborted (core dumped)
In the upstream bug I outlined how to (re)compile sord as needed for any experiments.
=> https:/
A Test PPA which had various iterations of trying to be surgical with the change (well, more surgical than global -O1) is at: https:/
Changed in sord (Ubuntu): | |
status: | New → In Progress |
We've found the fix in the upstream discussion.
gcc is not more a suspect :-)
Uploading a fix to unblock gst-plugins in Hirsute.
Since this is upstream it will be able to be a sync soon again.