Updates:
Labels: ProjectAddressSanitizer
Comment by ramosian.gli...@gmail.com:
Adding Project:AddressSanitizer as part of GitHub migration.
Affected issues:
issue 334: ASan doesn't print stats after an LSan report
http://code.google.com/p/address-sanitizer/issues/detail?id=334
issue 335: ASan with online symbolizer sometimes produces mangled
function names
http://code.google.com/p/address-sanitizer/issues/detail?id=335
issue 339: ASAN and interaction with GNU Smalltalk JIT
http://code.google.com/p/address-sanitizer/issues/detail?id=339
issue 340: FAIL: c-c++-common/asan/misalign-[12].c after r213807 on
x86_64-apple-darwin13 with -m32
http://code.google.com/p/address-sanitizer/issues/detail?id=340
issue 341: Remove the (A|M|T|L)SAN_SYMBOLIZER_PATH env variables
http://code.google.com/p/address-sanitizer/issues/detail?id=341
issue 342: Segfault in instrumented programs that use GNU indirect
functions.
http://code.google.com/p/address-sanitizer/issues/detail?id=342
issue 343: asan_symbolize.py sometimes omits newlines in stack traces
http://code.google.com/p/address-sanitizer/issues/detail?id=343
issue 345: Use Linux madvise(MADV_DONTDUMP) to exclude ASan shadow
regions from core dumps
http://code.google.com/p/address-sanitizer/issues/detail?id=345
issue 346: moar string interceptors: strstr, strcasestr, strcspn, strpbrk
http://code.google.com/p/address-sanitizer/issues/detail?id=346
issue 348: asan does not always detect access beyond mmaped page
http://code.google.com/p/address-sanitizer/issues/detail?id=348
issue 349: [AArch64] Fix kernel_old_Xid_t type
http://code.google.com/p/address-sanitizer/issues/detail?id=349
issue 350: LLVM sanitizer-bootstrap bot failing
http://code.google.com/p/address-sanitizer/issues/detail?id=350
issue 351: adb randomly hangs on sanitizer-x86_64-linux bot
http://code.google.com/p/address-sanitizer/issues/detail?id=351
issue 352: False negative related to atomic operations
http://code.google.com/p/address-sanitizer/issues/detail?id=352
issue 353: Assembly instrumentation fails on Android-x86
http://code.google.com/p/address-sanitizer/issues/detail?id=353
issue 354: Handle memory accesses in intrinsics
http://code.google.com/p/address-sanitizer/issues/detail?id=354
issue 356: can not mask function in closed source library
http://code.google.com/p/address-sanitizer/issues/detail?id=356
issue 359: Address sanitizer uses a larger stack size than
sysconf(_SC_THREAD_STACK_MIN)
http://code.google.com/p/address-sanitizer/issues/detail?id=359
issue 361: CHECK failed (assert() tls + stack) on Linux in 32bit threaded
http://code.google.com/p/address-sanitizer/issues/detail?id=361
issue 362: Container-overflow false positive with uninstrumented code
http://code.google.com/p/address-sanitizer/issues/detail?id=362
issue 365: On OS X when not re-execing, ASan overwrites already used
memory
http://code.google.com/p/address-sanitizer/issues/detail?id=365
issue 370: Kernel compilation error when using KSAN
http://code.google.com/p/address-sanitizer/issues/detail?id=370
issue 371: Asan should check for overlapping strings in sprintf
http://code.google.com/p/address-sanitizer/issues/detail?id=371
issue 372: 2to3 dies on Clang 3.5's asan_symbolize.py
http://code.google.com/p/address-sanitizer/issues/detail?id=372
issue 373: LeakSanitizer fails to detect an "obvious" leak
http://code.google.com/p/address-sanitizer/issues/detail?id=373
issue 374: AddressSanitizer does not catch "obvious" bugs
http://code.google.com/p/address-sanitizer/issues/detail?id=374
issue 375: On OS X, stacktraces are broken after a report is printed
http://code.google.com/p/address-sanitizer/issues/detail?id=375
issue 376: Missing unwind directives internal_clone may cause segfaults
in slow unwinder
http://code.google.com/p/address-sanitizer/issues/detail?id=376
issue 377: unknown-crash with annotate_contiguous_container
http://code.google.com/p/address-sanitizer/issues/detail?id=377
issue 379: Leak sanitizer support for Android on arm64
http://code.google.com/p/address-sanitizer/issues/detail?id=379
issue 380: link error when LDFLAGS has -Wl,--no-undefined
http://code.google.com/p/address-sanitizer/issues/detail?id=380
issue 381: intercept strtod and friends
http://code.google.com/p/address-sanitizer/issues/detail?id=381
issue 382: main thread's pthread destructors don't run before leak
checker, when in gdb
http://code.google.com/p/address-sanitizer/issues/detail?id=382
issue 383: No redzone created before first global
http://code.google.com/p/address-sanitizer/issues/detail?id=383
issue 384: Avoid remounting system partition on Android
http://code.google.com/p/address-sanitizer/issues/detail?id=384
issue 390: Compiling with AddressSanitizer using gcc ≥4.9 breaks printng
some variables in gdb on Linux
http://code.google.com/p/address-sanitizer/issues/detail?id=390
issue 391: AddressSanitizer: while reporting a bug found another one.
Ignoring.
http://code.google.com/p/address-sanitizer/issues/detail?id=391
issue 392: [android] system property access from native code is going away
http://code.google.com/p/address-sanitizer/issues/detail?id=392
issue 393: Link libasan with -z interpose on Linux
http://code.google.com/p/address-sanitizer/issues/detail?id=393
issue 396: Support Android in asan_symbolize
http://code.google.com/p/address-sanitizer/issues/detail?id=396
issue 398: Crash on ODR between instrumented and non-instrumented
libraries
http://code.google.com/p/address-sanitizer/issues/detail?id=398
issue 400: Improve wild-free detection
http://code.google.com/p/address-sanitizer/issues/detail?id=400
issue 402: -fsanitize=address should probably imply -Bsymbolic
http://code.google.com/p/address-sanitizer/issues/detail?id=402
--
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.
