This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Disabling stack access for remote targets?
- From: Joakim Tjernlund <joakim dot tjernlund at transmode dot se>
- To: gdb at sourceware dot org
- Date: Fri, 1 Jun 2012 16:29:23 +0200
- Subject: Disabling stack access for remote targets?
Debugging u-boot/bios direcly from reset using remote gdb can be a challenge.
One reason is that gdb insists on reading stack contents each time it stops execution.
This can be devastating for a board that hasn't initialized RAM yet.
Would it be possible for a remote target to inform gdb not to touch the
stack? In its simplest form one could just test for sp == 0
Jocke