This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: TLS redux
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: Paul Pluzhnikov <ppluzhnikov at google dot com>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Roland McGrath <roland at hack dot frob dot com>, "GNU C. Library" <libc-alpha at sourceware dot org>
- Date: Mon, 27 Jan 2014 18:32:46 +0100
- Subject: Re: TLS redux
- Authentication-results: sourceware.org; auth=none
- References: <20140115022335 dot EB13174430 at topped-with-meat dot com> <Pine dot LNX dot 4 dot 64 dot 1401150520530 dot 14350 at digraph dot polyomino dot org dot uk> <CALoOobOyQxDaszErqoOkSdHsc7NestF7Pt9rS01aPzWZcnFZCQ at mail dot gmail dot com>
Paul Pluzhnikov <ppluzhnikov@google.com> writes:
> One example that's burned into my memory is that memory allocated by
> ld.so's private malloc may later be free'd by public libc.so.6 free.
That should not happen, and would be a major bug. You would get an
error when enabling malloc checking.
> They are the same implementation, so no harm done, right?
The ld.so malloc is a stub implementation that has nothing in common
with libc malloc.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."