Re: [PATCH] Patch 2 of 2 for aarch64 ILP32 support in gdb

[Steve Ellcey <sellcey@caviumnetworks.com>]

On Wed, 2017-02-01 at 22:20 +0000, Yao Qi wrote:
> 
> If you get 500 fails in vanilla GDB on aarch64-linux, there must be
> something wrong.  We only have 36 fails in buildbot slave.
> 
> What is your compiler, library and kernel?  They may have some local
> ilp32 patches.

My compiler, library, and kernel do have ILP32 patches, though I am
building gdb in LP64 mode.  Those patches haven't caused new failures
in the GCC testsuite and only a couple of regressions in the glibc
testsuite.

I have heard there are some kernel bugs, fixed in 4.10, that could be
causing some of these failures.  I am using a 4.9 kernel with ILP32
patches.  I was running the testsuite in parallel mode and I have also
heard that could cause problems, I just redid it in serial mode to see
if that helps.  I still got 460 failures when compiling the tests in
LP64 mode.

347 of them are in gdb.threads, with 207 being messages like:

FAIL: gdb.threads/clone-attach-detach.exp: fg attach 2: detach (the program is no longer running)

I.e. a message containing '(the program is no longer running)'  I also
noticed that most of the tests that are failing have the name 'attach'
in them.  There are 97 tests in gdb.base failing and about 2/3 of them
also have some reference to 'attach'. So I think I have some issue
withgdb attaching to a process.  For example, the first failures are:

FAIL: gdb.base/attach-pie-noexec.exp: info shared
FAIL: gdb.base/attach-twice.exp: attach
FAIL: gdb.base/attach.exp: attach1, after setting file
FAIL: gdb.base/attach.exp: attach1 detach (the program is no longer
running)
FAIL: gdb.base/attach.exp: attach2, with no file
FAIL: gdb.base/attach.exp: after attach2, set should_exit
FAIL: gdb.base/attach.exp: continue to breakpoint: postloop (the
program is no longer running)
FAIL: gdb.base/attach.exp: continue until exit at after attach2, exit
(the program is no longer running)
FAIL: gdb.base/attach.exp: attach when process' a.out not in cwd
FAIL: gdb.base/attach.exp: continue until exit (the program is no
longer running)
FAIL: gdb.base/attach.exp: starting with --pid
FAIL: gdb.base/attach.exp: cmdline attach run: run to prompt


Steve Ellcey
sellcey@cavium.com