https://bugs.winehq.org/show_bug.cgi?id=48161
--- Comment #18 from Paul Gofman gofmanp@gmail.com ---
What package did you see this in? The WineHQ 5.0-rc1 packages are all built with -fno-stack-protector and -fcf-protection=none.
The snippet from Comment #14 is from https://dl.winehq.org/wine-builds/fedora/31/x86_64/wine-devel64-5.0.rc1-2.2....
The cf-protection is definately there. The objdump clearly shows the instructions at function start, and also:
rpm -q --queryformat="%{NAME}: %{OPTFLAGS}\n" ./wine-devel64-5.0.rc1-2.2.x86_64.rpm:
wine-devel64: -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
Regarding the Ubuntu binary, I've checked the disassembly and could not actually find stack protection code there. So the error I've got probably comes from some native libraries which were confused by something else. Unfortunately I don't have Ubuntu installation here at the moment and cannot test it properly, so the problem might be caused by my run of those binaries on Fedora, or, more likely, some completely different build specifics. Please note that AION32 still starts fine with my local build with default flags.
So what is exactly is wrong (if anything) with Ubuntu build is subject for further debugging, but frankly it would be much less time consuming for me if I could test an official Fedora build without -fcf-protection and stack protection first, and see if it is OK here, or if it shows the same problem, which I would debug on Fedora in this case.