Change Details

This adds the PT_GETREGSET ptrace type. This reads all the registers from a specified core dump note type. Because the data field is an int the arguments are backwards when compared to the Linux PTRACE_GETREGSET call. The ptrace addr points to a struct iovec pointing at memory to hold the registers along with its length. On success the length in the iovec is updated to tell userspace the actual length the kernel wrote. Currently there's no way to ask for the length userspace needs to allocate from the kernel. One possible solution is to use a null vec, where the base is NULL and length is 0, and have the kernel set the length to be correct. Add support to read NT_X86_XSTATE. This is sufficienrly complex as its length is only known at runtime. To handle this case use a SYSINIT to set the size on boot.

This adds the PT_GETREGSET and PT_SETREGSET ptrace types. These can be used to access all the registers from a specified core dump note type. The NT_PRSTATUS and NT_FPREGSET notes are initially supported. Other machine-dependant types are expected to be added in the future. The ptrace addr points to a struct iovec pointing at memory to hold the registers along with its length. On success the length in the iovec is updated to tell userspace the actual length the kernel wrote or, if the base address is NULL, the length the kernel would have written. Because the data field is an int the arguments are backwards when compared to the Linux PTRACE_GETREGSET call.

This adds the PT_GETREGSET and PT_SETREGSET ptrace types. This reads all the registers fromThese can be a specified core dump note type. Because the data field is an int theused to access all the registers from a specified core dump note type. arguments are backwards when compared to the Linux PTRACE_GETREGSETThe NT_PRSTATUS and NT_FPREGSET notes are initially supported. Other callmachine-dependant types are expected to be added in the future. The ptrace addr points to a struct iovec pointing at memory to hold the registers along with its length. On success the length in the iovec is updated to tell userspace the actual length the kernel wrote. Currently there's no way to ask for the length userspace needs to or, if the allocate from the kernel. One possible solution is to ubase a null vec, where the baseddress is NULL and length is 0, and havethe length the kernel set the length to be correctwould have written. Add support to read NT_X86_XSTATE. This is sufficienrly complex as itsBecause the data field is an int the arguments are backwards when length is only known at runtime. To handle this case use a SYSINIT to set the size on bootcompared to the Linux PTRACE_GETREGSET call.