Bug#673596: libc6: FTBFS on wheezy/sid amd64 (test suite failures)

[Jonathan Nieder <jrnieder@gmail.com>]

tags 673596 + upstream
quit

Thibaut Girka wrote:

> dlfcn/bug-atexit3 is the first to fail (fails to load libstdc++.so.6).

Oh, right.  glibc doesn't know to look to /lib/$(gcc -print-multiarch)
for libraries, so I usually copy libstdc++.so.6 and libgcc_s.so.1 to
the build tree by hand so the test suite can use them.  There's
probably a more elegant way.

[...]
> Yeah, running it using the newly-built glibc reproduces the bug.
>
> (I ran it like that:
>  ./elf/ld-linux.so.2 --library-path .:elf:nptl /home/thib/tmp/a.out
> )
>
> In addition, I've been watching /proc/$PID/status to see how the program behaves.
> Most of the time, the number of threads stays in 2 ~ NB_THREADS, but at some point in time,
> it may increase to hundreds, or even thousands of threads.

Perfect --- looks like it's not a Debian-specific bug and the mass of
glibc hackers at large can be brought to bear on it, too.

Please contact libc-help@sourceware.org[1] with your testcase and a
summary of the symptoms and how you ran into it to get help tracking
down the cause.

Thanks again for narrowing this down this far.  Hopefully we can find
the culprit soon.

Good luck,
Jonathan

[1] Traffic is about 2 messages per day.  I don't remember whether it
is subscribers-only.  It's probably safest to subscribe (with or
without mail delivery) to be sure mail doesn't get stuck in a
moderation queue: http://www.gnu.org/software/libc/development.html