This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: MIPS32 gdb vectors question
Tim Michals wrote:
I'm looking into why MIPS32/GDB does not respond to GDB commands. Just
wanted to check to make sure the correct vector processing code is called,
hence, debug_vector is not called, but other_vector is.
Correct. That's because that's what the break command says it does :-).
The debug vector is only used by the debug single step exception, debug
interrupt exception, debug instruction break exception, debug software
breakpoint exception and debug data break exception.
Software break is only used with the SDBBP instruction. It's possible GDB
is putting that instruction in instead of "break 5" (opcode 0x005000d if
you want to check GDB memory writes with set debug remote 1), but that
seems highly unlikely as that would break so many things.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss