using gdb/kgdb

[Charles Krinke]

> 
At this point, try setting the architecture as below (you can
show the current architecture first, to check that it is
wrongly set to "e500", which doesn't work properly)

(gdb) show architecture
The target architecture is set automatically (currently powerpc:e500)

(gdb) set architecture powerpc:common
The target architecture is assumed to be powerpc:common

> (gdb)target remote /dev/ttyUSB0
> ...

More explanation can be found here:
http://www.ultsol.com/faq_p311.htm
[I would prefer to reference an explanation on this
mailing list, but I did not find one.]

I hope this solves your problem.

Clive

Dear Clive:

I appreciate your kind comment, but I think I have already accommodate
this by using the latest gdb and cross-compiling it and it starts up in
architecture powerpc:common.

There must be something else going awry here and I wonder what other
things might cause the pc to be unreadable and uncontrollable from gdb.

Charles