Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC/RFA/i386] pb reading insns if breakpoints still inserted
Date: Sat, 29 Apr 2006 15:06:00 -0000	[thread overview]
Message-ID: <20060429150556.GA21836@nevyn.them.org> (raw)
In-Reply-To: <u8xpofn9r.fsf@gnu.org>

On Sat, Apr 29, 2006 at 05:51:28PM +0300, Eli Zaretskii wrote:
> > Now, you could make a reasonable argument that the default when reading
> > memory ought to be to ignore breakpoints.  But that would be a much
> > harder change to test; we'd need to catch all the places which do need
> > to see breakpoints
> 
> We don't need to catch all of them at once, if that's hard.  We can
> catch them one by one and fix them as we do.

Well, this one's been there for years.  I'd rather have slightly more
confidence that we won't introduce a whole new set of such bugs...

> > I can only think of one off the top of my head, but I'm sure there
> > are more.  So, I would suggest making it separately.
> 
> It's fine with me, but I still don't understand why it has to be in an
> architecture-specific file, not in some more general place.  Am I
> missing something?

Right now, there are many ways to read memory; two of them skip
inserted breakpoints, and the others don't.  So, to fix this sort of
problem, you have to deliberately use the functions which do skip
breakpoints.  Thus the change has to be at the site of the memory
read, which is in this case in a target-specific file.  We don't want
to remove breakpoints before invoking the prologue analyzer; the
removal may be unnecessary if a "step" command is in progress and not
done yet.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-29 15:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 17:12 Joel Brobecker
2006-04-28 17:54 ` Jim Blandy
2006-04-28 18:40   ` Mark Kettenis
2006-04-28 18:48     ` Joel Brobecker
2006-04-28 20:58     ` Jim Blandy
2006-04-28 21:09       ` Mark Kettenis
2006-04-28 21:13         ` Daniel Jacobowitz
2006-04-28 21:42           ` Jim Blandy
2006-04-28 21:54             ` Joel Brobecker
2006-04-28 21:49           ` Joel Brobecker
2006-04-28 22:00             ` Jim Blandy
2006-04-29 14:20 ` Eli Zaretskii
2006-04-29 14:28   ` Daniel Jacobowitz
2006-04-29 14:51     ` Eli Zaretskii
2006-04-29 15:06       ` Daniel Jacobowitz [this message]
2006-04-29 16:57         ` Eli Zaretskii
2006-04-29 23:14           ` Daniel Jacobowitz
2006-05-01 16:36 ` Mark Kettenis
2006-05-01 17:06   ` Joel Brobecker
2006-05-05 18: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=20060429150556.GA21836@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.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