search for: libasan

...de into FSF gcc (and are keeping >> it synced to the upstream llvm.org code). I have been helping >> with the darwin build and testing -fsanitize=address against the >> complete FSF gcc testsuite. This seems to have exposed a potential >> bug in pthread or eh on darwin under libasan. Hundreds of test cases >> in the g++ and libstdc++ testsuites fail under -fsanitize=address >> in the following manner... >> >> ASAN:SIGSEGV >> ================================================================= >> ==2738== ERROR: AddressSanitizer: SEGV on unknown...

...s have ported llvm.org's asan code into FSF gcc (and are keeping it synced to the upstream llvm.org code). I have been helping with the darwin build and testing -fsanitize=address against the complete FSF gcc testsuite. This seems to have exposed a potential bug in pthread or eh on darwin under libasan. Hundreds of test cases in the g++ and libstdc++ testsuites fail under -fsanitize=address in the following manner... ASAN:SIGSEGV ================================================================= ==2738== ERROR: AddressSanitizer: SEGV on unknown address 0x0000ffd27000 (pc 0x0000ffd27000 sp 0x7fff5...

Hi all, We observed that under certain circumstances pthread_create() (libasan implemention) does not return. The conditions are the following: - address sanitizer enabled - main and child thread run on the same CPU (affinity) - real-time scheduling policy for both threads - different scheduling priority values (this includes the case of setting a real-time policy for one...

...(and are keeping >>> it synced to the upstream llvm.org code). I have been helping >>> with the darwin build and testing -fsanitize=address against the >>> complete FSF gcc testsuite. This seems to have exposed a potential >>> bug in pthread or eh on darwin under libasan. Hundreds of test cases >>> in the g++ and libstdc++ testsuites fail under -fsanitize=address >>> in the following manner... >>> >>> ASAN:SIGSEGV >>> ================================================================= >>> ==2738== ERROR: AddressSa...

...rg's asan code into FSF gcc (and are keeping > it synced to the upstream llvm.org code). I have been helping > with the darwin build and testing -fsanitize=address against the > complete FSF gcc testsuite. This seems to have exposed a potential > bug in pthread or eh on darwin under libasan. Hundreds of test cases > in the g++ and libstdc++ testsuites fail under -fsanitize=address > in the following manner... > > ASAN:SIGSEGV > ================================================================= > ==2738== ERROR: AddressSanitizer: SEGV on unknown address 0x0000ffd27000...

...-- ================================================================= ==21606==ERROR: AddressSanitizer: heap-use-after-free on address 0x602000042830 at pc 0x7f9f834fa0f7 bp 0x7fff24ab9050 sp 0x7fff24ab87f8 READ of size 1 at 0x602000042830 thread T0 ??? #0 0x7f9f834fa0f6 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x5a0f6) ??? #1 0x7f787837d683 in _XimUnRegisterIMInstantiateCallback (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x64683) ??? #2 0x7f7878364d32 in XUnregisterIMInstantiateCallback (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x4bd32) ??? #3 0x7f787837d566 in _XimRegisterIMInstantiateCallback (/usr...

...(and are keeping >>> it synced to the upstream llvm.org code). I have been helping >>> with the darwin build and testing -fsanitize=address against the >>> complete FSF gcc testsuite. This seems to have exposed a potential >>> bug in pthread or eh on darwin under libasan. Hundreds of test cases >>> in the g++ and libstdc++ testsuites fail under -fsanitize=address >>> in the following manner... >>> >>> ASAN:SIGSEGV >>> ================================================================= >>> ==2738== ERROR: AddressS...

...seful in some situations. In particular, if a compiler driver automatically appends a static library to the final executable but you don't know the exact path of the library, there's currently no way to keep track of that dependency. A typical example of it is `-fsanitizer=asan` which adds libasan to the linker command line. If libasan is updated, you may want to rebuild your program, but you don't want to manually write its path to a build file because that may change. Proposal: Add a new command line flag `--write-dependencies=<path>` to lld. If the flag is given, lld creates a...

...>>>> it synced to the upstream llvm.org code). I have been helping >>>> with the darwin build and testing -fsanitize=address against the >>>> complete FSF gcc testsuite. This seems to have exposed a potential >>>> bug in pthread or eh on darwin under libasan. Hundreds of test cases >>>> in the g++ and libstdc++ testsuites fail under -fsanitize=address >>>> in the following manner... >>>> >>>> ASAN:SIGSEGV >>>> ================================================================= >>>> =...

