search for: asan_rtl

Displaying 18 results from an estimated 18 matches for "asan_rtl".

2011 Jun 16
2
[LLVMdev] LLVM-based address sanity checker
...t functionality, we could use that instead. This is my first code in LLVM, so it definitely needs cleanup to meet the LLVM guidelines. Run time library (could be used with any other compiler): - Almost everything is on one file: http://code.google.com/p/address-sanitizer/source/browse/trunk/asan/asan_rtl.cc This library replaces malloc, tracks thread stacks, replaces SIGILL and SIGSEGV handlers, reports warnings. Linux x86/x86_64 and ChromiumOS is fully functional, MacOS is in flight. Tests: http://code.google.com/p/address-sanitizer/source/browse/trunk/asan/asan_test.cc --kcc > -Chris >...
2011 May 03
5
[LLVMdev] LLVM-based address sanity checker
...LLVM trunk? The instrumentation pass is ~350 LOC ( http://code.google.com/p/address-sanitizer/source/browse/trunk/llvm/AddressSanitizer.cpp), but may grow over time as we add optimizations. The run-time library (malloc replacement, http://code.google.com/p/address-sanitizer/source/browse/trunk/asan/asan_rtl.cc) is ~1500 LOC. Thanks, --kcc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110503/dd4e4f71/attachment.html>
2016 May 25
4
Runtime interception: design problem
...correct directory but I don't see how this should be designed in order that the code optimized by BoundsCheking Pass uses my own malloc&free functions. I spent quite some time on Asan runtime code and found that runtime could be initialized with a call to __asan_init() (function defined in asan_rtl.cc) from the instrumented code directly but I don't know if it's the only way to do it or how to reproduce it... So to resume, I want to make my own malloc and free function to be called by the code I instrument with BoundsChecking. Any suggestion is welcome =) Thanks, Pierre ------------...
2011 Jun 16
2
[LLVMdev] LLVM-based address sanity checker
...rumentation pass is ~350 LOC ( > http://code.google.com/p/address-sanitizer/source/browse/trunk/llvm/AddressSanitizer.cpp), > but may grow over time as we add optimizations. > The run-time library (malloc replacement, > http://code.google.com/p/address-sanitizer/source/browse/trunk/asan/asan_rtl.cc) > is ~1500 LOC. > > Thanks, > > --kcc > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110616/e95aacf3/attachment.html>
2011 Jun 16
0
[LLVMdev] LLVM-based address sanity checker
...> The instrumentation pass is ~350 LOC (http://code.google.com/p/address-sanitizer/source/browse/trunk/llvm/AddressSanitizer.cpp), but may grow over time as we add optimizations. > The run-time library (malloc replacement, http://code.google.com/p/address-sanitizer/source/browse/trunk/asan/asan_rtl.cc) is ~1500 LOC. > > Thanks, > > --kcc > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- next part --------...
2014 Oct 10
2
[LLVMdev] Remaining Compiler-RT failures in ARM
On 10 October 2014 21:31, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > Sounds like an arm-thumb interworking veneer, generated by the linker... the > real function should be called 'asan_handle_no_return' (with some number of '_' > prefixing it. I don't remember how many get added). It is a veneer which has just a jump and a word after it, which
2015 Dec 02
2
fuzzer crash (but not the good kind)
...projects/compiler-rt/lib/sanitizer_common/sanitizer_coverage_libcdep.cc:467 "((n % 16)) == ((0))" (0x1, 0x0) #0 0x11d3b7 in __asan::AsanCheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/asan/asan_rtl.cc:67:3 #1 0x122f1f in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_common.cc:159:5 #2 0x134317 in __sanitizer::CoverageData::Update8bitCounterBitsetAn...
2016 May 26
0
Runtime interception: design problem
...rectory but I don't see how this should be designed in order that the code optimized by BoundsCheking Pass uses my own malloc&free functions. > > I spent quite some time on Asan runtime code and found that runtime could be initialized with a call to __asan_init() (function defined in asan_rtl.cc) from the instrumented code directly but I don't know if it's the only way to do it or how to reproduce it... > > So to resume, I want to make my own malloc and free function to be called by the code I instrument with BoundsChecking. Any suggestion is welcome =) > > Thanks,...
2015 Dec 03
2
fuzzer crash (but not the good kind)
...ommon/sanitizer_coverage_libcdep.cc:467 >> "((n % 16)) == ((0))" (0x1, 0x0) >> #0 0x11d3b7 in __asan::AsanCheckFailed(char const*, int, char const*, >> unsigned long long, unsigned long long) >> /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/asan/asan_rtl.cc:67:3 >> #1 0x122f1f in __sanitizer::CheckFailed(char const*, int, char >> const*, unsigned long long, unsigned long long) >> /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_common.cc:159:5 >> #2 0x134317 in >> __sanit...
2019 Jan 24
2
[Release-testers] [8.0.0 Release] rc1 has been tagged
On Thu, 2019-01-24 at 19:58 +0100, Dimitry Andric via Release-testers wrote: > On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > > > > 8.0.0-rc1 was just tagged (from the branch at r351980). > > > > It took a little longer than planned, but it's looking good. > > > > Please run the test
2015 Dec 03
2
fuzzer crash (but not the good kind)
....cc:467 >>>> "((n % 16)) == ((0))" (0x1, 0x0) >>>> #0 0x11d3b7 in __asan::AsanCheckFailed(char const*, int, char >>>> const*, unsigned long long, unsigned long long) >>>> /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/asan/asan_rtl.cc:67:3 >>>> #1 0x122f1f in __sanitizer::CheckFailed(char const*, int, char >>>> const*, unsigned long long, unsigned long long) >>>> /home/brian/src/fuzzpy/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_common.cc:159:5 >>>>...
2016 May 25
0
Runtime interception: design problem
...see how this should be designed in > order that the code optimized by BoundsCheking Pass uses my own > malloc&free functions. > > I spent quite some time on Asan runtime code and found that runtime > could be initialized with a call to __asan_init() (function defined in > asan_rtl.cc) from the instrumented code directly but I don't know if > it's the only way to do it or how to reproduce it... > > So to resume, I want to make my own malloc and free function to be > called by the code I instrument with BoundsChecking. Any suggestion is > welcome =) &...
2013 Nov 21
0
[LLVMdev] Building LLVM with asan
...-lz -ltinfo -lm /usr/bin/ld: /home/kfischer/julia/deps/llvm-svn/build_Release+Asserts+Sanitize/Release+Asserts/bin/llvm-lto: local symbol `__asan_report_store4' in /home/kfischer/julia/deps/llvm-svn/build_Release+Asserts/Release+Asserts/bin/../lib/clang/3.5/lib/linux/libclang_rt.asan-x86_64.a(asan_rtl.o) is referenced by DSO /usr/bin/ld: final link failed: Bad value On Thu, Nov 21, 2013 at 12:08 PM, Keno Fischer <kfischer at csail.mit.edu>wrote: > Indeed, removing that flag works fine, the only question is why this is > added in tools/llvm-shlib/Makefile in the first place then an...
2017 Jul 31
0
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
On 31 Jul 2017, at 19:26, Hans Wennborg <hans at chromium.org> wrote: > > On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric <dimitry at andric.com> wrote: >> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote: >>> >>> 5.0.0-rc1 has just been tagged. >>> >>> Please build, test and upload binaries
2013 Nov 21
2
[LLVMdev] Building LLVM with asan
Indeed, removing that flag works fine, the only question is why this is added in tools/llvm-shlib/Makefile in the first place then and what to do about it: ifeq ($(HOST_OS), $(filter $(HOST_OS), Linux GNU GNU/kFreeBSD)) # Don't allow unresolved symbols. LLVMLibsOptions += -Wl,--no-undefined endif On Thu, Nov 21, 2013 at 11:53 AM, Alexander Potapenko <glider at
2017 Jul 31
3
[cfe-dev] [5.0.0 Release] Release Candidate 1 tagged
On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric <dimitry at andric.com> wrote: > On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote: >> >> 5.0.0-rc1 has just been tagged. >> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. > > Built and tested rc1. Test failures on
2017 Feb 11
2
Asan self host problems: Failed to deallocate
...tizer_common/sanitizer_posix.cc:143 "(("unable to unmap" && 0)) != (0)" (0x0, 0x0) #0 0x51f42f in __asan::AsanCheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) /usr/local/google/home/blaikie/dev/llvm/src/projects/compiler-rt/lib/asan/asan_rtl.cc:69:3 #1 0x532eff in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) /usr/local/google/home/blaikie/dev/llvm/src/projects/compiler-rt/lib/sanitizer_common/sanitizer_termination.cc:79:5 #2 0x52cf61 in __sanitizer::UnmapOrDie(void*, unsigned...
2017 Feb 15
2
Asan self host problems: Failed to deallocate
...osix.cc:143 > "(("unable to unmap" && 0)) != (0)" (0x0, 0x0) > > #0 0x51f42f in __asan::AsanCheckFailed(char const*, int, char const*, > unsigned long long, unsigned long long) > /usr/local/google/home/blaikie/dev/llvm/src/projects/compiler-rt/lib/asan/asan_rtl.cc:69:3 > > #1 0x532eff in __sanitizer::CheckFailed(char const*, int, char > const*, unsigned long long, unsigned long long) > /usr/local/google/home/blaikie/dev/llvm/src/projects/compiler-rt/lib/sanitizer_common/sanitizer_termination.cc:79:5 > > #2 0x52cf61 in __sanitizer...