search for: __asan__

...This step works not dissimilarly to the step to link an executable: we build the list of archive libraries depended on, but instead of linking an executable, we run a linker script over them. This script will re-link each '.o' file from the transitive closure of archives, prepending a '__asan__' (or other runtime library prefix) onto each symbol; effectively mangling each symbol. All of these processed '.o' files would go into a single, final archive that would be the installed runtime library. The only functions not processed in this manner are a white list of "exported&...

...dissimilarly to > the step to link an executable: we build the list of archive libraries > depended on, but instead of linking an executable, we run a linker script > over them. This script will re-link each '.o' file from the transitive > closure of archives, prepending a '__asan__' (or other runtime library > prefix) onto each symbol; effectively mangling each symbol. All of these > processed '.o' files would go into a single, final archive that would be > the installed runtime library. The only functions not processed in this > manner are a white lis...

...>> the step to link an executable: we build the list of archive libraries >> depended on, but instead of linking an executable, we run a linker script >> over them. This script will re-link each '.o' file from the transitive >> closure of archives, prepending a '__asan__' (or other runtime library >> prefix) onto each symbol; effectively mangling each symbol. All of these >> processed '.o' files would go into a single, final archive that would be >> the installed runtime library. The only functions not processed in this >> manner...

...e step to link an executable: we build the list of archive libraries >>> depended on, but instead of linking an executable, we run a linker script >>> over them. This script will re-link each '.o' file from the transitive >>> closure of archives, prepending a '__asan__' (or other runtime library >>> prefix) onto each symbol; effectively mangling each symbol. All of these >>> processed '.o' files would go into a single, final archive that would be >>> the installed runtime library. The only functions not processed in this &gt...

...nk an executable: we build the list of archive libraries >>>> depended on, but instead of linking an executable, we run a linker script >>>> over them. This script will re-link each '.o' file from the transitive >>>> closure of archives, prepending a '__asan__' (or other runtime library >>>> prefix) onto each symbol; effectively mangling each symbol. All of these >>>> processed '.o' files would go into a single, final archive that would be >>>> the installed runtime library. The only functions not processed...