search for: covariant3

...#39;t have any other option) and Mac OS. Alexander, Out of curiosity, how do these CF bugs show up in a backtrace? For instance, the additional darwin-specific failures I see with -fsanitize=address in the FSF g++ testsuite typically appear as simple segfaults such as with... FAIL: g++.dg/abi/covariant3.C -std=c++98 execution test FAIL: g++.dg/abi/covariant3.C -std=c++11 execution test that backtraces as... Starting program: /sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/gcc/testsuite/g++/covariant3.exe Reading symbols for shared libraries +++++................................. done Program...

Currently the replacement of allocation routines is based on creating a new malloc zone and a new CFAllocator (because the allocator replacement is done later than it could be, we must have both). This makes us depend on CoreFoundation to call CFAllocatorSetDefault. Because of some bugs in CF which start firing after CFAllocatorSetDefault, we have to add several hacks to circumvent the effects of