Date: Tue, 10 Apr 2018 10:33:59 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Re: tcmalloc compatibility On Tue, Apr 10, 2018 at 01:22:54PM +0300, Denis V. Razumovsky wrote: > Dear Sirs, > > Could you please be so kind to fix muls compatibility with tcmalloc > (libtcmalloc_minimal in particular). Seems that tcmalloc developers > can't fix all issues without corresponding changes of musl. malloc interposition is undefined behavior (as is any interposition of standard functions), and is very difficult to actually support as an extension in a way that doesn't have lots of serious problems. This has been discussed before but I don't have links handy. I'll try to dig them up later. The glibc folks are also aware that it's broken (on glibc, it only works if you get lucky and follow unwritten rules) and would probably like a fix but it's not easy on their side either. > Small cite from tcmalloc bug-report: > > > >> Doesn't look like musl will ever support replacing their malloc for > dynamically linked musl. This claim doesn't seem to be well-justified. Myself and members of our community have written a lot on why existing malloc interposition hacks are broken, but there's also an interest in what would take to make it work, and I particularly am interested in this from a standpoint that musl's malloc is not very good, and that being able to dynamically interpose it would facilitate developing and testing a replacement. Note however that if malloc interposition is supported at some point, there will be a specification for constraints on the malloc implementation including what functions you can call from it (e.g. something like AS-safety), and bug reports for implementations that do things outside this spec (and thereby inherently can't work safely or reliably) will not be considered bugs. > All appropriate details you can find at the page: > > https://github.com/gperftools/gperftools/issues/693 > > > Because of this many important software can't be ported properly to > Alpine linux because they depends from libtcmalloc_minimal. This seems false. You can just remove tcmalloc from them and use the system malloc and they will work fine (possibly after patching out unnecessary calls into the internals of the malloc replacement, e.g. for debug/stats/etc.). Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.