Disabling stack access for remote targets?

Joakim Tjernlund joakim.tjernlund@transmode.se
Fri Jun 1 14:29:00 GMT 2012


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



More information about the Gdb mailing list