public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Jon Beniston" <jbeniston@compxs.com>
To: <insight@sources.redhat.com>
Subject: h/w breakpoints
Date: Wed, 07 Jan 2004 18:03:00 -0000	[thread overview]
Message-ID: <004301c3d548$925c7400$06bda8c0@Kindrogan> (raw)

Hi,

I'm am trying to debug a remote target that only has h/w breakpoints
available (the code is in ROM). Is this known to be handled well by
Insight? Currently I have to set all breakpoints via the command line.
Looking at the remote debug output (set debug remote 1), I can see that
only Z0, X and M commands (all which write memory) are sent to the
target when I set a breakpoint via Insight. Should it not try Z1 as well
if all the previous fail? The fact that s/w breakpoints don't get set
has the nasty side effect of causing continue not to do anything without
reporting any error (removing all s/w breakpoints allows it to resume).
Another downside of using the hbreak command is that the breakpoints
don't appear in the GUI.

Now I could hack my debug target code to write a h/w breakpoint when
receiving a Z0, but feel that this should probably be handled better by
Insight. I'm willing to have a crack at modifying this if deemed
appropriate.

Cheers,
Jon




                 reply	other threads:[~2004-01-07 18:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='004301c3d548$925c7400$06bda8c0@Kindrogan' \
    --to=jbeniston@compxs.com \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).