search for: foo_munged

...The vague strategy I am imagining for the build proces is this: 1) compile runtime into a static library, just like any other static library 2) collect all the '.o' files in the static archive, and in any dependencies' static archive libraries 3) for each 'foo.o' build a 'foo_munged.o' using $tool, the _munged version has all symbols not on the whitelist for export to the instrumented binary 4) put all of the _munged '.o' files into a single runtime archive The $tool here could be "ld -r" with a linker script, or (likely necessary on windows) a very si...

...the build proces is this: > > 1) compile runtime into a static library, just like any other static > library > > 2) collect all the '.o' files in the static archive, and in any > dependencies' static archive libraries > > 3) for each 'foo.o' build a 'foo_munged.o' using $tool, the _munged > version has all symbols not on the whitelist for export to the instrumented > binary > > 4) put all of the _munged '.o' files into a single runtime archive > > > The $tool here could be "ld -r" with a linker script, or (likely...

...gt; >> 1) compile runtime into a static library, just like any other static >> library >> >> 2) collect all the '.o' files in the static archive, and in any >> dependencies' static archive libraries >> >> 3) for each 'foo.o' build a 'foo_munged.o' using $tool, the _munged >> version has all symbols not on the whitelist for export to the instrumented >> binary >> >> 4) put all of the _munged '.o' files into a single runtime archive >> >> >> The $tool here could be "ld -r" with...

Hi, Yes, stlport was a pain to deploy and maintain + it calls normal operator new/delete (there is no way to put them into a separate namespace). Note that in some codebases we build asan/tsan runtimes from source. How the build process will look with that object file mangling? How easy it is to integrate it into a custom build process? Soon I will start integrating tsan into Go language. For

...runtime into a static library, just like any other static >>> library >>> >>> 2) collect all the '.o' files in the static archive, and in any >>> dependencies' static archive libraries >>> >>> 3) for each 'foo.o' build a 'foo_munged.o' using $tool, the _munged >>> version has all symbols not on the whitelist for export to the instrumented >>> binary >>> >>> 4) put all of the _munged '.o' files into a single runtime archive >>> >>> >>> The $tool here cou...