Looks like the specific upstream issue is
https://github.deere.com/FOCUS/WineATL/blob/fab575865d1bbceedde12226d2517d17b20189bc/gdb/wine-
add-symbol-file.py
And there's a build for kinetic that contains the fix, which does
actually install and work on jammy (since no other dependencies changed
too
It's fixed upstream on the 2.38 branch too, and kinetic has that update
in binutils-source_2.38-4ubuntu1. So binutils-mingw-w64 just needs to be
recompiled against that latest binutils-source package (no other changes
needed, it already pulls the latest). And ideally an SRU back to jammy
LTS, just
** Bug watch added: Sourceware.org Bugzilla #28885
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
** Also affects: binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
Importance: Unknown
Status: Unknown
** Also affects: binutils (Ubuntu)
Importance: Undeci
Linking binutils package and subscribing Mattias Klose since
https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu1 mentions
"Update from the binutils 2.38 branch: Fix PR 28885" and so a rebuild
based on binutils-source_2.38-4ubuntu1 would fix this issue.
--
You received this bug notificatio
** Also affects: wine via
https://bugs.winehq.org/show_bug.cgi?id=52770
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/19719
Looks like https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2
is now in the ubuntu-proposed pocket (thanks Matthias!). So binutils-
mingw-w64 would just need a recompile based on that resulting new
binutils-source_2.38-4ubuntu2_all.deb.
I don't think there should be any changes needed to
> Changed in binutils-mingw-w64 (Ubuntu):
> status: Triaged → Fix Released
not fixed in Kinetic yet either; it would be if rebuilt with the
binutils-source there now, but
https://launchpad.net/ubuntu/+source/binutils-mingw-w64/9build1 built on
2022-04-26 is before Mattias brought in PR2885
> And it fixes a VSCode integration issue.
Also Qt Creator. And probably most any other gdb GUI that displays a
"locals" window and therefore might try to display an optimized-out
symbol.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
binutils fix publised to jammy-updates on 2022-10-24, binutils-mingw-w64
would just need a recompile against binutils-source 2.38-4ubuntu2 to fix
this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
** Changed in: binutils (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1971901
Title:
dlltool uses non-unique
The versioning is confusing because this package is not self-contiained.
It gets most of its source code from another package, recorded via
`Built-Using: binutils` in its debian/control file. The actual buggy
code is in binutils-source 2.38-3ubuntu1; binutils-source 2.38-4ubuntu2
contains the fix.
@dannf Thanks, it works for on my x86 winelib program too (amd64
installation).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1848200
Title:
gdb not stopping on breakpoint in
12 matches
Mail list logo