...l7_4.2.x86_64.rpm 63ee891732a70dea3b62c0b5d535aff0b141f892b5b106244b8470e177d9ab85 gcc-objc++-4.8.5-16.el7_4.2.x86_64.rpm f6d14f434a63a300d04a196ce4ed0437ae274555b936d9fb6a04910cb2b9657b gcc-plugin-devel-4.8.5-16.el7_4.2.x86_64.rpm 9e21639f1f2e63e58647ca0e9a5aaad2f916460f4647f5b260b80cb623013407 libasan-4.8.5-16.el7_4.2.i686.rpm 97261d647a28ac63e0869f72bc2d2403fb81be3a9bebbce3cb95799ce4fb0fe9 libasan-4.8.5-16.el7_4.2.x86_64.rpm e62f707dcfe7d24bf106d593589b5b33fec977c8138a0a28cbaa1ac3538aa910 libasan-static-4.8.5-16.el7_4.2.i686.rpm 022cc384ba0b92554d9d00fc4eb346e8d764497adf7f16907b36354a323b1462...

...l7_6.2.x86_64.rpm 11083f3d86e04333bc8bedabebeba53b9a0d00b47b69bdd0dd9b0847a7ecb70d gcc-objc++-4.8.5-36.el7_6.2.x86_64.rpm 217f966f99a87abdd07fda4971cbe65ae68f74e4a65ff6dd972a0e4dc2e9e060 gcc-plugin-devel-4.8.5-36.el7_6.2.x86_64.rpm de3c266962526efc4e2960b7153cd8f56cffecfd1dcdb357797e4dc1726408ed libasan-4.8.5-36.el7_6.2.i686.rpm b1bed6bdb163928ae0c19d760983c3970b412b4a353cf827b6acc40674434298 libasan-4.8.5-36.el7_6.2.x86_64.rpm 90b931d343aacc05679bcb364abaa4e81aadb109432df7dec57011152dc28e75 libasan-static-4.8.5-36.el7_6.2.i686.rpm 8a474ea77ad996a57261226b2bfe9db46e5387ed879d355794c5788681640cf5...

...l7_4.1.x86_64.rpm 8089dd37b5d180463d02bc9a028768bff1c3e1e576a30954c4fbed5bc2238a16 gcc-objc++-4.8.5-16.el7_4.1.x86_64.rpm abaf62e1c1e1e53d090701c2afb9803cac1b523cb961176d744ebe4fc6439d53 gcc-plugin-devel-4.8.5-16.el7_4.1.x86_64.rpm 15a5e398ae2d5e476b7599a02a3503365081efb878c282e0ea383f6ccde63166 libasan-4.8.5-16.el7_4.1.i686.rpm 1e9da3ca1af45aa632b21f6eeef32543c63b831d5c7944579f1454311fd5ab8e libasan-4.8.5-16.el7_4.1.x86_64.rpm dcaaf63d9e595e4adc604f30bd1495490e72487cd970496c77bc5c99e1127a95 libasan-static-4.8.5-16.el7_4.1.i686.rpm cc62110941aaa47c0bbef909f67de5dcaa28216eaa4eef1ab739f2cd86ffc115...

...l7_6.1.x86_64.rpm 8d625412547d927d0fed1c0218be19ba3270cb48038823b3f884471002c713ca gcc-objc++-4.8.5-36.el7_6.1.x86_64.rpm 1ec24dbd2eb93a0212cdb6a2c1153f5801d3ed3c961fda5d7345417545a322ee gcc-plugin-devel-4.8.5-36.el7_6.1.x86_64.rpm c01ebc157601bad5ae16a7c526e089f152d0f03705017b56e459bbb9c11e8929 libasan-4.8.5-36.el7_6.1.i686.rpm 1353d37f9c2fce5e543a0be52db8e126097ccdb48782c397e71f363fc3fce316 libasan-4.8.5-36.el7_6.1.x86_64.rpm b82653f894c2e4ccf2d6041e18f6e6f5079ab719731b3346a76d148d2108c172 libasan-static-4.8.5-36.el7_6.1.i686.rpm e151a3c1253a69525a46a5fb725df848795b1b8a341d2b89a02efd799bf3e1dd...

