Glibc 2.12 segfaults under certain conditions

[Carlos O'Donell]

On Wed, Aug 18, 2010 at 7:43 AM, Daniele Stanzani
<daniele.stanzani@fcp.it> wrote:
> A generated backtrace for the second row:
> (gdb) backtrace
> #0  0x00007f83eff66068 in ?? () from /lib/libnss_files.so.2
> #1  0x00007f83eff66531 in _nss_files_getpwuid_r ()
> from /lib/libnss_files.so.2
> #2  0x00007f83f0837ebd in getpwuid_r () from /lib/libc.so.6
> #3  0x00007f83f083a26a in ?? () from /lib/libc.so.6
> #4  0x00007f83f0839f45 in getlogin () from /lib/libc.so.6
> #5  0x0000000000403513 in ?? ()
> #6  0x00000000004024bd in ?? ()
> #7  0x00007f83f07b7c4d in __libc_start_main () from /lib/libc.so.6
> #8  0x00000000004018d9 in ?? ()
> #9  0x00007fff744fa328 in ?? ()
> #10 0x000000000000001c in ?? ()
> #11 0x0000000000000001 in ?? ()
> #12 0x00007fff744fa8fe in ?? ()
> #13 0x0000000000000000 in ?? ()
>
>
> Should I report this issue to my distribution or to the glibc bugzilla?

Always report issues to your distribution.

Your distribution maintainers will work with upstream glibc to resolve
the issue.

In your case my first guess is bad memory on the machine.

Cheers,
Carlos.