This is a pretty big change that I haven't tested any, which worries
me a lot. The general idea here is that "struct elf_prstatus" can be
visible to userspace (from )
"
Generic ptrace interface that exports the architecture specific
regsets using the corresponding NT_* types (which are
This is a pretty big change that I haven't tested any, which worries
me a lot. The general idea here is that "struct elf_prstatus" can be
visible to userspace (from )
"
Generic ptrace interface that exports the architecture specific
regsets using the corresponding NT_* types (which are
Palmer Dabbelt wrote:
> I tried to fix all the users of "struct elf_prstatus" that should now
> be using "struct elf_fdpic_prstatus". The only testing I did here was
> to build a Blackfin defconfig with "struct elf_prstatus" not defined,
> and to build an x86 defconfig with "struct
Palmer Dabbelt wrote:
> I tried to fix all the users of "struct elf_prstatus" that should now
> be using "struct elf_fdpic_prstatus". The only testing I did here was
> to build a Blackfin defconfig with "struct elf_prstatus" not defined,
> and to build an x86 defconfig with
This is a pretty big change that I haven't tested any, which worries
me a lot. The general idea here is that "struct elf_prstatus" can be
visible to userspace (from )
"
Generic ptrace interface that exports the architecture specific
regsets using the corresponding NT_* types (which are
This is a pretty big change that I haven't tested any, which worries
me a lot. The general idea here is that "struct elf_prstatus" can be
visible to userspace (from )
"
Generic ptrace interface that exports the architecture specific
regsets using the corresponding NT_* types (which are
6 matches
Mail list logo