Bug#1004894: sudo: [i386] invalid opcode

2022-03-25 Thread Martin-Éric Racine
On Mon, Mar 14, 2022 at 4:45 PM Martin-Éric Racine wrote: > > On Mon, Mar 14, 2022 at 4:39 PM Marc Haber > wrote: > > > > On Mon, Mar 14, 2022 at 04:32:58PM +0200, Martin-Éric Racine wrote: > > > On Mon, Mar 14, 2022 at 4:30 PM Marc Haber > > > wrote: > > > > > > > > On Mon, Mar 14, 2022 at 04:2

Bug#1004894: sudo: [i386] invalid opcode

2022-03-14 Thread Martin-Éric Racine
On Mon, Mar 14, 2022 at 4:39 PM Marc Haber wrote: > > On Mon, Mar 14, 2022 at 04:32:58PM +0200, Martin-Éric Racine wrote: > > On Mon, Mar 14, 2022 at 4:30 PM Marc Haber > > wrote: > > > > > > On Mon, Mar 14, 2022 at 04:23:40PM +0200, Martin-Éric Racine wrote: > > > > The Geode LX is not a vanilla

Bug#1004894: sudo: [i386] invalid opcode

2022-03-14 Thread Marc Haber
On Mon, Mar 14, 2022 at 04:32:58PM +0200, Martin-Éric Racine wrote: > On Mon, Mar 14, 2022 at 4:30 PM Marc Haber > wrote: > > > > On Mon, Mar 14, 2022 at 04:23:40PM +0200, Martin-Éric Racine wrote: > > > The Geode LX is not a vanilla 586. It is a vanilla 686. The reported > > > CPU variant has sim

Bug#1004894: sudo: [i386] invalid opcode

2022-03-14 Thread Martin-Éric Racine
On Mon, Mar 14, 2022 at 4:30 PM Marc Haber wrote: > > On Mon, Mar 14, 2022 at 04:23:40PM +0200, Martin-Éric Racine wrote: > > The Geode LX is not a vanilla 586. It is a vanilla 686. The reported > > CPU variant has simply remained at 586 for reasons only known to AMD. > > According to all docs ava

Bug#1004894: sudo: [i386] invalid opcode

2022-03-14 Thread Marc Haber
On Mon, Mar 14, 2022 at 04:23:40PM +0200, Martin-Éric Racine wrote: > The Geode LX is not a vanilla 586. It is a vanilla 686. The reported > CPU variant has simply remained at 586 for reasons only known to AMD. According to all docs available to me, it is a vanilla 686 sans multi-byte NOP ("NOPL")

Bug#1004894: sudo: [i386] invalid opcode

2022-03-14 Thread Martin-Éric Racine
On Mon, Mar 14, 2022 at 4:21 PM Marc Haber wrote: > > Control: tags -1 wontfix > Control: severity -1 minor > thanks > > On Sat, Feb 19, 2022 at 09:02:02AM +0100, Henning Paul wrote: > > IIRC, it doesn't implement all of the i686 instruction set (hence the > > illegal opcode). > > I apologize, but

Bug#1004894: sudo: [i386] invalid opcode

2022-03-14 Thread Marc Haber
Control: tags -1 wontfix Control: severity -1 minor thanks On Sat, Feb 19, 2022 at 09:02:02AM +0100, Henning Paul wrote: > IIRC, it doesn't implement all of the i686 instruction set (hence the > illegal opcode). I apologize, but it looks like the Geode LX is no longer among the CPUs supported in

Bug#1004894: sudo: [i386] invalid opcode

2022-02-19 Thread Henning Paul
Hello, Am 19.02.22 um 06:30 schrieb Marc Haber: On Fri, Feb 18, 2022 at 09:51:57PM +0100, Henning Paul wrote: root@alix:~# lscpu Architecture: i586 CPU op-mode(s): 32-bit Address sizes:32 bits physical, 32 bits virtual Byte Order: Little Endian CPU(s):

Bug#1004894: sudo: [i386] invalid opcode

2022-02-18 Thread Marc Haber
On Fri, Feb 18, 2022 at 09:51:57PM +0100, Henning Paul wrote: > root@alix:~# lscpu > Architecture: i586 > CPU op-mode(s): 32-bit > Address sizes:32 bits physical, 32 bits virtual > Byte Order: Little Endian > CPU(s): 1 > On-line CPU(s) list:

Bug#1004894: sudo: [i386] invalid opcode

2022-02-18 Thread Henning Paul
Am 18.02.22 um 15:21 schrieb Henning Paul: On Wed, 16 Feb 2022 22:45:28 Martin-Éric Racine wrote: On Wed, Feb 16, 2022 at 10:31 PM Marc Haber wrote: On Wed, Feb 16, 2022 at 07:15:37PM +0200, Martin-Éric Racine wrote: So it still doesn't build on Geode LX. How about your i386 build chroot?

Bug#1004894: sudo: [i386] invalid opcode

2022-02-16 Thread Martin-Éric Racine
On Wed, Feb 16, 2022 at 10:31 PM Marc Haber wrote: > > On Wed, Feb 16, 2022 at 07:15:37PM +0200, Martin-Éric Racine wrote: > > I cannot help but wonder why the build doesn't simply parse > > $(HARDENING_CFLAGS) and $(HARDENING_LDFLAGS). Hard-coded hardening > > options tend to be a bad idea. GCC s

Bug#1004894: sudo: [i386] invalid opcode

2022-02-16 Thread Marc Haber
On Wed, Feb 16, 2022 at 07:15:37PM +0200, Martin-Éric Racine wrote: > I cannot help but wonder why the build doesn't simply parse > $(HARDENING_CFLAGS) and $(HARDENING_LDFLAGS). Hard-coded hardening > options tend to be a bad idea. GCC supports them all, but the target > host's CPU won't always sup

Bug#1004894: sudo: [i386] invalid opcode

2022-02-16 Thread Martin-Éric Racine
On Wed, Feb 16, 2022 at 6:45 PM Marc Haber wrote: > On Tue, Feb 15, 2022 at 09:58:49PM +0200, Martin-Éric Racine wrote: > > On Tue, Feb 15, 2022 at 9:10 PM Marc Haber > > wrote: > > > > > > On Tue, Feb 15, 2022 at 09:03:01PM +0200, Martin-Éric Racine wrote: > > > > 1.9.8p2-1 FTBFS on Geode testin

Bug#1004894: sudo: [i386] invalid opcode

2022-02-16 Thread Marc Haber
Hi, On Tue, Feb 15, 2022 at 09:58:49PM +0200, Martin-Éric Racine wrote: > On Tue, Feb 15, 2022 at 9:10 PM Marc Haber > wrote: > > > > On Tue, Feb 15, 2022 at 09:03:01PM +0200, Martin-Éric Racine wrote: > > > 1.9.8p2-1 FTBFS on Geode testing host (log attached earlier) > > > 1.9.9-1 FTBFS on Geode

Bug#1004894: sudo: [i386] invalid opcode

2022-02-16 Thread Martin-Éric Racine
On Wed, Feb 16, 2022 at 10:11 AM Marc Haber wrote: > > On Wed, Feb 16, 2022 at 10:08:01AM +0200, Martin-Éric Racine wrote: > > ../../../lib/util/json.c:122:1: internal compiler error: in > > graphds_scc, at graphds.c:316 > > That makes it a toolchain issue. > > This bug has grown huge. Can you ple

Bug#1004894: sudo: [i386] invalid opcode

2022-02-16 Thread Marc Haber
On Wed, Feb 16, 2022 at 10:08:01AM +0200, Martin-Éric Racine wrote: > ../../../lib/util/json.c:122:1: internal compiler error: in > graphds_scc, at graphds.c:316 That makes it a toolchain issue. This bug has grown huge. Can you please file a new bug against gcc and mark this bug as affected? I am

Bug#1004894: sudo: [i386] invalid opcode

2022-02-16 Thread Martin-Éric Racine
On Wed, Feb 16, 2022 at 9:11 AM Marc Haber wrote: > > On Tue, Feb 15, 2022 at 09:58:49PM +0200, Martin-Éric Racine wrote: > > On Tue, Feb 15, 2022 at 9:10 PM Marc Haber > > wrote: > > > > > > On Tue, Feb 15, 2022 at 09:03:01PM +0200, Martin-Éric Racine wrote: > > > > 1.9.8p2-1 FTBFS on Geode test

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Marc Haber
On Tue, Feb 15, 2022 at 09:58:49PM +0200, Martin-Éric Racine wrote: > On Tue, Feb 15, 2022 at 9:10 PM Marc Haber > wrote: > > > > On Tue, Feb 15, 2022 at 09:03:01PM +0200, Martin-Éric Racine wrote: > > > 1.9.8p2-1 FTBFS on Geode testing host (log attached earlier) > > > 1.9.9-1 FTBFS on Geode test

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Martin-Éric Racine
On Tue, Feb 15, 2022 at 9:10 PM Marc Haber wrote: > > On Tue, Feb 15, 2022 at 09:03:01PM +0200, Martin-Éric Racine wrote: > > 1.9.8p2-1 FTBFS on Geode testing host (log attached earlier) > > 1.9.9-1 FTBFS on Geode testing host (log attached earlier) > > I apologize, I didnt see earlier that your b

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Marc Haber
On Tue, Feb 15, 2022 at 09:03:01PM +0200, Martin-Éric Racine wrote: > 1.9.8p2-1 FTBFS on Geode testing host (log attached earlier) > 1.9.9-1 FTBFS on Geode testing host (log attached earlier) I apologize, I didnt see earlier that your builds were already failing at build time. The error is config

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Martin-Éric Racine
On Tue, Feb 15, 2022 at 8:35 PM Marc Haber wrote: > > On Tue, Feb 15, 2022 at 04:12:03PM +0200, Martin-Éric Racine wrote: > > I also tried building that 1.9.8p2-1 on my amd64 host's i386 chroot. > > It builds, and the binaries don't produce a core dump on the Geode > > host. Presumably the breakag

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Marc Haber
On Tue, Feb 15, 2022 at 04:12:03PM +0200, Martin-Éric Racine wrote: > I also tried building that 1.9.8p2-1 on my amd64 host's i386 chroot. > It builds, and the binaries don't produce a core dump on the Geode > host. Presumably the breakage happened after that release. > > Hopefully this can help y

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Martin-Éric Racine
On Tue, Feb 15, 2022 at 3:04 PM Martin-Éric Racine wrote: > > On Tue, Feb 15, 2022 at 1:52 PM Marc Haber > wrote: > > > > On Tue, Feb 15, 2022 at 12:47:47PM +0100, Marc Haber wrote: > > > On Tue, Feb 15, 2022 at 01:36:17PM +0200, Martin-Éric Racine wrote: > > > > Logged onto my unstable-i386 chro

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Marc Haber
On Tue, Feb 15, 2022 at 12:47:47PM +0100, Marc Haber wrote: > On Tue, Feb 15, 2022 at 01:36:17PM +0200, Martin-Éric Racine wrote: > > Logged onto my unstable-i386 chroot. > > $ dget http://deb.debian.org/debian/pool/main/s/sudo/sudo_1.9.5p2-3.dsc > > Fetched build-deps. > > $ debuild -uc -us > > Co

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Marc Haber
On Tue, Feb 15, 2022 at 01:36:17PM +0200, Martin-Éric Racine wrote: > Logged onto my unstable-i386 chroot. > $ dget http://deb.debian.org/debian/pool/main/s/sudo/sudo_1.9.5p2-3.dsc > Fetched build-deps. > $ debuild -uc -us > Copied sudo and sudo-dbgsym over to the Geode host. > Logged onto the Geod

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Martin-Éric Racine
On Tue, Feb 15, 2022 at 1:23 PM Marc Haber wrote: > > On Tue, Feb 15, 2022 at 12:56:54PM +0200, Martin-Éric Racine wrote: > > On Thu, Feb 3, 2022 at 10:14 AM Martin-Éric Racine > > wrote: > > > On Thu, Feb 3, 2022 at 10:10 AM Marc Haber > > > wrote: > > > > On Thu, Feb 03, 2022 at 09:55:53AM +02

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Marc Haber
On Tue, Feb 15, 2022 at 12:56:54PM +0200, Martin-Éric Racine wrote: > On Thu, Feb 3, 2022 at 10:14 AM Martin-Éric Racine > wrote: > > On Thu, Feb 3, 2022 at 10:10 AM Marc Haber > > wrote: > > > On Thu, Feb 03, 2022 at 09:55:53AM +0200, Martin-Éric Racine wrote: > > > > On Thu, Feb 3, 2022 at 9:41

