Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Hardware breakpoints / watchpoints
@ 2004-01-06 13:36 Jon Beniston
  0 siblings, 0 replies; 2+ messages in thread
From: Jon Beniston @ 2004-01-06 13:36 UTC (permalink / raw)
  To: gdb

Hi,

Can anyone please shed a little more info on the current status of h/w
breakpoints and watchpoints? How do they fit in with multi arch targets?
Is there a standard interface for setting them in a simulator?

Cheers,
JonB




^ permalink raw reply	[flat|nested] 2+ messages in thread
* Re: Hardware breakpoints / watchpoints
@ 2004-01-06 14:07 Ramana Radhakrishnan
  0 siblings, 0 replies; 2+ messages in thread
From: Ramana Radhakrishnan @ 2004-01-06 14:07 UTC (permalink / raw)
  To: jbeniston; +Cc: gdb


Thus spake Jon Beniston
> Hi,
>
> Can anyone please shed a little more info on the current status of h/w
> breakpoints and watchpoints? How do they fit in with multi arch targets?
There are target methods for operating on hardware breakpoints / watchpoints.

target.to_insert_hw_break(watch)point . So depending on the target
specification the implementation is present.
A case in study would be procf implementations of hw breakpoints /
watchpoints with procfs . look at nto-procfs.c for the QNX Neutrino as a
case study of stuff.

You can also look at remote_insert_hw_breakpoint in remote.c . The
simulator must also have such an interface since the simulator is one more
target for gdb.

cheers
Ramana










> Is there a standard interface for setting them in a simulator?
>
> Cheers,
> JonB
>
>
>


----
Ramana Radhakrishnan
Codito Technologies


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-01-06 14:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-06 13:36 Hardware breakpoints / watchpoints Jon Beniston
2004-01-06 14:07 Ramana Radhakrishnan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox