numerous tests fail in "make check" stage of gdb-8.0.1 on Debian 8.8 powerpc64

numerous tests fail in "make check" stage of gdb-8.0.1 on Debian 8.8 powerpc64

[Dennis Clarke]

This is a Debian 8.8 system on a PowerMac G5 with dual PowerPC 970
processors.

The output from config.guess looks to be reasonable and the configure 
stage went along nicely with an odd warning :


deb8_ppc64$ ../gdb-8.0.1/config.guess
powerpc64-unknown-linux-gnu

deb8_ppc64$ ../gdb-8.0.1/configure --host=powerpc64-unknown-linux-gnu \
 > --target=powerpc64-unknown-linux-gnu --with-expat=/usr/local \
 > --with-gdb-datadir=/usr/local/share/gdb --without-libunwind-ia64 \
 > --without-lzma --with-separate-debug-dir=/usr/local/lib/debug \
 > --with-system-gdbinit=/etc/opt/gdb/gdbinit --with-zlib \
 > --without-babeltrace
configure: WARNING: If you wanted to set the --build type, don't use --host.
     If a cross compiler is detected then cross compile mode will be used.
checking build system type... powerpc64-unknown-linux-gnu
checking host system type... powerpc64-unknown-linux-gnu
checking target system type... powerpc64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... no
checking for mawk... mawk
checking for powerpc64-unknown-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for powerpc64-unknown-linux-gnu-g++... no
checking for powerpc64-unknown-linux-gnu-c++... no
checking for powerpc64-unknown-linux-gnu-gpp... no
checking for powerpc64-unknown-linux-gnu-aCC... no
checking for powerpc64-unknown-linux-gnu-CC... no
checking for powerpc64-unknown-linux-gnu-cxx... no
checking for powerpc64-unknown-linux-gnu-cc++... no
checking for powerpc64-unknown-linux-gnu-cl.exe... no
checking for powerpc64-unknown-linux-gnu-FCC... no
checking for powerpc64-unknown-linux-gnu-KCC... no
checking for powerpc64-unknown-linux-gnu-RCC... no
checking for powerpc64-unknown-linux-gnu-xlC_r... no
checking for powerpc64-unknown-linux-gnu-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether g++ accepts -static-libstdc++ -static-libgcc... yes
checking for powerpc64-unknown-linux-gnu-gnatbind... no
checking for gnatbind... gnatbind
checking for powerpc64-unknown-linux-gnu-gnatmake... no
checking for gnatmake... gnatmake
checking whether compiler driver understands Ada... yes
checking how to compare bootstrapped objects... cmp --ignore-initial=16 
$$f1 $$f2
checking for objdir... .libs
checking for isl 0.16, 0.15, or deprecated 0.14... yes
checking for isl 0.16 or 0.15... yes
checking for default BUILD_CONFIG...
checking for --enable-vtable-verify... no
checking for bison... bison -y
checking for bison... bison
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for flex... flex
checking for flex... flex
checking for makeinfo... makeinfo
checking for expect... expect
checking for runtest... runtest
checking for powerpc64-unknown-linux-gnu-ar... no
checking for ar... ar
checking for powerpc64-unknown-linux-gnu-as... no
checking for as... as
checking for powerpc64-unknown-linux-gnu-dlltool... no
checking for dlltool... no
checking for powerpc64-unknown-linux-gnu-ld... no
checking for ld... ld
checking for powerpc64-unknown-linux-gnu-lipo... no
checking for lipo... no
checking for powerpc64-unknown-linux-gnu-nm... no
checking for nm... nm
checking for powerpc64-unknown-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for powerpc64-unknown-linux-gnu-strip... no
checking for strip... strip
checking for powerpc64-unknown-linux-gnu-windres... no
checking for windres... no
checking for powerpc64-unknown-linux-gnu-windmc... no
checking for windmc... no
checking for powerpc64-unknown-linux-gnu-objcopy... no
checking for objcopy... objcopy
checking for powerpc64-unknown-linux-gnu-objdump... no
checking for objdump... objdump
checking for powerpc64-unknown-linux-gnu-readelf... no
checking for readelf... readelf
checking for powerpc64-unknown-linux-gnu-cc... no
checking for cc... cc
checking for powerpc64-unknown-linux-gnu-c++... no
checking for c++... c++
checking for powerpc64-unknown-linux-gnu-gcc... no
checking for gcc... gcc
checking for powerpc64-unknown-linux-gnu-gfortran... no
checking for gfortran... gfortran
checking for powerpc64-unknown-linux-gnu-gccgo... no
checking for gccgo... no
checking for powerpc64-unknown-linux-gnu-ar... no
checking for ar... ar
checking for powerpc64-unknown-linux-gnu-as... no
checking for as... as
checking for powerpc64-unknown-linux-gnu-dlltool... no
checking for dlltool... no
checking for powerpc64-unknown-linux-gnu-ld... no
checking for ld... ld
checking for powerpc64-unknown-linux-gnu-lipo... no
checking for lipo... no
checking for powerpc64-unknown-linux-gnu-nm... no
checking for nm... nm
checking for powerpc64-unknown-linux-gnu-objcopy... no
checking for objcopy... objcopy
checking for powerpc64-unknown-linux-gnu-objdump... no
checking for objdump... objdump
checking for powerpc64-unknown-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for powerpc64-unknown-linux-gnu-readelf... no
checking for readelf... readelf
checking for powerpc64-unknown-linux-gnu-strip... no
checking for strip... strip
checking for powerpc64-unknown-linux-gnu-windres... no
checking for windres... no
checking for powerpc64-unknown-linux-gnu-windmc... no
checking for windmc... no
checking where to find the target ar... host tool
checking where to find the target as... host tool
checking where to find the target cc... host tool
checking where to find the target c++... host tool
checking where to find the target c++ for libstdc++... host tool
checking where to find the target dlltool... host tool
checking where to find the target gcc... host tool
checking where to find the target gfortran... host tool
checking where to find the target gccgo... host tool
checking where to find the target ld... host tool
checking where to find the target lipo... host tool
checking where to find the target nm... host tool
checking where to find the target objcopy... host tool
checking where to find the target objdump... host tool
checking where to find the target ranlib... host tool
checking where to find the target readelf... host tool
checking where to find the target strip... host tool
checking where to find the target windres... host tool
checking where to find the target windmc... host tool
checking whether to enable maintainer-specific portions of Makefiles... no
configure: creating ./config.status
config.status: creating Makefile
deb8_ppc64$

The compile went along fine and am running tests now but seeing a number 
of "FAIL" messages :


FAIL: gdb.base/dup-sect.exp: split
FAIL: gdb.base/dup-sect.exp: var1 after strip
FAIL: gdb.base/dup-sect.exp: var2 after strip
.
.
.
FAIL: gdb.base/ending-run.exp: step out of main
FAIL: gdb.base/ending-run.exp: step to end of run
.
.
.
FAIL: gdb.base/examine-backward.exp: char-width=1, print-max=20: take 6 
strings backward (pattern 1)
FAIL: gdb.base/examine-backward.exp: char-width=1, print-max=20: take 1 
string backward (6/6)
Running 
/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb/testsuite/../../../gdb-8.0.1/gdb/testsuite/gdb.base/exe-lock.exp 
...

etc etc etc

It is difficult to know if the entire gdb build should be tossed away or 
is this normal behavior ?

Dennis

Re: numerous tests fail in "make check" stage of gdb-8.0.1 on Debian 8.8 powerpc64

[Yao Qi]

On Wed, Sep 27, 2017 at 2:34 PM, Dennis Clarke <dclarke@blastwave.org> wrote:
>
> It is difficult to know if the entire gdb build should be tossed away or is
> this normal behavior ?
>

GDB tests are never FAIL free, so some test fails don't mean GDB is
completely broken.  However,
fails in these tests do means something is wrong.

-- 
Yao (齐尧)

Re: numerous tests fail in "make check" stage of gdb-8.0.1 on Debian 8.8 powerpc64

[Dennis Clarke]

