This is the mail archive of the
mailing list for the GDB project.
Re: handle hardware breakpoints in overlays
- To: Michael Snyder <msnyder at cygnus dot com>
- Subject: Re: handle hardware breakpoints in overlays
- From: jtc at redback dot com (J.T. Conklin)
- Date: 05 Oct 1999 16:43:21 -0700
- Cc: gdb-patches at sourceware dot cygnus dot com
- References: <firstname.lastname@example.org> <37FA85E7.D8C@cygnus.com>
- Reply-To: jtc at redback dot com
>>>>> "Michael" == Michael Snyder <email@example.com> writes:
Michael> No, but if you think about the way overlays work
Michael> (or can be expected to work in at least some implementations),
Michael> the code is going to be copied from the LMA address to the
Michael> VMA address by some software agent, without the debugger's
Michael> knowledge or participation.
I assumed that GDB had to be notified on every overlay switch, since
the overlay sections may not be in the address space of the processor
(it might be loaded from some external device, etc). If this is not
the case, I think we can put this patch on the back burner, since hw
breakpoints will not be inserted and/or removed as overlays are
Is there any mechanism for the overlay manager and GDB to cooperate?
Without it, I can't see how overlay breakpoints can work unless the
LMA is in writable physical memory.