This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug nptl/3317] Overriding free which clobbers data and calls pthread_getspecific can get bad value

------- Additional Comments From ian at airs dot com  2006-10-12 05:58 -------
That was, of course, just an example which tests for whether the problem exists.

The issue is overriding malloc(), free() and friends, where they use pthread
specific keys, and where free clobbers the block data for debugging purposes. 
Since the pthread code itself calls free, it is impossible for free to know
whether or not the pthread specific key has been destroyed.  The only way is for
free to check whether pthread_get_specific returns NULL, but that doesn't work
if it clobbers the data for debugging purposes.

I can't say that I'm surprised that you plan to ignore this bug report. 
However, I hope the report will give a hint to distros to swap the order of
those two lines.

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]