Linker and stub problems on sh2
William A. Gatliff
Mon May 20 08:00:00 GMT 2002
On Mon, May 20, 2002 at 01:03:32PM +0200, email@example.com wrote:
> Last thing, I added to gdbstub a serial interrupt check, which work
> quietly fine, exept that sometime, the interrupt exception will
> scramble the code at the address where the exception happened I
> understood that this is due to the fact that the value of the
> gdb2_stepped_opcode is non zero after a cont command to the gdb.
Hmmm... yep, looks like I left out the code to zero out the .bss
section. Your crt0 will want to do this, to make sure
gdb_sh2_stepped_opcode is zero at startup. Otherwise, the value in
gdb_sh2_stepped_opcode is essentially random, so you'll get
unpredictable results the next time you do a stepi because you'll run
a random opcode.
If you are linking in a stub with your application, then you could
zero out gdb_sh2_stepped_opcode in your .gdbinit file, to save you
some work until you had your other crt0 problems worked out.
> Sorry for the poor english.
Your english is fine. :^)
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to firstname.lastname@example.org
More information about the crossgcc