RE: x86 Hardware Breakpoints

RE: x86 Hardware Breakpoints

[Xinan Tang]

Hi

  If you implement the gdb remote stub on MPC855, what you need to do is
to support 'Z' packet in the remote stub. Please read appendix A of
"Debugging with GDB" for details.

Hope this helps

--Xinan

Tidal Networks


-----Original Message-----
From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com]
On Behalf Of Schneider, Jan (GE51)
Sent: Friday, October 22, 2004 7:55 AM
To: gdb@sources.redhat.com
Subject: x86 Hardware Breakpoints

I would like to implement Hardware Breakpoints for the MPC855.
For this I currently analyze the gdb, how it works with x86 processors.
Now I look for the straight place in the gdb sources, where it stops if
such
breakpoint is triggered
or rather where the gdb gets feedback of the processor that the
breakpoint
has slammed.

I hope that someone can point me some helpful information.

thanks
Jan

RE: x86 Hardware Breakpoints

[Dave Korn]

> -----Original Message-----
> From: gdb-owner On Behalf Of Schneider, Jan (GE51)
> Sent: 22 October 2004 15:55

> I would like to implement Hardware Breakpoints for the MPC855.
> For this I currently analyze the gdb, how it works with x86 
> processors.
> Now I look for the straight place in the gdb sources, where 
> it stops if such breakpoint is triggered
> or rather where the gdb gets feedback of the processor that 
> the breakpoint has slammed.
> 
> I hope that someone can point me some helpful information.

  You should read "info gdbint" and in particular the sections on breakpoints and
watchpoints in node "Algorithms".  Also available online at

http://sources.redhat.com/gdb/current/onlinedocs/gdbint_3.html#SEC6

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

x86 Hardware Breakpoints

[Schneider, Jan (GE51)]

I would like to implement Hardware Breakpoints for the MPC855.
For this I currently analyze the gdb, how it works with x86 processors.
Now I look for the straight place in the gdb sources, where it stops if such
breakpoint is triggered
or rather where the gdb gets feedback of the processor that the breakpoint
has slammed.

I hope that someone can point me some helpful information.

thanks
Jan