Comment # 14 on bug 1193139 from Tom de Vries

(In reply to Borislav Petkov from comment #13)
> (In reply to Tom de Vries from comment #10)
> > We did run the tests before, and it started failing only recently, so in
> > that sense it's a regression.
> 
> Can we quantify "only recently" better? Maybe I can bisect the 15SP3 kernel
> and see what has caused this...

It's a good question, unfortunately I don't have a good answer yet.

On OBS, I saw this problem pop up in devel:gcc/gdb in the last two weeks or so.
 Of course there's no guarantee that all the machines that were used for
testing before did support mpx, but things suddenly started failing over
several configurations, so it certainly has the appearance of regression.

I can reproduce the problem on both my laptops with openSUSE Leap 15.3
installed.

I tried as hunch to install the kernel 5.3.18-59.10 (which AFAIU is 15.3 GA)
and still reproduced the problem.

I'm now trying to reinstall leap 15.2 on my insert-distro-here laptop, but am
running into installation problems which I'm trying to solve.

In the past year, I have run leap15.2 on my laptop, I only switched to 15.3
recently.  I have fixed problems related to mpx m32 in the test-suite, and I
did not see these failures then.

Last fix there:
...
commit 0c4e2c6c88e9e67ca39f4f2e3bdb205b4f4a1e6c
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue Jan 19 13:31:12 2021 +0100

    [gdb/testsuite] Fix gdb.arch/i386-mpx.exp with -m32
...

I occasionally ran test with -m32 and did not meet this problem till I noticed
the problem on OBS, after which I reproduced on my laptop which at this point
was already switched to leap 15.2.