[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 91153] Possible new leak to suppress in glibc-2.?.supp
From:       "Daniel Richard G." <skunk () iskunk ! org>
Date:       2005-01-31 21:51:05
Message-ID: 20050131215105.18427.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=91153         
skunk iskunk org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |



------- Additional Comments From skunk iskunk org  2005-01-31 22:51 -------
It may have taken more than that week, but I've put together a trivial test case \
illustrating the "leak." All that's needed to trigger it is -lpthread and a call to \
some random stdio function. (See attachment in next post)

I concede that this is not a memory leak per se, but believe there is a good case for \
adding an appropriate suppression to glibc-2.[23].supp; any loss records reported in \
the test code _have_ to be noise.

Similar loss records are reported with glibc 2.2 and 2.3, though the call stacks are \
different. (With 2.3, it seems to happen at the end of the program, in an implicit \
exit() call.)

Curiously enough, when we use a valgrind that was built on a 2.2 system, on a 2.3 \
system, no loss is reported....


[prev in list] [next in list] [prev in thread] [next in thread]