From: jtc@redback.com (J.T. Conklin)
To: markom@opencores.org
Cc: gdb@sources.redhat.com
Subject: Re: HW breakpoints, watchpoints and trace
Date: Thu, 17 May 2001 10:31:00 -0000 [thread overview]
Message-ID: <5mheyjubks.fsf@jtc.redback.com> (raw)
In-Reply-To: <3B022218.5A59D75F@opencores.org>
>>>>> "Marko" == Marko Mlinar <markom@opencores.org> writes:
Marko> I have a question: Our processor (or1k) has a lot of HW
Marko> debugging capabilities and I was wondering what would be the
Marko> best solution to include them into user interface.
Marko> e.g.: We can create HW watchpoint as
Marko> "watchpoint_event" = $1234 == 506 && ( $50 > 70 && $50 <= 120
Marko> || !write_to_address_occured (4567))
Marko> (Sorry about this freaky pseudo code, but I hope you get my
Marko> point)
Actually, I'm a bit confused.
Marko> We could surely add special command which would support such
Marko> functionality, but I would like to have this functionality
Marko> detected automaticaly using break or hbreak.
Note that GDB already supports hardware watchpoints on several
targets. See the watch, awatch, and rwatch commands for details.
The low-level guts of GDB only supports read, write, or access watch-
points on memory locations, but the high level CLI takes expressions.
So with "watch foo > 3", GDB would get an event when "foo" is changed,
and then it would evaluate "foo > 3".
From your above pseudo code, it appears that the or1k processor might
be able to evaluate the entire expression. GDB has no support for such
a thing. I suggest getting basic hardware watchpoints working before
taking on such a project.
--jtc
--
J.T. Conklin
RedBack Networks
prev parent reply other threads:[~2001-05-17 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 23:42 Marko Mlinar
2001-05-17 10:31 ` J.T. Conklin [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=5mheyjubks.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=gdb@sources.redhat.com \
--cc=markom@opencores.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