[Bug libc/4861] New: uninitialized data in the profiling code

["thor at math dot tu-berlin dot de" <sourceware-bugzilla@sourceware.org>]

When running multithreaded code on the above architecture using valgrind, it
detects at times the following problem:

==30381== Use of uninitialised value of size 8
==30381==    at 0x564C310: profil_counter (in /lib64/libc-2.5.so)
==30381==    by 0x55B95AF: (within /lib64/libc-2.5.so)

Apparently, something's wrong here. Unfortunately, this problem is not easy to
reproduce.

A potentially related problem seems to be that semaphores and profiling do not
seem to go well together in multithreaded code. With profiling enabled, some
semaphores seem to become spuriously available?

glibc release seems to be 2.5 on a Suse 10.2 (unfortunately with a custom kernel
patched by HP), running

gcc (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux)

-- 
           Summary: uninitialized data in the profiling code
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: thor at math dot tu-berlin dot de
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=4861

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.