Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Greg Law <glaw@undo-software.com>, gdb@sourceware.org
Subject: Re: bfinish writes to random addresses.
Date: Wed, 26 Jul 2006 01:21:00 -0000	[thread overview]
Message-ID: <20060725184023.GA18796@nevyn.them.org> (raw)
In-Reply-To: <20303.82.92.89.47.1153851740.squirrel@webmail.xs4all.nl>

On Tue, Jul 25, 2006 at 08:22:20PM +0200, Mark Kettenis wrote:
> >  Daniel Jacobowitz wrote:
> >
> > > And there aren't very many hardware breakpoints, if any.
> >
> >  At least in the cases I've seen on x86, most of the time the hardware
> >  breakpoints aren't in use.  Of course, on other architectures there may
> >  be none, and on x86 they may all be used.  But my point was that if a
> >  hardware breakpoint is used if available, it would fix this at least in
> >  those cases.
> 
> If you can come up with some code that doesn't compicate matters too much
> and falls back on the software breakpoints if no hardware breakpoints are
> available, that might be a good idea.

Fortunately, we already need code to do this sort of thing - and it's
one of those issues that we (at CS) are going to be taking a look at
this year, time permitting.  This is just the reverse of trying to use
a software breakpoint when debugging ROM, and the same approach will
work.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-07-25 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 15:41 Greg Law
2006-07-25 15:42 ` Daniel Jacobowitz
2006-07-25 16:09   ` Greg Law
2006-07-25 16:20     ` Daniel Jacobowitz
2006-07-25 16:27       ` Greg Law
2006-07-25 16:53         ` Daniel Jacobowitz
2006-07-25 18:40         ` Mark Kettenis
2006-07-26  1:21           ` Daniel Jacobowitz [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=20060725184023.GA18796@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=glaw@undo-software.com \
    --cc=mark.kettenis@xs4all.nl \
    /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