On 09/27/2017 05:45 PM, Yao Qi wrote:
> On Wed, Sep 27, 2017 at 2:34 PM, Dennis Clarke <dclarke@blastwave.org> wrote:
>>
>> It is difficult to know if the entire gdb build should be tossed away or is
>> this normal behavior ?
>>
> 
> GDB tests are never FAIL free, so some test fails don't mean GDB is
> completely broken.  However,
> fails in these tests do means something is wrong.
> 

I am not sure what to make of that. It means "something is wrong" and
also "something is always wrong with gdb".

The test results look like so :

                 === gdb Summary ===

# of expected passes            33093
# of unexpected failures        96
# of expected failures          58
# of known failures             65
# of unresolved testcases       3
# of untested testcases         56
# of unsupported tests          206
/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb/testsuite/../../gdb/gdb 
version  8.0.1 -nw -nx -data-directory 
/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb/testsuite/../data-directory 


gmake[4]: *** [check-single] Error 1
gmake[4]: Leaving directory 
`/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb/testsuite'
gmake[3]: *** [check] Error 2
gmake[3]: Leaving directory 
`/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb/testsuite'
gmake[2]: *** [check] Error 2
gmake[2]: Leaving directory 
`/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb'
gmake[1]: *** [check-gdb] Error 2
gmake[1]: Leaving directory 
`/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001'
gmake: *** [do-check] Error 2

So there are 96 failures that were not expected. Also, the resultant gdb
binary seems to have found my libiconv and libexpat but not libz :

deb8_ppc64$ ldd ./gdb/gdb
         linux-vdso64.so.1 (0x00003fff7efe0000)
         libdl.so.2 => /lib64/libdl.so.2 (0x00003fff7efb0000)
         libexpat.so.1 => /usr/local/lib/libexpat.so.1 (0x00003fff7ef50000)
         libiconv.so.2 => /usr/local/lib/libiconv.so.2 (0x00003fff7ee30000)
         libm.so.6 => /lib64/libm.so.6 (0x00003fff7ed60000)
         libc.so.6 => /lib64/libc.so.6 (0x00003fff7eb90000)
         /lib64/ld64.so.1 (0x0000000051b20000)


deb8_ppc64$ ls -lo /usr/local/lib/libz*
-rw-r--r-- 1 root 333690 May 27 03:05 /usr/local/lib/libz.a
lrwxrwxrwx 1 root     14 May 27 03:05 /usr/local/lib/libz.so -> 
libz.so.1.2.11
lrwxrwxrwx 1 root     14 May 27 03:05 /usr/local/lib/libz.so.1 -> 
libz.so.1.2.11
-rwxr-xr-x 1 root 236688 May 27 03:05 /usr/local/lib/libz.so.1.2.11
deb8_ppc64$

Not sure if I can install this or not.

My whole reason for this is simply that gdb on the system won't work
with a 64-bit binary and I don't know why :

deb8_ppc64$ cat hello.c

#include <stdio.h>
#include <stdlib.h>
int main( int argc, char *argv[])
{
     fprintf ( stdout, "hello world.\n" );
     return (  EXIT_SUCCESS );
}

Compile it, run it and look at it :

Code:

deb8_ppc64$ gcc -m64 -g -o hello hello.c
deb8_ppc64$ ./hello
hello world.

deb8_ppc64$ file hello
hello: ELF 64-bit MSB executable, 64-bit PowerPC or cisco 7500, version 
1 (SYSV), dynamically linked, interpreter /lib64/ld64.so.1, for 
GNU/Linux 2.6.32, 
BuildID[sha1]=c79bcf90665edeb4b1d9a5972c4f7ddf8ec9877d, not stripped
deb8_ppc64$


deb8_ppc64$ which gdb
/usr/bin/gdb
deb8_ppc64$ ls -lap /usr/bin/gdb
-rwxr-xr-x 1 root root 6301688 Nov  9  2014 /usr/bin/gdb
deb8_ppc64$ /usr/bin/gdb hello
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/local/src/test/hello/hello": not in executable format: File format 
not recognized
(gdb) quit
deb8_ppc64$


So I decided to simply get the source and build a new gdb. Which may not
  work very well given the tests above.

Very difficult to tell what to do here.

Dennis