On Monday 19 September 2011 16:25:05, Linas Vepstas (Code Aurora) wrote: > On Sat, Sep 10, 2011 at 12:29:57PM +0100, Pedro Alves wrote: > > On Saturday 10 September 2011 07:42:26, Jonas Bonn wrote: > > > > > I'm really not an expert on GDB, but I believe it can use either the > > > PEEK/POKE functions to access regs, or it can use GET/SETREGS; it's an > > > architecture-dependent configuration. I think the second variant can > > > be easily modified to become GET/SETREGSET instead, and the PEEK/POKE > > > variant wouldn't be needed at all. > > > > Yes, the x86/x86-64 ports or gdb and gdbserver are already > > using GET/SETREGSET even. > > Reading the code, it seemed to only fetch "extended state" in > this way, and not all of the registers. Am I mistaken? True. gdb/gdbserver need to keep working with older x86 kernels, so we avoid having two ways of doing things with the other registers. No reason to support legacy interfaces with new ports though. I wish there was an equivalent of PTRACE_GETREGSET for siginfo... -- Pedro Alves -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
