https://d.puremagic.com/issues/show_bug.cgi?id=11981
--- Comment #18 from Martin Nowak <[email protected]> 2014-02-09 10:00:29 PST --- (In reply to comment #17) > I'm starting to wonder if it's really posix-specific. The issue only manifests > when using shared libraries (second malloc call is made from dl-tls.c). > Yep, because the TLS segment for loaded shared libraries is allocated lazily, while the TLS segments the executable and linked shared libraries are allocated eagerly. > Can Windows DLL TLS handling be susceptible to this too? Is it currently > possible to replicate that unittest for Windows? The same problem cannot happen on OSX or Windows, because we're using suspend API's there, i.e. no signal handler code that does the TLS access is run. -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
