> With 2.3.39 and prior kernels, all glibc programs using si_uid get broken
> values (because glibc uses a 32bit type for si_uid and thus gets usually
Ok this was the bit I was unware of. I assumed glibc did the right thing.
Also on different endian processors you will get differently inconvenient
results, which side does the compiler pad ?
> upper 16 bits of id garbage - running my siginfotest.c on glibc gives me
> bogus si_uid like -939655168) and as I have not seen anybody complaining
Ok
> So the question is whether to fix current glibc programs, make things less
> complicated and break libc5 (well, breaking means worst that on a system with uids
Andreas said that libc5 doesnt use siginfo stuff anyway ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:20 EST