MIPS remote debugging support (Was: Re: [kaffe] mipsel SIGSEGV)
Mark and Janice Juszczec
juszczec at hotmail.com
Tue Dec 9 08:57:02 PST 2003
Dalibor and all
Greetings from frosty NE Ohio.
>>Its odd that the html doc you reference says I should be able to do:
>>target r3900 <dev> to use "Densan DVE-R3900 ROM monitor for Toshiba R3900
>>because when I do help targets from gdb (configured with
>>--target=mips-idt-ecoff) r3900 is not in the list.
>That sounds like a good question for the gdb mailing list ;)
Consider it on its way.
>>>the other choice may be to use the gdbserver program on the mipsel
>>I tried this. After stripping, gdbserver is too big to put on the Helio
>>with kaffe, rt.jar, the kernel, etc.
I might have enough space. I'm getting some decompression error messages
from the kernel at boot time. It could be my kernel isn't accessing all
available memory. I'll throw du on and see how much space it says it has.
>I guess there are two more possibilities:
>a) using kgdb to debug the kernel. Probably quite slow, if it works at all.
>You need a kernel that's compiled with kgdb support.
Do you mean track back to kaffe from where the kernel generates the SIGSEGV?
>b) Adding support for gdb stubs for mips to kaffe. There is a mips-stub.c
>in the linux kernel sources  and there is some documentation on using
>remote stubs .
We are thinking alike ;-) This is the next step in my plan. Over the
weekend, I dug out mips-stub.c (ok, in my kernel source its called
gdb-stub.c). I've been researching what gdb required stuff is present, is
missing and so on.
Do any of the kaffe mips users have mipsel appropriate debugging stubs lying
around. that I can look at? I can't believe I'm the first guy to do this.
Cell phone switch rules are taking effect find out more here.
More information about the kaffe