On Wed, 14 May 2003, Andrew Cagney wrote:

:) Theodore,
:)
:) Just noticed that the AVR target doesn't provide the BREAKPOINT_FROM_PC
:) method.
:)
:) Up until now the architecture vector providing a default
:) breakpoint_from_pc (it would internal error for the AVR case). I
:) suspect, up until now, this hasn't been a problem because the AVR was
:) always remote.
:)
:) Anyway, I've just posted a patch to always require breakpoint-from-pc
:) and this is causing the AVR grief.
:)
:) So, is there a breakpoint instruction, or should GDB allow targets that
:) have no breakpoint at all?

Ok, I added the BREAKPOINT_FROM_PC method for the avr and as I
suspected it doesn't interfere with remote targets (unless I am over
looking something):

(gdb) b main
Breakpoint 1 at 0x104: file tst.c, line 34.
(gdb) c
Continuing.
Sending packet: $Z0,104,2#a9...Ack
Packet received: OK
Packet Z0 (software-breakpoint) is supported
Sending packet: $Hc0#db...Ack
Packet received:
Sending packet: $c#63...Ack
Packet received: T0520:02;21:ff10;22:04010000;
Sending packet: $g#67...Ack
Packet received: 00000000000000000000000000000000000100000000000000000001ff100a0102ff1004010000
Sending packet: $mfc,8#9a...Ack
Packet received: cfefd0e1debfcdbf
Sending packet: $z0,104,2#c9...Ack
Packet received: OK

Breakpoint 1, main () at tst.c:34
(gdb)


Andrew, does the attached patch help things with your patch? If so,
I'll go ahead and commit it.

Ted Roth

(Wondering if I should have posted this to gdb-patches instead. ;-)