This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: GDB stubs / MIPS ISA I
- To: "Jurica Baricevic" <jura at INTESIS dot hr>
- Subject: Re: [ECOS] GDB stubs / MIPS ISA I
- From: Jesper Skov <jskov at redhat dot com>
- Date: 19 May 2000 14:23:27 +0200
- Cc: "Ecos" <ecos-discuss at sourceware dot cygnus dot com>
- References: <001101bfc17b$b3ef0ef0$6b00a8c0@jura>
>>>>> "Jurica" == Jurica Baricevic <jura@INTESIS.hr> writes:
Jurica> breakpoint. So, it seems that debugged program is always on
Jurica> the first breakpoint and it is not possible to step through
Jurica> the rest of the code.
Could be that caches are not handled properly, so when the stub tries
to single step it hits the existing breakpoint.
In mips-stub.c there are some commented out diag_printf statements
that can help you figure out what is going wrong.
Jurica> P.S. If you are interested in compatibility problems I found
Jurica> in '/mips/arch/...' I can say that they are related to not
Jurica> respecting the MIPS ISA I load delay slot.
[snip]
Jurica> What is the best way to avoid this kind of incompatibilities?
Something for Nick to reply to - but I suspect it's due to all the
existing MIPS variants introduce delays in hardware if the register
content is not ready when attempted used.
If you send a patch with MIPS I compatibility fixes, I'm sure they
would be accepted almost immediately.
Jesper