Sync ma wrote:
> gdb wonder the value of register 37? there only 32
general purpose
> regs in my 4KEc cpu.
I used to read some GDB source code related to MIPS
arch(ISA). In some MIPS
archs, Reg.37 means PC register. But I have no idea which
arch(target) in
"config.sub" your 4KEC belong to. I think the
target dependent file
"mips-tdep.c/h" can give you some clue.
> Anyway, there should be some handler function in
gdbserver for command
> 'p', but I have not found in gdb-6.5 yet.
Maybe you can find it in "remote.c". 'p' is not a
command, it is a RSP packet.
> Someone guide me.( Lots question about remote
debugging(debugging with
> BDIGDB), eg. 'stepi' makes no stop, I could only return
to GDB CLI
> with 'CTRL+C', A japanese engineer wrote in another
maillist says that
> some instruction sets may not support tracing... I
found a manual for
> U-boot debugging with BDI2000, but it can not be
reproduced on my MIPS
> processor).
It depends on archs. If GDB (compiled for your target)
support SW single
stepping, you can achieve "stepi", or you can
implement SW single stepping in
your STUB. I have never used "tracing" related
command before, so I don't know
if gdb can. What GDB can do depends on how much RSP packets
you implement in
your STUB and how much functions registered to GDB in target
dependent files. So
concentrate in what you can do, let others go. It is very
hard for remote
debugging achieve the same goal as debugging on host.
Regards,
Wenbo
--
Wenbo Yang
The State Key Lab. of Information Security
Graduate School of CAS, 19A Yuquan Road, Beijing, China
Homepage: http://solrex.cn
SimpLight Nanoelectronics Ltd. 6 Zhichun Road, 10th Floor,
Beijing, China
Phone: +86-10-5126-6989 --- Email: wenbo.yang simplnano.com
|
