potential insight-gdb problem with settings hardware breakpoints or just missing feature

potential insight-gdb problem with settings hardware breakpoints or just missing feature

[Nenad Lazovic]

I am using arm-elf-gdb or arm-elf-insight together with OCDLibRemote is a
utility from
www.macraigor.comto debug ARM7 (Philips LPC2106).
I am having a problem setting hardware breakpoints. Following is the typical
session:

(gdb) target remote localhost:2000
Remote debugging using localhost:2000
_start () at ../../../arm_ucos/lpc210x/src/gcc/init.S:83
83              b ResetHandler

(gdb) info breakpoints
Num Type           Disp Enb Address    What
1   hw breakpoint  keep y   0x00000138
../../../arm_ucos/lpc210x/src/gcc/init.S:175

(gdb) delete
Delete all breakpoints? (y or n) y

(gdb) hbreak 175

Hardware assisted breakpoint 2 at 0x138: file
../../../arm_ucos/lpc210x/src/gcc/init.S, line 175.

(gdb) info breakpoints
Num Type           Disp Enb Address    What
2   hw breakpoint  keep y   0x00000138
../../../arm_ucos/lpc210x/src/gcc/init.S:175

(gdb) n
Warning:
Cannot insert hardware breakpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

(gdb) s
Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint) packet

(gdb) n
Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint) packet

(gdb) c
Continuing.
Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint) packet

Am I missing something ?
Are hardware breakpoints supported ? If not, any plans ?

Thanks,

Nenad

Re: potential insight-gdb problem with settings hardware breakpoints or just missing feature

[Keith Seitz]

On Tue, 2004-04-13 at 21:38, Nenad Lazovic wrote:
> (gdb) s
> Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint) packet

This sounds like the target stub/debug agent on your board does not
support gdb's Z1 packet, which is apparently needed to set hardware
breakpoints.

I recommend two things: 1) contact Macraigor Systems and ask them if
hardware breakpoints is supported in OCDLibRemote; 2) ask on the gdb
list where people who know about this stuff hang out.

This mailing list deals with just the UI (insight), and is ill-equipped
to deal with backend issues like this.

Keith

Re: potential insight-gdb problem with settings hardware breakpoints or just missing feature

[Peter Reilley]

Hello Nenad;

Only software breakpoints are supported using Z packets in OCDLibRemote
However there is a way to use the hardware breakpoints.   Use the
"monitor set hbreak <addr>" command.   The "monitor" commands are
a passthru mechanism that talks directly to OCDLibRemote.   You can
get a list of all the available monitor commands by typing "monitor help".

There is only one hardware breakpoint available with the hbreak command.
The other hardware breakpoint is used by OCDLibRemote to implement
software breakpoints.   This is necessary for architectural reasons.

Hope that this helps;
Pete.

----- Original Message ----- 
From: "Nenad Lazovic" <nlazovic@sympatico.ca>
To: <insight@sources.redhat.com>
Sent: Wednesday, April 14, 2004 12:38 AM
Subject: potential insight-gdb problem with settings hardware breakpoints or
just missing feature


