From: Jay Monkman <jtm@smoothsmoothie.com>
To: Mark Beckwith <mark@intrig.com>
Cc: Jay Monkman <jtm-list-gdb@smoothsmoothie.com>, gdb@sources.redhat.com
Subject: Re: bdi2000 and gdb (newbie question)
Date: Wed, 01 Sep 2004 18:53:00 -0000 [thread overview]
Message-ID: <20040901185741.GD9529@smoothsmoothie.com> (raw)
In-Reply-To: <20040901161829.GI14091@john.intrig.com>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Wed, Sep 01, 2004 at 11:18:29AM -0500, Mark Beckwith wrote:
> error when I do the "target remote" command. Would this be possible? If
> so I would like to volunteer.
That might be a limitation with the remote protocol. I don't think
there's any info in it declaring the architecture type.
> So I'm debugging just fine now out of ram. However, when I set BREAKMODE
> HARD and try to step through flash, only one breakpoint gets hit, and then
> can't step or set another. The documentation I've read states that the
> breakpoint will be cleared once it is hit, but that doesn't seem to be
What documentation? I've never seen it remove the breakpoint
permanently unless I delete it.
> happening. Also the delete command doesn't seem to clear the hardware
> breakpoint. I have to do a "ci" all the time from the bdi. Any
> suggestions on working with hardware breakpoints?
Did you insert the breakpoint with gdb?
If you are running from RAM, you will probably have better success if
you use soft breakpoints.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-01 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 20:57 Mark Beckwith
2004-08-26 21:06 ` Daniel Jacobowitz
2004-08-26 22:12 ` Jay Monkman
2004-08-27 16:24 ` Mark Beckwith
2004-08-27 17:49 ` Jay Monkman
2004-09-01 16:18 ` Mark Beckwith
2004-09-01 18:53 ` Jay Monkman [this message]
2004-09-01 21:00 ` Mark Beckwith
2004-08-27 6:59 ` Fabian Cenedese
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=20040901185741.GD9529@smoothsmoothie.com \
--to=jtm@smoothsmoothie.com \
--cc=gdb@sources.redhat.com \
--cc=jtm-list-gdb@smoothsmoothie.com \
--cc=mark@intrig.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