On Tue, 17 Oct 2023 10:57:41 -0500, Justin <r...@neoquasar.org> wrote: >Similar issue in Gentoo: >https://bugs.gentoo.org/show_bug.cgi?id=862201 ><https://bugs.gentoo.org/show_bug.cgi?id=862201> > >Similar issue in FreeBSD, more recent, but different processor: >https://forums.freebsd.org/threads/illegal-instruction-after-12-4-upgrade-i386.89353/ > ><https://forums.freebsd.org/threads/illegal-instruction-after-12-4-upgrade-i386.89353/> > >Relevant GCC commit: >https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=77d372abec0fbf2cfe922e3140ee3410248f979e > ><https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=77d372abec0fbf2cfe922e3140ee3410248f979e>
The corresponding Debian issue are probably #1004893 and #1043281 which was boiled down to a GCC issue, #1005863 and https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104713 As the sudo maintainer, I am reluctant to turn off a hardening feature to support ancient CPUs. I would be reluctant to do that for a normal package, but ESPECIALLY for a package like sudo which is installed nearly everywhere and contains an suid root binary. I am willing to consider arguments and Ctte advice, but as things are now I am fine with the current state. Greetings Marc -- -------------------------------------- !! No courtesy copies, please !! ----- Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834