This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [RFA 4/5] New port: CR16: gdbserver
- From: Kaushik Phatak <Kaushik dot Phatak at kpitcummins dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Tue, 22 Jan 2013 13:42:54 +0000
- Subject: RE: [RFA 4/5] New port: CR16: gdbserver
- References: <C6CA53A2A46BA7469348BDBD663AB65845B2FF84@KCHJEXMB03.kpit.com> <50CB742E.9090506@redhat.com> <C6CA53A2A46BA7469348BDBD663AB65848564536@KCHJEXMB02.kpit.com> <50F97ABF.4060203@redhat.com>
Hi Pedro,
Thanks for your feedback.
> No, this needs to be fixed. The .dat registers must agree with GDB's remote
> register set. Once that is fixed, you'll be able to put more registers
> in the "expedite" set
I am working on these points. From what I see, my cr16_regmap needs to be
4-byte aligned so that ptrace calls within linux-low.c can use these without
causing any I/O errors. The updated reg.dat file would not match in offset
to cr16_regmap, but would match gdb.
Some additional code would be needed to handle the padding and packing through
ptrace in the kernel. This would allow the correct register number to be
accessed which would match gdb as well as reg-cr16.dat.
Let me know if you have any thoughts on this.
Regards,
Kaushik