Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Brendan Kirby <brendan.kirby@imgtec.com>
To: Pedro Alves <palves@redhat.com>, Peter Schauer <peterschauer@gmx.net>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
	Simon Marchi	<simon.marchi@ericsson.com>,
	<gdb-patches@sourceware.org>,
	Matthew Fortune	<Matthew.Fortune@imgtec.com>,
	"Maciej W. Rozycki"	<maciej.rozycki@imgtec.com>,
	Rich Fuhler <rich.fuhler@imgtec.com>
Subject: Re: [PATCH obv/pushed] MIPS ptrace build fixes
Date: Mon, 24 Aug 2015 17:52:00 -0000	[thread overview]
Message-ID: <55DB59BD.6030304@imgtec.com> (raw)
In-Reply-To: <55DB3236.4090400@redhat.com>

On 08/24/2015 08:03 AM, Pedro Alves wrote:
> On 08/24/2015 03:59 PM, Peter Schauer wrote:
>
>>>> This looks like a memory problem on the build slave, it seems that
>>>> memory flipped from 0x73 ('s') to 0x63 ('c').
>>> OOC, how did you figure this out?
>> From these lines:
>>
>> 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>
>>                      ^
>>
>> gcc lists the correct source include (stddef.h), but then complains
>> about not finding ctddef.h, so it looks like memory flipped somewhere
>> between (or while) reading the include file name and then trying to
>> access the include file.
>>
> Aaaah.  Nice catch.
>
> Brendan, is anyone looking at sorting this out?
I'm not aware of anyone working on this.  I'm CC'ing a few people who
might be.  If it turns out to be a hardware problem, then I can move it
to another Edge Router Pro.   But, I don't have anything other than Edge
Router Pro boards to put it on.

Brendan


  reply	other threads:[~2015-08-24 17:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 21:19 Simon Marchi
2015-07-29 21:26 ` Simon Marchi
2015-07-29 21:59   ` Pedro Alves
2015-07-29 22:32     ` Sergio Durigan Junior
2015-07-30  9:14       ` Peter Schauer
2015-08-24 14:48         ` Pedro Alves
2015-08-24 14:59           ` Peter Schauer
2015-08-24 15:03             ` Pedro Alves
2015-08-24 17:52               ` Brendan Kirby [this message]
2015-08-24 18:04                 ` Pedro Alves
2015-08-24 18:10                   ` Sergio Durigan Junior
2015-08-24 18:17                     ` Pedro Alves
2015-08-24 18:20                       ` Sergio Durigan Junior
2015-08-24 18:24                         ` Sergio Durigan Junior
2015-08-24 18:30                           ` Brendan Kirby
2015-08-24 18:05                 ` Sergio Durigan Junior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55DB59BD.6030304@imgtec.com \
    --to=brendan.kirby@imgtec.com \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=gdb-patches@sourceware.org \
    --cc=maciej.rozycki@imgtec.com \
    --cc=palves@redhat.com \
    --cc=peterschauer@gmx.net \
    --cc=rich.fuhler@imgtec.com \
    --cc=sergiodj@redhat.com \
    --cc=simon.marchi@ericsson.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox