This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Gdb stubs debugging an a-priori executable?
On Fri, 2001-11-23 at 03:08, Grant Edwards wrote:
> On Thu, Nov 22, 2001 at 10:19:15AM +0100, Jesper Skov wrote:
> > >>>>> "Grant" == Grant Edwards <grante@visi.com> writes:
> >
> > Grant> So the question is: why does loading data to the first 48 bytes
> > Grant> in RAM break the gdb stubs? It's an ARM7 platform, in case
> > Grant> that matters. Do the gdb stubs expect the interrupt vectors to
> > Grant> be in a certain state?
> >
> > Because RedBoot enters GDB mode hitting a berakpoint - and you just
> > changed the vector to point at your program's entry address by
> > overloading the bottom of RAM.
>
> I see. Breakpoints are done via SW interrupt?
No, undefined instructions.
Jesper