This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Breakpoints
- To: "'gdb mail list'" <gdb at sourceware dot cygnus dot com>
- Subject: Breakpoints
- From: David Williams <davidwilliams at ozemail dot com dot au>
- Date: Wed, 22 Dec 1999 14:29:31 +1100
- Organization: DLC software P/L
- Reply-To: "davidwilliams at ozemail dot com dot au" <davidwilliams at ozemail dot com dot au>
Hi all,
Does GDB ever need to set more than one breakpoint when stepping through
source code? I have not (as yet) seen this type of behaviour.
I have a stub that supports breakpoints in flash via hardware facility but
it can set only one breakpoint. If GDB requires more than one at time then
I am in trouble. My target is 68EZ328 (68000 core, not CPU32, no BDM, has
its own peculiar emulation mode). My stub currently looks for attempts to
write trap #1 op-codes to program memory (FLASH) and then instead of
writing to program memory it sets a hardware breakpoint at the address
(thanks Stan for the suggestion).
TIA
David Williams