Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Marko Mlinar <markom@opencores.org>
To: Daniel Jacobowitz <drow@mvista.com>,
	David Carlton <carlton@math.stanford.edu>
Cc: gdb@sources.redhat.com
Subject: Re: PATCH for Re: mips-elf build fails
Date: Tue, 15 Oct 2002 03:40:00 -0000	[thread overview]
Message-ID: <200210151239.38777.markom@opencores.org> (raw)
In-Reply-To: <20021014204759.GA10876@nevyn.them.org>

> > 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.
>
> You're right.
>
> Marko, when you do something like this it is vital that you check
> existing definitions of the macro.  It's defined to an empty string in
> a number of header files, which is fine for #ifdef.  I've check this in
> to fix the build failures.

thanks for fixing it.

I have quite some TODO list with these kind of changes in order to put our 
target in. Since I do not want to cause more trouble I would like to ask 
somebody to help me with the global changes. Apparently you will have less 
work this way anyway :)

The next step should be:

-----
>> > #define STEP_SKIPS_DELAY_P (1)
>> > #define STEP_SKIPS_DELAY(pc) (or1k_step_skips_delay (pc))
> 
> what needs to be defined instead?

They need to be added to gdbarch.{sh,h,c}.  That's a separate change. 
See my post.  For this, look at one of the ``F:'' (predicate) methods - 
DO_REGISTERS_INFO.
-----

Any volounteers? :)

Marko


      parent reply	other threads:[~2002-10-15 10:40 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
     [not found]     ` <20021014204759.GA10876@nevyn.them.org>
2002-10-15  3:40       ` Marko Mlinar [this message]

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=200210151239.38777.markom@opencores.org \
    --to=markom@opencores.org \
    --cc=carlton@math.stanford.edu \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.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