This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH obv/pushed] MIPS ptrace build fixes
- From: Peter Schauer <peterschauer at gmx dot net>
- To: sergiodj at redhat dot com (Sergio Durigan Junior)
- Cc: palves at redhat dot com (Pedro Alves), simon dot marchi at ericsson dot com (Simon Marchi), gdb-patches at sourceware dot org, brendan dot kirby at imgtec dot com (Brendan Kirby)
- Date: Thu, 30 Jul 2015 11:13:46 +0200 (CEST)
- Subject: Re: [PATCH obv/pushed] MIPS ptrace build fixes
- Authentication-results: sourceware.org; auth=none
> On Wednesday, July 29 2015, Pedro Alves wrote:
>
> > On 07/29/2015 10:26 PM, Simon Marchi wrote:
> >> On 15-07-29 05:19 PM, Simon Marchi wrote:
> >>> FYI, I am pushing this as obvious.
> >>>
> >>> Since Pedro's ptrace cleanups, the MIPS buildbot compilation fails.
> >
> > In my defense, I did get a build fail email report, but it points at:
> >
> > http://gdb-build.sergiodj.net/builders/Debian-MIPS-m64/builds/77
> >
> > and looking at:
> >
> > http://gdb-build.sergiodj.net/builders/Debian-MIPS-m64/builds/77/steps/compile%20gdb/logs/stdio
> >
> > it shows the build had failed for an unrelated issue:
> >
> > tdep.Tpo ../../binutils-gdb/gdb/i386obsd-tdep.c
> > In file included from ../../binutils-gdb/gdb/common/common-defs.h:32:0,
> > from ../../binutils-gdb/gdb/defs.h:28,
> > from ../../binutils-gdb/gdb/i386obsd-tdep.c:20:
> > build-gnulib/import/stdlib.h:41:20: fatal error: /usr/lib/gcc/mips-linux-gnu/4.9/include/ctddef.h: No such file or directory
> > #include <stddef.h>
> > ^
This looks like a memory problem on the build slave, it seems that
memory flipped from 0x73 ('s') to 0x63 ('c').
> > compilation terminated.
> > The bug is not reproducible, so it is likely a hardware or OS problem.
> > make[2]: *** [i386obsd-tdep.o] Error 1
> > Makefile:1133: recipe for target 'i386obsd-tdep.o' failed
> >
> > So I just ignored it. Guess I was "lucky".
>
> FWIW, I've been noticing random errors in the MIPS buildslave. I even
> spotted an ICE once (I think Alan Modra reported it to me). Not sure if
> it is because of the load or something else.
So these might have been caused by memory problems too.
--
Peter Schauer Peter.Schauer@mytum.de