This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA 4/5] New port: CR16: gdbserver


On 01/23/2013 12:50 PM, Kaushik Phatak wrote:
>> You mean additional code in gdbserver, or in the kernel?  I'd think the
>> former.
> Yes, the code changes would be for gdbserver and gdb. 
> I would prefer to keep my kernel code changes to a minimal.
> 
>> always expose the registers as pairs in the remote protocol,
>> and then implement the user visible non-paired registers in
>> GDB as pseudo registers (and hide the pairs).  IOW, your .dat
>> file would stay the same, and gdbserver wouldn't change.  GDB's
>> core cr16 register numbers would be decoupled from the RSP
>> register set.
> Yes, I agree. Disturbing the .dat file is causing issues in the 
> remote protocol. 

What issues?  Can you be more specific?

> So, using pseudo registers within gdb would be a 
> better way to proceed as long as I can get the register numbers to 
> match my expedite register numbers.

-- 
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]