search for: sizeclassmap

...ome/wink/foss/llvm.3.9.0/test-msan/a [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. __sanitizer::SizeClassAllocator64<123145302310912ul, 8796093022208ul, 8ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __msan::MsanMapUnmapCallback>::AllocateBatch ( this=this at entry=0x21289a0 <__msan::allocator>, stat=stat at entry=0x2128970 <__msan::fallback_allocator_cache+109392>, c=c at entry=0x210de20 <__msan::fallback_allocator_cache>, class_id=class_id at...

First off, thanks -- this is a pretty great library and it feels like I'm learning a lot. I'm getting some more experience with libfuzzer and finding that I have a couple of questions: - How does libfuzzer decide to write a new test file? What distinguishes this one from all the other cases for which new test inputs were not written? Must be something about the path taken through the

...brian/tmp/testing/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_linux.cc:471 #2 0x0000000000447899 in GenericScopedLock (mu=mu at entry=0x640000001290, this=<synthetic pointer>) #3 __sanitizer::SizeClassAllocator64<105553116266496ul, 4398046511104ul, 0ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __asan::AsanMapUnmapCallback>::PopulateFreeList ( #4 0x0000000000447ff8 in __sanitizer::SizeClassAllocator64<105553116266496ul, 4398046511104ul, 0ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __asan::AsanMapUnmapCallback>::AllocateBatch (this=this at en...

...foss/llvm.3.9.0/test-eventfd/eventfd [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. __sanitizer::SizeClassAllocator64<123145302310912ul, 8796093022208ul, 8ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __msan::MsanMapUnmapCallback>::AllocateBatch ( this=this at entry=0x212c9a0 <__msan::allocator>, stat=stat at entry=0x212c970 <__msan::fallback_allocator_cache+109392>, c=c at entry=0x2111e20 <__msan::fallback_allocator_cache>, class_id=class_i...

...locator.cc b/lib/msan/msan_allocator.cc index b7d3947..dae6d72 100644 --- a/lib/msan/msan_allocator.cc +++ b/lib/msan/msan_allocator.cc @@ -49,7 +49,15 @@ struct MsanMapUnmapCallback { typedef SizeClassAllocator32<0, SANITIZER_MMAP_RANGE_SIZE, sizeof(Metadata), SizeClassMap, kRegionSizeLog, ByteMap, MsanMapUnmapCallback> PrimaryAllocator; - +#elif defined (__i386__) +static const uptr kMaxAllowedMallocSize = 3UL << 30; + static const uptr kRegionSizeLog = 20; + static const uptr kNumRegions = SANITIZER_MMAP_RANGE_SIZE >&gt...

I've "successfully" built 3.9.0 release but when I run "ninja check-all" I got 208 Unexpected failures: Expected Passes : 33997 Expected Failures : 198 Unsupported Tests : 685 Unexpected Failures: 208 Below is the log I captured running "time ninja check-all | tee ninja-check-all.txt" https://drive.google.com/open?id=0B-KTY7zi7eZHU2hGYTRtd01QZjA

..._state : 8; // Carry over from ASAN. Used to determine the start of user allocation. u32 from_memalign : 1; // 23 bits available // 2-nd 4 bytes // Carry over from ASAN (comment copied verbatim). // This field is used for small sizes. For large sizes it is equal to // SizeClassMap::kMaxSize and the actual size is stored in the // SecondaryAllocator's metadata. u32 user_requested_size : 29; // 3-rd 4 bytes u32 cpu_id; // Allocation cpu id // 4-th 4 bytes // Allocation timestamp in ms from a baseline timestamp computed at // the start of profiling (to...

...the start of user allocation. > > u32 from_memalign : 1; > > // 23 bits available > > > > // 2-nd 4 bytes > > // Carry over from ASAN (comment copied verbatim). > > // This field is used for small sizes. For large sizes it is equal to > > // SizeClassMap::kMaxSize and the actual size is stored in the > > // SecondaryAllocator's metadata. > > u32 user_requested_size : 29; > > > > // 3-rd 4 bytes > > u32 cpu_id; // Allocation cpu id > > > > // 4-th 4 bytes > > // Allocation timestamp in...

...mine the start of user allocation. > >   u32 from_memalign     : 1; > >   // 23 bits available > > >   // 2-nd 4 bytes > >   // Carry over from ASAN (comment copied verbatim). > >   // This field is used for small sizes. For large sizes it is equal to > >   // SizeClassMap::kMaxSize and the actual size is stored in the > >   // SecondaryAllocator's metadata. > >   u32 user_requested_size : 29; > > >   // 3-rd 4 bytes > >   u32 cpu_id; // Allocation cpu id > > >   // 4-th 4 bytes > >   // Allocation timestamp in ms from a...

...>> u32 from_memalign : 1; >> >> // 23 bits available >> >> // 2-nd 4 bytes >> >> // Carry over from ASAN (comment copied verbatim). >> >> // This field is used for small sizes. For large sizes it is equal to >> >> // SizeClassMap::kMaxSize and the actual size is stored in the >> >> // SecondaryAllocator's metadata. >> >> u32 user_requested_size : 29; >> >> // 3-rd 4 bytes >> >> u32 cpu_id; // Allocation cpu id >> >> // 4-th 4 bytes >> >>...