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?
- From: Jesper Skov <jskov at redhat dot com>
- To: Grant Edwards <grante at visi dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: 22 Nov 2001 10:19:15 +0100
- Subject: Re: [ECOS] Gdb stubs debugging an a-priori executable?
- References: <48256B0B.0075AEC8.00@TWALINS3>
>>>>> "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.
Jesper