...l7_5.1.x86_64.rpm 2a108a876222b41df1a71146b7e4302390f8093f546c261a7db0e8df8510ba32 gcc-objc++-4.8.5-28.el7_5.1.x86_64.rpm 9d9b5d25cd59b2620c533629cf765cb08432c3eaa05023784deb5d834fb496a7 gcc-plugin-devel-4.8.5-28.el7_5.1.x86_64.rpm a6ba9f4dd29038112bd66b301fb9825cac81dfe1d4982080f6a818fe5eefe966 libasan-4.8.5-28.el7_5.1.i686.rpm d46ca51f351f74c7e5220e20dc4fd3f5f14a49081b6f9de01d69703e8863065f libasan-4.8.5-28.el7_5.1.x86_64.rpm 77c231756853658ade09c8cc29ac747e53ef8fd576b0532e6bec6832df1271eb libasan-static-4.8.5-28.el7_5.1.i686.rpm bc79885f34aa659544240ee2644a6f77e9e04bbe6b3e654d61bcea82b19dedeb...

....el7_0.x86_64.rpm ec6f84c79a8f79c128fb6b8459baf90e61929c0ceb3af83515f048c25e82e350 gcc-objc++-4.8.2-16.2.el7_0.x86_64.rpm 47786bec040805aa8bc8c215424cf17fc91429933986084152ef774e2eb96f7c gcc-plugin-devel-4.8.2-16.2.el7_0.x86_64.rpm 02affe99974e1f7629572b423a01d9c04cf71c5132b33834920702388db7e2e3 libasan-4.8.2-16.2.el7_0.i686.rpm 65156882710703be048b2f3e2af1af7baac1d4f58d5b1c0d3c7fa9cd788b8301 libasan-4.8.2-16.2.el7_0.x86_64.rpm beadf9ad5fcfe7eeaa3f2c9c5e08f5c347a2857c543f0b2e88096801b6dea093 libasan-static-4.8.2-16.2.el7_0.i686.rpm ef3914fcfc6f03a6cca23b2e1606f5446740d1b6a5315f35946eba87cc5f1b5e...

...t; it synced to the upstream llvm.org code). I have been helping > >>>> with the darwin build and testing -fsanitize=address against the > >>>> complete FSF gcc testsuite. This seems to have exposed a potential > >>>> bug in pthread or eh on darwin under libasan. Hundreds of test cases > >>>> in the g++ and libstdc++ testsuites fail under -fsanitize=address > >>>> in the following manner... > >>>> > >>>> ASAN:SIGSEGV > >>>> ===========================================================...

...; > > In particular, if a compiler driver automatically appends a static library > to the final executable but you don't know the exact path of the library, > there's currently no way to keep track of that dependency. A typical > example of it is `-fsanitizer=asan` which adds libasan to the linker > command line. If libasan is updated, you may want to rebuild your program, > but you don't want to manually write its path to a build file because that > may change. > > > > Proposal: > > Add a new command line flag `--write-dependencies=<path>`...

...want to spend too much effort fixing mach_override. > > --kcc Kostya, Unless I am misunderstanding the code in asan/asan_intercepted_functions.h, using MAC_INTERPOSE_FUNCTIONS on FSF gcc will require the missing blocks support to be implemented. I did a quick and dirty attempt to build libasan using libsanitizer/asan/dynamic/asan_interceptors_dynamic.cc imported from llvm svn. The bootstrap chokes on... /bin/sh ../libtool --tag=CXX --mode=compile /sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/./gcc/xg++ -B/sw/src/fink.build/gcc48-4.8.0-1000/darwin_objdir/./gcc/ -nostdinc++ -nostdin...

...override. > > > > --kcc > > Kostya, > Unless I am misunderstanding the code in > asan/asan_intercepted_functions.h, > using MAC_INTERPOSE_FUNCTIONS on FSF gcc will require the missing blocks > support > to be implemented. I did a quick and dirty attempt to build libasan using > libsanitizer/asan/dynamic/asan_interceptors_dynamic.cc imported from llvm > svn. > The bootstrap chokes on... > Alex is the expert in the OSX side of things, hopefully he can comment. But our situation wrt asan on OSX is as I see it: - mach_override does not work: we spent...

...the upstream llvm.org code). I have been helping > > >>>> with the darwin build and testing -fsanitize=address against the > > >>>> complete FSF gcc testsuite. This seems to have exposed a potential > > >>>> bug in pthread or eh on darwin under libasan. Hundreds of test cases > > >>>> in the g++ and libstdc++ testsuites fail under -fsanitize=address > > >>>> in the following manner... > > >>>> > > >>>> ASAN:SIGSEGV > > >>>> ==================================...