This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
MIPS build slave
- From: Simon Marchi <simon dot marchi at polymtl dot ca>
- To: gdb-patches at sourceware dot org, Brendan Kirby <brendan dot kirby at imgtec dot com>
- Date: Sat, 18 Jul 2015 00:14:47 -0400
- Subject: MIPS build slave
- Authentication-results: sourceware.org; auth=none
Hi Brendan,
TLDR: I think most of the tests don't run properly on the MIPS build
slaves, check gdb.log for "Cannot exec".
Long version:
I am trying to clear an unexpected pass in mi-watch.exp (the test
expects gdb to fail, but it seems to work fine). git tells me the
xfail was added by commit 4a543da in 2007 and that it was added with
the MIPS platform in mind:
https://www.sourceware.org/ml/gdb-patches/2007-09/msg00151.html
I would therefore like to see if the test passes correctly on the MIPS
platform today before removing the xfail. Unfortunately, the test
doesn't run on the buildbot.
You can check the gdb.log here, search for mi-watch.exp (warning,
that's a very big file):
http://gdb-build.sergiodj.net/cgit/Debian-MIPS-m64/.git/plain/gdb.log
Here is the important snippet (with messed up formatting since I'm
using gmail, sorry):
220-exec-run
&"Cannot exec /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/outputs/gdb.mi/mi-watch/mi-watch
-c exec /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/outputs/gdb.mi/mi-watch/mi-watch
.\n"
&"Error: No such file or directory\n"
=thread-group-started,id="i1",pid="30605"
=thread-created,id="1",group-id="i1"
=thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1"
220^error,msg="During startup program exited with code 127."
(gdb)
ERROR: Unable to start target
There are many other tests that have the same problem, which is why I
suspect that the tests don't run as they should.
Simon