99 issues changed in address-sanitizer

[address-sanitizer]

Updates:
        Labels: ProjectAddressSanitizer

Comment by ramosian.gli...@gmail.com:
(No comment was entered for this change.)
Affected issues:
  issue 7: No redzones for weak symbols
    http://code.google.com/p/address-sanitizer/issues/detail?id=7

  issue 12: need to instrument thread-local globals
    http://code.google.com/p/address-sanitizer/issues/detail?id=12

  issue 16: symbolize stack traces using code from lldb
    http://code.google.com/p/address-sanitizer/issues/detail?id=16

  issue 73: Detect Use after destruction (but before free)
    http://code.google.com/p/address-sanitizer/issues/detail?id=73

  issue 78: asan needs more libc interceptors.
    http://code.google.com/p/address-sanitizer/issues/detail?id=78

  issue 79: ASan should print thread names.
    http://code.google.com/p/address-sanitizer/issues/detail?id=79

  issue 83: use @llvm.lifetime.start/end for more precise stack  
use-after-scope detection
    http://code.google.com/p/address-sanitizer/issues/detail?id=83

  issue 88: A simple ObjC program crashes in objc_msgSend
    http://code.google.com/p/address-sanitizer/issues/detail?id=88

  issue 89: ASan needs to keep track of all the libraries loaded during the  
process lifetime
    http://code.google.com/p/address-sanitizer/issues/detail?id=89

  issue 92: On mac asan_symbolize script does not symbolicate frames coming  
from a dynamic library
    http://code.google.com/p/address-sanitizer/issues/detail?id=92

  issue 97: dr asan inlined strlen false positive in libfontconfig.so
    http://code.google.com/p/address-sanitizer/issues/detail?id=97

  issue 100: find unaligned partially OOB accesses
    http://code.google.com/p/address-sanitizer/issues/detail?id=100

  issue 112: MemsetWildAddressTest fails on Android
    http://code.google.com/p/address-sanitizer/issues/detail?id=112

  issue 114: When printing report on SEGV, disassemble the faulty  
instruction and print accesses READ-or-WRITE and size
    http://code.google.com/p/address-sanitizer/issues/detail?id=114

  issue 116: Infinite recursion in the dynamic runtime on 10.8
    http://code.google.com/p/address-sanitizer/issues/detail?id=116

  issue 130: Make it possible for the users to disable checks in some  
library wrappers
    http://code.google.com/p/address-sanitizer/issues/detail?id=130

  issue 131: asan should check malloc/delete or new/free mismatch
    http://code.google.com/p/address-sanitizer/issues/detail?id=131

  issue 137: consider using _Unwind unwinder instead of fast fp-based  
unwinder as an option
    http://code.google.com/p/address-sanitizer/issues/detail?id=137

  issue 138: asan should support variable-sized alloca
    http://code.google.com/p/address-sanitizer/issues/detail?id=138

  issue 140: Custom unwinders for interpreted/jitted languages
    http://code.google.com/p/address-sanitizer/issues/detail?id=140

  issue 141: chrome, content_shell and DumpRenderTree fail to start on arm  
linux because stack unwinding during malloc recording crashes
    http://code.google.com/p/address-sanitizer/issues/detail?id=141

  issue 142: introduce the Task concept
    http://code.google.com/p/address-sanitizer/issues/detail?id=142

  issue 147: asan false positive with -static-libstdc++ and exceptions
    http://code.google.com/p/address-sanitizer/issues/detail?id=147

  issue 148: failing to intercept strdup
    http://code.google.com/p/address-sanitizer/issues/detail?id=148

  issue 164: 400.perlbench is slower than 3x with asan
    http://code.google.com/p/address-sanitizer/issues/detail?id=164

  issue 165: Allocator [v2] works badly on 32-bit archs?
    http://code.google.com/p/address-sanitizer/issues/detail?id=165

  issue 166: ignore or warn on setrlimit(RLIMIT_AS)
    http://code.google.com/p/address-sanitizer/issues/detail?id=166

  issue 177: stack depot grows uncontrollably on chrome
    http://code.google.com/p/address-sanitizer/issues/detail?id=177

  issue 181: Find destruction-order problems in ASan
    http://code.google.com/p/address-sanitizer/issues/detail?id=181

  issue 185: BuiltinLongJmpTest fails on PowerPC
    http://code.google.com/p/address-sanitizer/issues/detail?id=185

  issue 186: strict_init_order=false mode of init-order checking doesn't  
work on Darwin
    http://code.google.com/p/address-sanitizer/issues/detail?id=186

  issue 189: support swapcontext
    http://code.google.com/p/address-sanitizer/issues/detail?id=189

  issue 190: asan_symbolize.py should fall back to non-symbolized output if  
