This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: Breakpoints
- To: "davidwilliams at ozemail dot com dot au" <davidwilliams at ozemail dot com dot au>
- Subject: Re: Breakpoints
- From: jtc at redback dot com (J.T. Conklin)
- Date: 22 Dec 1999 15:49:47 -0800
- Cc: "'gdb mail list'" <gdb at sourceware dot cygnus dot com>
- References: <01BF4C88.F6D54B20.davidwilliams@ozemail.com.au>
- Reply-To: jtc at redback dot com
>>>>> "David" == David Williams <davidwilliams@ozemail.com.au> writes:
David> Hi all, Does GDB ever need to set more than one breakpoint when
David> stepping through source code? I have not (as yet) seen this
David> type of behaviour.
I don't know. It would be useful if GDB only needed one breakpoint.
Yours is not the only target with a single hardware breakpoint.
David> I have a stub that supports breakpoints in flash via hardware
David> facility but it can set only one breakpoint. If GDB requires
David> more than one at time then I am in trouble. My target is
David> 68EZ328 (68000 core, not CPU32, no BDM, has its own peculiar
David> emulation mode). My stub currently looks for attempts to write
David> trap #1 op-codes to program memory (FLASH) and then instead of
David> writing to program memory it sets a hardware breakpoint at the
David> address (thanks Stan for the suggestion).
It might be useful to support the remote protocol's 'Z'/'z' breakpoint
commands. This eliminates the possibility that a memory write will be
confused with breakpoint insertion.
--jtc
--
J.T. Conklin
RedBack Networks