Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: Fix sw watchpoint-out-of-scope events
Date: Tue, 18 Sep 2007 15:54:00 -0000	[thread overview]
Message-ID: <20070918155400.GA1128@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0709111642220.32532@perivale.mips.com>

On Tue, Sep 11, 2007 at 05:23:54PM +0100, Maciej W. Rozycki wrote:
>  This is a fix for software watchpoint-out-of-scope events for MIPS 
> platforms.  It implements a in_function_epilogue_p() hook which is used to 
> single-step a function's epilogue once a local watchpoint has been 
> destroyed (because of the restoration of the frame pointer).  As a result 
> the event is only reported once the caller has been reached back.

This patch is fine.  I wish it wasn't necessary, but for now it is.

> for the remote targets.  It does not fix them for Linux, because the o32 
> calling convention makes the restoration of the GOT pointer in the caller 
> ("lw gp,..." after "jalr") a part of the function call.  Therefore 
> execution stops in the right function, but one instruction too early, 
> still within the source line of the call.  It is still a step forward 
> though and less of nuisance for the user.

Hmm, do you think we should accept that line as a pass then?  The same
will happen on other architectures too.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-09-18 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 16:24 Maciej W. Rozycki
2007-09-18 15:54 ` Daniel Jacobowitz [this message]
2007-09-19 12:31   ` Maciej W. Rozycki
2007-09-19 12:38     ` Daniel Jacobowitz
2007-09-19 13:05       ` Maciej W. Rozycki
2007-09-19 13:16         ` 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=20070918155400.GA1128@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.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