> I am using arm-elf-gdb or arm-elf-insight together with OCDLibRemote is a
> utility from
> www.macraigor.comto debug ARM7 (Philips LPC2106).
> I am having a problem setting hardware breakpoints. Following is the
typical
> session:
>
> (gdb) target remote localhost:2000
> Remote debugging using localhost:2000
> _start () at ../../../arm_ucos/lpc210x/src/gcc/init.S:83
> 83              b ResetHandler
>
> (gdb) info breakpoints
> Num Type           Disp Enb Address    What
> 1   hw breakpoint  keep y   0x00000138
> ../../../arm_ucos/lpc210x/src/gcc/init.S:175
>
> (gdb) delete
> Delete all breakpoints? (y or n) y
>
> (gdb) hbreak 175
>
> Hardware assisted breakpoint 2 at 0x138: file
> ../../../arm_ucos/lpc210x/src/gcc/init.S, line 175.
>
> (gdb) info breakpoints
> Num Type           Disp Enb Address    What
> 2   hw breakpoint  keep y   0x00000138
> ../../../arm_ucos/lpc210x/src/gcc/init.S:175
>
> (gdb) n
> Warning:
> Cannot insert hardware breakpoint 2.
> Could not insert hardware breakpoints:
> You may have requested too many hardware breakpoints/watchpoints.
>
> (gdb) s
> Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint)
packet
>
> (gdb) n
> Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint)
packet
>
> (gdb) c
> Continuing.
> Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint)
packet
>
> Am I missing something ?
> Are hardware breakpoints supported ? If not, any plans ?
>
> Thanks,
>
> Nenad
>
>

RE: potential insight-gdb problem with settings hardware breakpoints or just missing feature

[Nenad Lazovic]

help for sure.
thanks
Nenad


-----Original Message-----
From: insight-owner@sources.redhat.com
[mailto:insight-owner@sources.redhat.com]On Behalf Of Peter Reilley
Sent: Wednesday, April 14, 2004 2:40 PM
To: insight@sources.redhat.com; Nenad Lazovic
Cc: Jim MacGregor
Subject: Re: potential insight-gdb problem with settings hardware
breakpoints or just missing feature


Hello Nenad;

Only software breakpoints are supported using Z packets in OCDLibRemote
However there is a way to use the hardware breakpoints.   Use the
"monitor set hbreak <addr>" command.   The "monitor" commands are
a passthru mechanism that talks directly to OCDLibRemote.   You can
get a list of all the available monitor commands by typing "monitor help".

There is only one hardware breakpoint available with the hbreak command.
The other hardware breakpoint is used by OCDLibRemote to implement
software breakpoints.   This is necessary for architectural reasons.

Hope that this helps;
Pete.

----- Original Message -----
From: "Nenad Lazovic" <nlazovic@sympatico.ca>
To: <insight@sources.redhat.com>
Sent: Wednesday, April 14, 2004 12:38 AM
Subject: potential insight-gdb problem with settings hardware breakpoints or
just missing feature


> I am using arm-elf-gdb or arm-elf-insight together with OCDLibRemote is a
> utility from
> www.macraigor.comto debug ARM7 (Philips LPC2106).
> I am having a problem setting hardware breakpoints. Following is the
typical
> session:
>
> (gdb) target remote localhost:2000
> Remote debugging using localhost:2000
> _start () at ../../../arm_ucos/lpc210x/src/gcc/init.S:83
> 83              b ResetHandler
>
> (gdb) info breakpoints
> Num Type           Disp Enb Address    What
> 1   hw breakpoint  keep y   0x00000138
> ../../../arm_ucos/lpc210x/src/gcc/init.S:175
>
> (gdb) delete
> Delete all breakpoints? (y or n) y
>
> (gdb) hbreak 175
>
> Hardware assisted breakpoint 2 at 0x138: file
> ../../../arm_ucos/lpc210x/src/gcc/init.S, line 175.
>
> (gdb) info breakpoints
> Num Type           Disp Enb Address    What
> 2   hw breakpoint  keep y   0x00000138
> ../../../arm_ucos/lpc210x/src/gcc/init.S:175
>
> (gdb) n
> Warning:
> Cannot insert hardware breakpoint 2.
> Could not insert hardware breakpoints:
> You may have requested too many hardware breakpoints/watchpoints.
>
> (gdb) s
> Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint)
packet
>
> (gdb) n
> Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint)
packet
>
> (gdb) c
> Continuing.
> Can't set hardware breakpoint without the 'Z1' (hardware-breakpoint)
packet
>
> Am I missing something ?
> Are hardware breakpoints supported ? If not, any plans ?
>
> Thanks,
>
> Nenad
>
>