Updates:
Labels: ProjectAddressSanitizer
Comment by ramosian.gli...@gmail.com:
Adding Project:AddressSanitizer as part of GitHub migration.
Affected issues:
issue 257: lsan false positive with new T[0]
http://code.google.com/p/address-sanitizer/issues/detail?id=257
issue 259: shmctl() interceptor assumes wrong size for written data
http://code.google.com/p/address-sanitizer/issues/detail?id=259
issue 264: Symbolization of globals is broken on Android
http://code.google.com/p/address-sanitizer/issues/detail?id=264
issue 266: No longer need -undefined dynamic_lookup in Darwin ASAN
runtime library LDFLAGS
http://code.google.com/p/address-sanitizer/issues/detail?id=266
issue 267: getShadowMapping is hard to extend for new platforms
http://code.google.com/p/address-sanitizer/issues/detail?id=267
issue 268: Machine-readable error reports
http://code.google.com/p/address-sanitizer/issues/detail?id=268
issue 270: llvm-symbolizer fails to symbolize frames in a stripped library
http://code.google.com/p/address-sanitizer/issues/detail?id=270
issue 274: Incorrect shadow values for global string constants on OSX
http://code.google.com/p/address-sanitizer/issues/detail?id=274
issue 276: Add optional support for dynamic runtime
http://code.google.com/p/address-sanitizer/issues/detail?id=276
issue 277: function-sections-are-bad.cc fails on 32-bit platforms
http://code.google.com/p/address-sanitizer/issues/detail?id=277
issue 278: Do not sanitize kernel area on 32-bit targets
http://code.google.com/p/address-sanitizer/issues/detail?id=278
issue 279: Programs with __attribute__((annotate)) fail to link under
AddressSanitizer
http://code.google.com/p/address-sanitizer/issues/detail?id=279
issue 283: __aeabi_memcpy and friends are not intercepted
http://code.google.com/p/address-sanitizer/issues/detail?id=283
issue 284: Use LIKELY/UNLIKELY macros more aggressively
http://code.google.com/p/address-sanitizer/issues/detail?id=284
issue 285: Non-portable test
http://code.google.com/p/address-sanitizer/issues/detail?id=285
issue 288: kasan: poor performance due to stack trace collection
instrumentation
http://code.google.com/p/address-sanitizer/issues/detail?id=288
issue 289: kasan: instrumentation of atomic operations
http://code.google.com/p/address-sanitizer/issues/detail?id=289
issue 290: Sanitizers should check memory accesses in inline asm
http://code.google.com/p/address-sanitizer/issues/detail?id=290
issue 292: Shadow memory has big footprint of large virtual memory.
http://code.google.com/p/address-sanitizer/issues/detail?id=292
issue 293: modify asan/etc test infrastructure so that some lit tests can
be run under all sanitizers
http://code.google.com/p/address-sanitizer/issues/detail?id=293
issue 294: Port LSan to arm
http://code.google.com/p/address-sanitizer/issues/detail?id=294
issue 296: AsanThreadLocalMallocStorage is unnecessarily large
http://code.google.com/p/address-sanitizer/issues/detail?id=296
issue 297: pthread_cond_init interceptor fails
http://code.google.com/p/address-sanitizer/issues/detail?id=297
issue 300: llvm-symbolizer does not see inlined functions
http://code.google.com/p/address-sanitizer/issues/detail?id=300
issue 301: Support %lc in the printf wrapper
http://code.google.com/p/address-sanitizer/issues/detail?id=301
issue 302: Add ability to forward SEGVs to ASAN handler
http://code.google.com/p/address-sanitizer/issues/detail?id=302
issue 305: ASan shouldn't instrument globals defined in ".CRT*$*" sections
http://code.google.com/p/address-sanitizer/issues/detail?id=305
issue 306: asan deadlock in ScopedInErrorReport destructor when
print_stats=1
http://code.google.com/p/address-sanitizer/issues/detail?id=306
issue 308: 32-bit tests broken in trunk
http://code.google.com/p/address-sanitizer/issues/detail?id=308
issue 312: segfault when creating more than 256 threads
http://code.google.com/p/address-sanitizer/issues/detail?id=312
issue 317: -fsanitize=address doesn't detect simple stack access violation
http://code.google.com/p/address-sanitizer/issues/detail?id=317
issue 319: Add LSan option to display suppressions used even when no
leaks are detected
http://code.google.com/p/address-sanitizer/issues/detail?id=319
issue 327: CHECK failed error in pdfium_test binary
http://code.google.com/p/address-sanitizer/issues/detail?id=327
issue 336: zero_page_pc.cc fails on Android
http://code.google.com/p/address-sanitizer/issues/detail?id=336
issue 337: Problems with C11's aligned_alloc?
http://code.google.com/p/address-sanitizer/issues/detail?id=337
issue 338: Need option for coverage files directory
http://code.google.com/p/address-sanitizer/issues/detail?id=338
issue 344: Clang driver incorrectly handles -Wl,-r flag
http://code.google.com/p/address-sanitizer/issues/detail?id=344
issue 347: asan does not detect stack buffer overflow for alloca(const)
http://code.google.com/p/address-sanitizer/issues/detail?id=347
issue 355: Address-sanitizer reports false global-buffer-overflow
http://code.google.com/p/address-sanitizer/issues/detail?id=355
issue 357: Uninstrumented linked-only executables fail to initialize ASan
before main
http://code.google.com/p/address-sanitizer/issues/detail?id=357
issue 358: A number of ASan tests fail in UAR mode
http://code.google.com/p/address-sanitizer/issues/detail?id=358
issue 360: Using Obj-C blocks triggers a false-positive ODR violation
http://code.google.com/p/address-sanitizer/issues/detail?id=360
issue 363: Mixing instrumented and non-instrumented runtime initializers
can cause segfaults
http://code.google.com/p/address-sanitizer/issues/detail?id=363
issue 364: Extend activation flags limit
http://code.google.com/p/address-sanitizer/issues/detail?id=364
issue 366: x86 android: no static intermediates
http://code.google.com/p/address-sanitizer/issues/detail?id=366
issue 367: sanitizer prevents linking, tons of undefined references
http://code.google.com/p/address-sanitizer/issues/detail?id=367
issue 368: kMaxNumberOfAddressRanges can be too small on OS X when
loading code at runtime with NSLinkModule
http://code.google.com/p/address-sanitizer/issues/detail?id=368
issue 369: asan should handle SIGBUS on Linux
http://code.google.com/p/address-sanitizer/issues/detail?id=369
issue 378: Tests shared between asan/tsan/msan/lsan
http://code.google.com/p/address-sanitizer/issues/detail?id=378
issue 385: Whitespace difference between asan and msan outputs
http://code.google.com/p/address-sanitizer/issues/detail?id=385
issue 386: JNI-based app fails with shadow memory range interleaves with
existing memory mapping after ASan instrumentation
http://code.google.com/p/address-sanitizer/issues/detail?id=386
issue 387: Wrong base address calculation for stripped Android libraries
http://code.google.com/p/address-sanitizer/issues/detail?id=387
issue 388: ASan shared runtime library on Android re-exports the entire
libgcc interface
http://code.google.com/p/address-sanitizer/issues/detail?id=388
issue 389: sigsegv in basic block tracer
http://code.google.com/p/address-sanitizer/issues/detail?id=389
issue 394: ASan is unable to link TLS arrays
http://code.google.com/p/address-sanitizer/issues/detail?id=394
issue 395: pointer not owned error when calling malloc_usable_size() on
array of structs with destructors
http://code.google.com/p/address-sanitizer/issues/detail?id=395
issue 397: thread_stats.malloced_by_size[class_id] overflow in
asan_allocator.cc
http://code.google.com/p/address-sanitizer/issues/detail?id=397
issue 399: LSan doesn't work with empty suppressions list
http://code.google.com/p/address-sanitizer/issues/detail?id=399
issue 401: Please tell us where you are moving due to Google Code shutdown
http://code.google.com/p/address-sanitizer/issues/detail?id=401
--
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.
