Re: test-getlogin_r segfaults with glibc 2.12

[Bruno Haible]

Hi Richard,

> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7ae77fe in __strncpy_sse2 (s1=<value optimized out>, 
>     s2=<value optimized out>, n=<value optimized out>) at ./strncpy.c:83
> 83      *++s1 = '\0';
> (gdb) bt
> #0  0x00007ffff7ae77fe in __strncpy_sse2 (s1=<value optimized out>, 
>     s2=<value optimized out>, n=<value optimized out>) at ./strncpy.c:83
> #1  0x00007ffff7b071d2 in __getlogin_r_loginuid (name=0x7fffffffda90 
> "rjones", 
>     namesize=0) at ../sysdeps/unix/sysv/linux/getlogin_r.c:84
> #2  0x00007ffff7b07299 in getlogin_r (name=0x7fffffffda90 "rjones", 
> namesize=0)
>     at ../sysdeps/unix/sysv/linux/getlogin_r.c:103

You can report this as a glibc bug. A call of getlogin_r with namesize = 0
should yield a return value ERANGE, not a crash. I bet it's due to the new
Linux-specific getlogin_r implementation from 2010-03-25.

Bruno