Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, Chris Dearman <chris@mips.com>,
	     "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: Adjust breakpoints in branch delay slots
Date: Fri, 25 May 2007 13:16:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0705251415210.13913@perivale.mips.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0705251217190.13913@perivale.mips.com>

On Fri, 25 May 2007, Maciej W. Rozycki wrote:

>  In principle on bare iron it should be doable, but the problem is, IIRC, 
> the state of cp0.cause.bd is not propagated under Linux to userland in any 
> way.  And at the moment I'm not sure how this would affect EJTAG debugging 
> either.

 FYI, I have now checked Linux and it should be fine -- must have been my
bad memory.  EJTAG has provisions for handling this correctly
(cp0.debug.dbd), but I'm not sure if associated software gets it right.

  Maciej


  parent reply	other threads:[~2007-05-25 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 18:08 Maciej W. Rozycki
2007-05-24 18:21 ` Mark Kettenis
2007-05-24 18:31 ` Daniel Jacobowitz
     [not found]   ` <Pine.LNX.4.61.0705251217190.13913@perivale.mips.com>
2007-05-25 12:50     ` Maciej W. Rozycki
2007-05-25 13:16     ` Maciej W. Rozycki [this message]
     [not found]     ` <Pine.LNX.4.61.0705251318500.13913@perivale.mips.com>
2007-05-25 13:19       ` Daniel Jacobowitz
2007-06-15 14:38         ` Maciej W. Rozycki
2007-05-25 13:21   ` Maciej W. Rozycki
2007-05-25 13:26     ` Daniel Jacobowitz

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=Pine.LNX.4.61.0705251415210.13913@perivale.mips.com \
    --to=macro@mips.com \
    --cc=chris@mips.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.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