Bug#1004894: sudo: [i386] invalid opcode

2022-02-15 Thread Martin-Éric Racine
On Thu, Feb 3, 2022 at 10:14 AM Martin-Éric Racine wrote: > > On Thu, Feb 3, 2022 at 10:10 AM Marc Haber > wrote: > > On Thu, Feb 03, 2022 at 09:55:53AM +0200, Martin-Éric Racine wrote: > > > On Thu, Feb 3, 2022 at 9:41 AM Marc Haber > > > wrote: > > > > > > > > On Thu, Feb 03, 2022 at 09:11:10A

Bug#1004894: sudo: [i386] invalid opcode

2022-02-03 Thread Marc Haber
On Thu, Feb 03, 2022 at 10:11:30AM +0200, Martin-Éric Racine wrote: > W: sudo-dbgsym: elf-error In program headers: Unable to find program > interpreter name > [usr/lib/debug/.build-id/52/9f0be3cc3ee3895db3782367a6d5027b490c16.debug] See #1000977 and #1000449 tl;dr, that's a binutils bug, which i

Bug#1004894: sudo: [i386] invalid opcode

2022-02-03 Thread Martin-Éric Racine
On Thu, Feb 3, 2022 at 10:10 AM Marc Haber wrote: > On Thu, Feb 03, 2022 at 09:55:53AM +0200, Martin-Éric Racine wrote: > > On Thu, Feb 3, 2022 at 9:41 AM Marc Haber > > wrote: > > > > > > On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > > > > On a Geode LX (i686 without PAE)

Bug#1004894: sudo: [i386] invalid opcode

2022-02-03 Thread Martin-Éric Racine
On Thu, Feb 3, 2022 at 9:55 AM Martin-Éric Racine wrote: > > On Thu, Feb 3, 2022 at 9:41 AM Marc Haber > wrote: > > > > On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > > > On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg > > > shows the following: >

Bug#1004894: sudo: [i386] invalid opcode

2022-02-03 Thread Marc Haber
Hi, On Thu, Feb 03, 2022 at 09:55:53AM +0200, Martin-Éric Racine wrote: > On Thu, Feb 3, 2022 at 9:41 AM Marc Haber > wrote: > > > > On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > > > On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg > > > shows the

Bug#1004894: sudo: [i386] invalid opcode

2022-02-02 Thread Martin-Éric Racine
On Thu, Feb 3, 2022 at 9:41 AM Marc Haber wrote: > > On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > > On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg > > shows the following: > > Just for the record, the current i386 sudo was built on x86-ubc-02, Lo

Bug#1004894: sudo: [i386] invalid opcode

2022-02-02 Thread Marc Haber
On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg > shows the following: Just for the record, the current i386 sudo was built on x86-ubc-02, Logs https://buildd.debian.org/status/logs.php?pkg=sudo&ver=1.9

Bug#1004894: sudo: [i386] invalid opcode

2022-02-02 Thread Martin-Éric Racine
Package: sudo Version: 1.9.9-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On a Geode LX (i686 without PAE), the most recent sudo dumps core. dmesg shows the following: # dmesg | grep traps [ 150.890563] traps: sudo[729] trap invalid opcode ip:44ffa0 sp:bfd59cfc error: