From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb <gdb@sources.redhat.com>, Marko Mlinar <markom@opencores.org>
Subject: Re: mips-elf build fails
Date: Mon, 14 Oct 2002 11:24:00 -0000 [thread overview]
Message-ID: <ro165w4ho9p.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20021014181651.GA12139@nevyn.them.org>
On Mon, 14 Oct 2002 14:16:51 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> On Mon, Oct 14, 2002 at 11:00:12AM -0700, David Carlton wrote:
>> My all-targets build over the weekend failed on mips-elf. I'm
>> including the error messages below.
>> This isn't on clean CVS sources, but I haven't modified infrun.c or
>> anything mips-elf specific on the sources that I'm using for this
>> build. All the other targets work.
> That's STOPPED_BY_WATCHPOINT. The definition hasn't changed in
> months....
Well, to be specific, the line is
if (HAVE_NONSTEPPABLE_WATCHPOINT && STOPPED_BY_WATCHPOINT (ecs->ws))
So it seems reasonable to assume that it's some sort of interation
between mips-elf and these patches:
2002-10-10 Marko Mlinar <markom@opencores.org>
* infrun.c (resume): Convert #ifdef HAVE_NONSTEPPABLE_WATCHPOINT into C,
accidentially not commited 2002-10-09
* gdbarch.h, gdbarch.c: Re-generate.
2002-10-09 Marko Mlinar <markom@opencores.org>
* infrun.c (resume): Convert #ifdef HAVE_NONSTEPPABLE_WATCHPOINT into C.
* gdbarch.sh (HAVE_NONSTEPPABLE_WATCHPOINT): Add.
* gdbarch.h, gdbarch.c: Re-generate.
In other words, I think it's HAVE_NONSTEPPABLE_WATCHPOINT rather than
STOPPED_BY_WATCHPOINT that's the problem.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-10-14 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 11:00 David Carlton
2002-10-14 11:16 ` Daniel Jacobowitz
2002-10-14 11:24 ` David Carlton [this message]
[not found] ` <20021014204759.GA10876@nevyn.them.org>
2002-10-15 3:40 ` PATCH for " Marko Mlinar
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=ro165w4ho9p.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=markom@opencores.org \
/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