On Thu, Jul 4, 2019 at 2:19 AM Arnd Bergmann wrote:
>
> On Thu, Jul 4, 2019 at 9:20 AM Andreas Schwab wrote:
> >
> > On Jul 03 2019, Alistair Francis wrote:
> >
> > > On Wed, Jul 3, 2019 at 12:08 AM Andreas Schwab wrote:
> > >>
> > >> On Jul 02 2019, Alistair Francis wrote:
> > >>
> > >> > In
On Thu, Jul 4, 2019 at 9:20 AM Andreas Schwab wrote:
>
> On Jul 03 2019, Alistair Francis wrote:
>
> > On Wed, Jul 3, 2019 at 12:08 AM Andreas Schwab wrote:
> >>
> >> On Jul 02 2019, Alistair Francis wrote:
> >>
> >> > In the RISC-V 32-bit glibc port [1] the siginfo_t struct in the kernel
> >>
On Jul 03 2019, Alistair Francis wrote:
> On Wed, Jul 3, 2019 at 12:08 AM Andreas Schwab wrote:
>>
>> On Jul 02 2019, Alistair Francis wrote:
>>
>> > In the RISC-V 32-bit glibc port [1] the siginfo_t struct in the kernel
>> > doesn't line up with the struct in glibc. In glibc world the
On Wed, Jul 3, 2019 at 12:08 AM Andreas Schwab wrote:
>
> On Jul 02 2019, Alistair Francis wrote:
>
> > In the RISC-V 32-bit glibc port [1] the siginfo_t struct in the kernel
> > doesn't line up with the struct in glibc. In glibc world the _sifields
> > union is 8 byte alligned (although I can't
On Jul 02 2019, Alistair Francis wrote:
> In the RISC-V 32-bit glibc port [1] the siginfo_t struct in the kernel
> doesn't line up with the struct in glibc. In glibc world the _sifields
> union is 8 byte alligned (although I can't figure out why)
Try ptype/o in gdb.
Andreas.
--
Andreas
Resending the the correct linux-riscv address.
In the RISC-V 32-bit glibc port [1] the siginfo_t struct in the kernel
doesn't line up with the struct in glibc. In glibc world the _sifields
union is 8 byte alligned (although I can't figure out why) while in the
kernel wordl the _sifields union is
6 matches
Mail list logo