Updates:
Labels: ProjectAddressSanitizer
Comment by [email protected]:
Adding Project:AddressSanitizer as part of GitHub migration.
Affected issues:
issue 1: Upgrade the LLVM code to avoid creating AVX instructions instead
of SSE2 instructions
http://code.google.com/p/address-sanitizer/issues/detail?id=1
issue 2: Build failed on RHEL 5.6
http://code.google.com/p/address-sanitizer/issues/detail?id=2
issue 3: globals are broken if PIC and nonPIC objects are mixed:
http://code.google.com/p/address-sanitizer/issues/detail?id=3
issue 4: Clang changes behaviour of MemIntrinsic functions before we
instrument their arguments
http://code.google.com/p/address-sanitizer/issues/detail?id=4
issue 5: ASAN fails to link programs with -O0
http://code.google.com/p/address-sanitizer/issues/detail?id=5
issue 6: clang on CentOS
http://code.google.com/p/address-sanitizer/issues/detail?id=6
issue 8: implement adaptive redzones
http://code.google.com/p/address-sanitizer/issues/detail?id=8
issue 9: Asan logo is no longer relevant
http://code.google.com/p/address-sanitizer/issues/detail?id=9
issue 10: Some programs hang because of the replaced CFAllocator
http://code.google.com/p/address-sanitizer/issues/detail?id=10
issue 11: ASan instrumentation should work with -O0
http://code.google.com/p/address-sanitizer/issues/detail?id=11
issue 13: Clang+ASan incorrectly handles exceptions.
http://code.google.com/p/address-sanitizer/issues/detail?id=13
issue 14: warn on missing blacklist, better errmsg
http://code.google.com/p/address-sanitizer/issues/detail?id=14
issue 17: Blacklist regexp errors silently lead to blacklist not working
http://code.google.com/p/address-sanitizer/issues/detail?id=17
issue 18: double-free / invalid-free errors should use Report instead of
Printf
http://code.google.com/p/address-sanitizer/issues/detail?id=18
issue 19: asan false positives caused by dlcose
http://code.google.com/p/address-sanitizer/issues/detail?id=19
issue 20: Issue with -faddress-sanitizer in combination with -Os/-O2
http://code.google.com/p/address-sanitizer/issues/detail?id=20
issue 21: ASan unittest (32-bit) fail to link with fresh googletest
http://code.google.com/p/address-sanitizer/issues/detail?id=21
issue 22: mach_override may conflict with that in the client programs
http://code.google.com/p/address-sanitizer/issues/detail?id=22
issue 23: _Unwind_Backtrace cannot unwind past wrap___cxa_throw on Mac
http://code.google.com/p/address-sanitizer/issues/detail?id=23
issue 24: slow asan start-up on Mac 64-bit
http://code.google.com/p/address-sanitizer/issues/detail?id=24
issue 25: Add -C option to addr2line to de-mangle names
http://code.google.com/p/address-sanitizer/issues/detail?id=25
issue 26: get rid of sysinfo/sysinfo.cc
http://code.google.com/p/address-sanitizer/issues/detail?id=26
issue 27: CHECK fails on linux and program doesn't launch
http://code.google.com/p/address-sanitizer/issues/detail?id=27
issue 28: clang and clang++ behave differently on a small OOB test
http://code.google.com/p/address-sanitizer/issues/detail?id=28
issue 29: Deal with ASLR on Mac OS
http://code.google.com/p/address-sanitizer/issues/detail?id=29
issue 30: can't static link against gflags
http://code.google.com/p/address-sanitizer/issues/detail?id=30
issue 31: Debugging breakpoints needed
http://code.google.com/p/address-sanitizer/issues/detail?id=31
issue 32: Doesn't compile on OSX Lion (10.7)
http://code.google.com/p/address-sanitizer/issues/detail?id=32
issue 33: ASan doesn't instrument the +load methods
http://code.google.com/p/address-sanitizer/issues/detail?id=33
issue 34: ASan incorrectly wraps memmove on OS X Lion
http://code.google.com/p/address-sanitizer/issues/detail?id=34
issue 35: GCD tests are broken on Mac OS 10.6
http://code.google.com/p/address-sanitizer/issues/detail?id=35
issue 36: ASan allows incorrect reordering of memory accesses
http://code.google.com/p/address-sanitizer/issues/detail?id=36
issue 37: ASan doesn't unpoison stack of subprocesses that share the same
memory
http://code.google.com/p/address-sanitizer/issues/detail?id=37
issue 38: crash on programs that link SenTestingKit (Apple's bundled unit
testing framework)
http://code.google.com/p/address-sanitizer/issues/detail?id=38
issue 39: Need to check that the shadow memory does not overlap with
existing mappings
http://code.google.com/p/address-sanitizer/issues/detail?id=39
issue 40: Use portable macros for printing sizes, offsets, and addresses
http://code.google.com/p/address-sanitizer/issues/detail?id=40
issue 41: debug info problems
http://code.google.com/p/address-sanitizer/issues/detail?id=41
issue 42: __asan_handle_no_return undefined in lib for i386
http://code.google.com/p/address-sanitizer/issues/detail?id=42
issue 43: ASan requires /MTd linking on Windows
http://code.google.com/p/address-sanitizer/issues/detail?id=43
issue 44: AsanStackTrace::FastUnwindStack reads wild addresses
http://code.google.com/p/address-sanitizer/issues/detail?id=44
issue 45: compilation hangs with -faddress-sanitizer
http://code.google.com/p/address-sanitizer/issues/detail?id=45
issue 46: asan fails to unwind from memcmp
http://code.google.com/p/address-sanitizer/issues/detail?id=46
issue 47: RFC: ForkSanitizer
http://code.google.com/p/address-sanitizer/issues/detail?id=47
issue 48: [Windows] Clang doesn't give us debug info
http://code.google.com/p/address-sanitizer/issues/detail?id=48
issue 49: [Windows] Reports on global OOB accesses are not well tested yet
http://code.google.com/p/address-sanitizer/issues/detail?id=49
issue 50: To analyze: 464.h264ref OOBs under ASan on Windows
http://code.google.com/p/address-sanitizer/issues/detail?id=50
issue 51: AddressSanitizerInterface.GetOwnershipStressTest is very slow
on Mac
http://code.google.com/p/address-sanitizer/issues/detail?id=51
issue 52: [Windows] Can't create more than ~23K threads under ASan
http://code.google.com/p/address-sanitizer/issues/detail?id=52
issue 53: libxpc is corrupting ASan flags on Mac OS 10.7
http://code.google.com/p/address-sanitizer/issues/detail?id=53
issue 54: mach_override should check it hasn't wrapped the function yet
http://code.google.com/p/address-sanitizer/issues/detail?id=54
issue 55: [Windows] Clang++ support
http://code.google.com/p/address-sanitizer/issues/detail?id=55
issue 56: [Windows] Clang++ support
http://code.google.com/p/address-sanitizer/issues/detail?id=56
issue 57: CHECK failure on racy double-free
http://code.google.com/p/address-sanitizer/issues/detail?id=57
issue 58: asan crashes in jni
http://code.google.com/p/address-sanitizer/issues/detail?id=58
issue 59: Need to build the runtime library with -ffreestanding
http://code.google.com/p/address-sanitizer/issues/detail?id=59
issue 60: ASan should detect stack overflows
http://code.google.com/p/address-sanitizer/issues/detail?id=60
issue 61: Clang can't build NaCl decoder with -O1 and ASan enabled
http://code.google.com/p/address-sanitizer/issues/detail?id=61
issue 62: Slightly inefficient instrumentation of 1-byte accesses:
http://code.google.com/p/address-sanitizer/issues/detail?id=62
issue 63: ASan doesn't play well with vmmap on OS X 10.7
http://code.google.com/p/address-sanitizer/issues/detail?id=63
issue 64: We need to use library interposition instead of mach_override
on Mac OS.
http://code.google.com/p/address-sanitizer/issues/detail?id=64
issue 65: Need to agree on the behavior of SEGV handlers in ASan,
Chromium and NaCl
http://code.google.com/p/address-sanitizer/issues/detail?id=65
issue 66: "heap-use-after-free" is printed for buffer overflow bugs.
http://code.google.com/p/address-sanitizer/issues/detail?id=66
issue 67: Assertion failed: (isa<X>(Val) && "cast<Ty>() argument of
incompatible type!")
http://code.google.com/p/address-sanitizer/issues/detail?id=67
issue 68: quadratic compile time due to llvm::SpillPlacement::addLinks
http://code.google.com/p/address-sanitizer/issues/detail?id=68
issue 69: quadratic build time due to llvm::SpillPlacement::addLinks
http://code.google.com/p/address-sanitizer/issues/detail?id=69
issue 70: [OSX] Sometimes malloc is replaced but free is not
http://code.google.com/p/address-sanitizer/issues/detail?id=70
issue 71: Unable to detect the Dangling pointer reference for the
stacked variables...
http://code.google.com/p/address-sanitizer/issues/detail?id=71
issue 72: Sort out the dl_iterate_phdr code on Linux.
http://code.google.com/p/address-sanitizer/issues/detail?id=72
issue 74: asan should instrument rmw and cmpxchg
http://code.google.com/p/address-sanitizer/issues/detail?id=74
issue 75: asan should instrument calls via pointer
http://code.google.com/p/address-sanitizer/issues/detail?id=75
issue 76: std:size_t => std::size_t
http://code.google.com/p/address-sanitizer/issues/detail?id=76
issue 77: AddressSanitizerInterface.GetOwnershipStressTest affects the
run-time of other tests
http://code.google.com/p/address-sanitizer/issues/detail?id=77
issue 80: Hybrid tools need to be able to identify compiler instrumented
code
http://code.google.com/p/address-sanitizer/issues/detail?id=80
issue 81: CFAllocatorSetDefault is per-thread
http://code.google.com/p/address-sanitizer/issues/detail?id=81
issue 82: AddrIsAlignedByGranularity CHECK fails
http://code.google.com/p/address-sanitizer/issues/detail?id=82
issue 84: Non support for OSX Leopard (10.5)
http://code.google.com/p/address-sanitizer/issues/detail?id=84
issue 85: ASAN build binaries on fedora-17 x86_64 segfault
http://code.google.com/p/address-sanitizer/issues/detail?id=85
issue 86: AddressSanitizerInterface.GetAllocatedSizeAndOwnershipTest is
flaky
http://code.google.com/p/address-sanitizer/issues/detail?id=86
issue 87: CFRelease(kCFAllocatorSystemDefault) fails within __asan_init()
http://code.google.com/p/address-sanitizer/issues/detail?id=87
issue 90: ASan does not play well with the seccomp sandbox on Linux
http://code.google.com/p/address-sanitizer/issues/detail?id=90
issue 91: Symbolicated trace is sometimes off by one on Mac
http://code.google.com/p/address-sanitizer/issues/detail?id=91
issue 93: Investigate occasional "WTF? should_instrument_==false in
event_basic_block, module=`/lib/ld-2.11.1.so`" messages when running DRT
on "full DRASan"
http://code.google.com/p/address-sanitizer/issues/detail?id=93
issue 94: asan_interceptors.cc: strncmp does not call
ENSURE_ASAN_INITED();
http://code.google.com/p/address-sanitizer/issues/detail?id=94
issue 95: Trouble to compile Firefox/ASan on Mountain Lion
http://code.google.com/p/address-sanitizer/issues/detail?id=95
issue 96: AddressSanitizer.StrCatOOBTest fails on Mountain Lion
http://code.google.com/p/address-sanitizer/issues/detail?id=96
issue 98: -faddress-sanitizer causes program with large stack variable to
segfault
http://code.google.com/p/address-sanitizer/issues/detail?id=98
issue 99: mz_free is called for non-allocated memory in Chromium tests
http://code.google.com/p/address-sanitizer/issues/detail?id=99
issue 101: find unaligned partially OOB accesses
http://code.google.com/p/address-sanitizer/issues/detail?id=101
issue 102: [Windows] malloc_uaf_crash is unstable on bot
http://code.google.com/p/address-sanitizer/issues/detail?id=102
issue 103: dispatch_sync() does not serialize when using asan
http://code.google.com/p/address-sanitizer/issues/detail?id=103
issue 104: Support RTL linked to both .exe and .dll
http://code.google.com/p/address-sanitizer/issues/detail?id=104
issue 105: -faddress-sanitizer doesn't work when used on ninja
http://code.google.com/p/address-sanitizer/issues/detail?id=105
issue 106: ASan doesn't play well with the seccomp-bpf sandbox (check
failed: proc_self_maps_buff_len_)
http://code.google.com/p/address-sanitizer/issues/detail?id=106
issue 107: ReserveShadowMemoryRange failed
http://code.google.com/p/address-sanitizer/issues/detail?id=107
issue 108: asan should intercept printf family of functions and report
unaddressable accesses to params
http://code.google.com/p/address-sanitizer/issues/detail?id=108
issue 109: mstats() crashes under ASan
http://code.google.com/p/address-sanitizer/issues/detail?id=109
issue 110: Slow compilation of ASan unittests in CMake debug build
http://code.google.com/p/address-sanitizer/issues/detail?id=110
issue 111: error: undefined reference to '__asan_report_load4' (firefox
3.6 / ubuntu / 32bit
http://code.google.com/p/address-sanitizer/issues/detail?id=111
issue 113: Chrome base_unittests do not work with the dynamic runtime
http://code.google.com/p/address-sanitizer/issues/detail?id=113
--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