no debug info is available
    http://code.google.com/p/address-sanitizer/issues/detail?id=190

  issue 191: Show stacks for unpoison & poison
    http://code.google.com/p/address-sanitizer/issues/detail?id=191

  issue 192: Handle assembly in sanitizer tools
    http://code.google.com/p/address-sanitizer/issues/detail?id=192

  issue 194: Global constructors in asan and msan runtime
    http://code.google.com/p/address-sanitizer/issues/detail?id=194

  issue 201: Let OSX users run uninstrumented executable with preloaded  
ASan runtime
    http://code.google.com/p/address-sanitizer/issues/detail?id=201

  issue 204: NS_IsMainThread hits "heap-buffer-overflow read of size 4"  
that is "located 0 bytes inside of 4-byte region"
    http://code.google.com/p/address-sanitizer/issues/detail?id=204

  issue 210: Use statically allocated shadow on 32-bit OSX
    http://code.google.com/p/address-sanitizer/issues/detail?id=210

  issue 212: report circular dependencies in leaked circular references
    http://code.google.com/p/address-sanitizer/issues/detail?id=212

  issue 213: LeakSanitizer spends a lot of time in StackDepotGet()
    http://code.google.com/p/address-sanitizer/issues/detail?id=213

  issue 215: Find init-order-fiasco caused by template instantiations
    http://code.google.com/p/address-sanitizer/issues/detail?id=215

  issue 216: Should be able to detect stack use-after-return bugs for  
stacks of threads that have ended
    http://code.google.com/p/address-sanitizer/issues/detail?id=216

  issue 219: can we get rid of force_interface_symbols now?
    http://code.google.com/p/address-sanitizer/issues/detail?id=219

  issue 226: Revisit memcpy()/memmove() handling on OSX after we drop  
support for 10.8
    http://code.google.com/p/address-sanitizer/issues/detail?id=226

  issue 231: implement memory tracing for heap objects
    http://code.google.com/p/address-sanitizer/issues/detail?id=231

  issue 236: Prohibit building with -fsanitize=address on OSX 10.6 and  
before
    http://code.google.com/p/address-sanitizer/issues/detail?id=236

  issue 241: provide more information for unnamed temps
    http://code.google.com/p/address-sanitizer/issues/detail?id=241

  issue 244: Support pthread_setname_np
    http://code.google.com/p/address-sanitizer/issues/detail?id=244

  issue 246: Porting to a new target (AArch64)
    http://code.google.com/p/address-sanitizer/issues/detail?id=246

  issue 247: Support source fortification
    http://code.google.com/p/address-sanitizer/issues/detail?id=247

  issue 248: Intercept iconv on OSX
    http://code.google.com/p/address-sanitizer/issues/detail?id=248

  issue 249: Bad choice of aliased symbol name in symbolizer
    http://code.google.com/p/address-sanitizer/issues/detail?id=249

  issue 250: shmctl interceptor does not work in 32-bit mode
    http://code.google.com/p/address-sanitizer/issues/detail?id=250

  issue 252: DRASan fails to identify a thread
    http://code.google.com/p/address-sanitizer/issues/detail?id=252

  issue 253: Correctly handle the symbolizer pipe on fork()
    http://code.google.com/p/address-sanitizer/issues/detail?id=253

  issue 258: false negatives with throw/longjmp
    http://code.google.com/p/address-sanitizer/issues/detail?id=258

  issue 260: ASan breaks dead stripping  
(-ffunction-sections/-Wl,-gc-section on Linux, -dead_strip on OSX)
    http://code.google.com/p/address-sanitizer/issues/detail?id=260

  issue 261: pthread_get_stacksize_np() returns incorrect value on Mac OS X  
10.9
    http://code.google.com/p/address-sanitizer/issues/detail?id=261

  issue 262: Detect stack overflow in SEGV handler
    http://code.google.com/p/address-sanitizer/issues/detail?id=262

  issue 263: Android libc closes stdout/stdin/stderr before atexit()  
handlers
    http://code.google.com/p/address-sanitizer/issues/detail?id=263

  issue 265: Miscalculation of ByteMap kSize1 for small mmap ranges on  
