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] |
On Tuesday, December 14, 2010 11:31:33 Pedro Alves wrote: > On Tuesday 14 December 2010 15:09:43, Mike Frysinger wrote: > > if the gdbserver code can remain backwards compatible with the Linux ABI, > > then i dont have a problem changing to a qXfer style. > > I don't think there'd be a problem with that. gdbserver can continue > fetching whatever it needs from the kernel using the ptrace registers > api, but that'd remain hidden from gdb (or the remote protocol). Getting > rid of the fdpic pseudo registers from the core register set also > presumably unifies the gdb core register set with an eventual bare metal > bfin toolchain (btw, isn't there such a thing?) or any other eventual > non-fdpic bfin toolchain. thinking about it more, the gdb port atm doesnt support FDPIC. so if the only contentious point of the gdbserver code is the FDPIC handling, then i can simply drop that and revisit when the Blackfin/FDPIC core code is merged. we do Blackfin bare metal every day. from the Blackfin side of things, it's the same as doing Linux/FLAT. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |