Need backport for use after free regression in binutils 2.34

Bug #1895068 reported by Tatsuyuki Ishi
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
binutils-mingw-w64 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

There has been a regression in binutils 2.34 [1] and this results in buggy build artifacts for software like DXVK. Although the fix is included in 2.35, it's still a good idea to backport this to 2.34.

A backport commit has already been published [2], and I had success applying the patch to the Ubuntu package source with minor modifications (aligning paths, also CHANGELOG had a conflict but I just removed it because it doesn't affect functionality). The resulting build produces correct output for DXVK, thus confirming the fix.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=25993
[2] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=463ec189fe9eca199edf87cda2c31efbe850390d

Revision history for this message
Stephen Kitt (steve-sk2) wrote :

Unfortunately, because of the way binutils-mingw-w64 is built, this is liable to be complex to fix.

In Focal, I could upload a new version with the patch, but I’m not sure how to go about getting an update into “proposed”.

In Groovy, binutils-source is 2.35, so the only possible fix is to build with that, which would mean getting the Debian 8.11 package synced.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in binutils-mingw-w64 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.