iOS/AArch64
    http://code.google.com/p/address-sanitizer/issues/detail?id=265

  issue 269: comparison and difference on unrelated pointers
    http://code.google.com/p/address-sanitizer/issues/detail?id=269

  issue 271: cannot use ASAN w/shared-library code (JVM, JNI)
    http://code.google.com/p/address-sanitizer/issues/detail?id=271

  issue 272: Attempting double-free on IOS with SDL
    http://code.google.com/p/address-sanitizer/issues/detail?id=272

  issue 273: remove the limit of the number of ever existed threads in asan
    http://code.google.com/p/address-sanitizer/issues/detail?id=273

  issue 275: asan_symbolize.py does not work with Python3
    http://code.google.com/p/address-sanitizer/issues/detail?id=275

  issue 280: Assembly instrumentation: blacklist support
    http://code.google.com/p/address-sanitizer/issues/detail?id=280

  issue 281: Assembly instrumentation reports have non-unwindable stacks
    http://code.google.com/p/address-sanitizer/issues/detail?id=281

  issue 282: Assembly instrumentation: handle more instructions
    http://code.google.com/p/address-sanitizer/issues/detail?id=282

  issue 286: __sanitizer_sanitize functions should setup GOT pointer on i386
    http://code.google.com/p/address-sanitizer/issues/detail?id=286

  issue 287: Building on Snow Leopard without IOS support
    http://code.google.com/p/address-sanitizer/issues/detail?id=287

  issue 291: CoverSan mode
    http://code.google.com/p/address-sanitizer/issues/detail?id=291

  issue 295: make operator new more standard compliant
    http://code.google.com/p/address-sanitizer/issues/detail?id=295

  issue 298: all sanitizers need to intercept setenv/getenv
    http://code.google.com/p/address-sanitizer/issues/detail?id=298

  issue 299: asan should report line number for definitions of globals
    http://code.google.com/p/address-sanitizer/issues/detail?id=299

  issue 303: FB10/LLVM/CLANG3.5: Shadow memory range interleaves with an  
existing memory mapping. ASan cannot proceed correctly. ABORTING.
    http://code.google.com/p/address-sanitizer/issues/detail?id=303

  issue 304: make unaligned pointers handling in LSan more useful
    http://code.google.com/p/address-sanitizer/issues/detail?id=304

  issue 307: Asm instrumentation does not preserve flags
    http://code.google.com/p/address-sanitizer/issues/detail?id=307

  issue 309: Enable malloc/delete/new/free mismatch checks on Windows
    http://code.google.com/p/address-sanitizer/issues/detail?id=309

  issue 310: Stack UAR flags not working on Chromium Mac build
    http://code.google.com/p/address-sanitizer/issues/detail?id=310

  issue 311: ASAN coverage missing DTORs and inline functions
    http://code.google.com/p/address-sanitizer/issues/detail?id=311

  issue 313: [libsanitizer] Fallback to llvm-symbolizer in PATH
    http://code.google.com/p/address-sanitizer/issues/detail?id=313

  issue 314: Left OOB accesses on new[]-allocated arrays with array cookies  
are not detected
    http://code.google.com/p/address-sanitizer/issues/detail?id=314

  issue 315: LSan should be more helpful when unable to attach to threads
    http://code.google.com/p/address-sanitizer/issues/detail?id=315

  issue 316: Investigate lit test failures on Android
    http://code.google.com/p/address-sanitizer/issues/detail?id=316

  issue 318: support dlclose
    http://code.google.com/p/address-sanitizer/issues/detail?id=318

  issue 320: Unable to use asan_device_setup.sh on android
    http://code.google.com/p/address-sanitizer/issues/detail?id=320

  issue 321: CHECK failed: ... "((trace)) != (0)" (0x0, 0x0)
    http://code.google.com/p/address-sanitizer/issues/detail?id=321

  issue 322: Expose __sanitizer_symbolize_pc()
    http://code.google.com/p/address-sanitizer/issues/detail?id=322

  issue 324: Asan support for Chrome on Android
    http://code.google.com/p/address-sanitizer/issues/detail?id=324

  issue 325: Leak of size 0 reported as leak of size 1
    http://code.google.com/p/address-sanitizer/issues/detail?id=325

  issue 326: Android L regressions
    http://code.google.com/p/address-sanitizer/issues/detail?id=326

  issue 328: AddressSanitizer should support -MTd/-MDd runtimes
    http://code.google.com/p/address-sanitizer/issues/detail?id=328

  issue 329: Unable to sanitize system_server on android
    http://code.google.com/p/address-sanitizer/issues/detail?id=329

  issue 330: Support re-exec of sanitized executable with preloading  
libasan on Linux and Android
    http://code.google.com/p/address-sanitizer/issues/detail?id=330

  issue 331: Problem with opendir / fstatfs in Firefox on Mac OSX
    http://code.google.com/p/address-sanitizer/issues/detail?id=331

  issue 332: [Windows] Revisit how the RTL handles multi-module apps
    http://code.google.com/p/address-sanitizer/issues/detail?id=332

  issue 333: Incomplete ASAN trace for heap use-after-free on a temporary
    http://code.google.com/p/address-sanitizer/issues/detail?id=333



--
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 address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.