Updates:
        Labels: ProjectAddressSanitizer

Comment by ramosian.gli...@gmail.com:
Adding Project:AddressSanitizer as part of GitHub migration.

Affected issues:
  issue 115: Trivial program crashes with dynamic runtime on Mac
    http://code.google.com/p/address-sanitizer/issues/detail?id=115

  issue 117: _NSGetEnviron returns NULL on 10.6 with the dynamic runtime
    http://code.google.com/p/address-sanitizer/issues/detail?id=117

  issue 118: Support for memory leak detection
    http://code.google.com/p/address-sanitizer/issues/detail?id=118

  issue 119: Segmentation fault in ASan with my app
    http://code.google.com/p/address-sanitizer/issues/detail?id=119

  issue 120: ninja check-asan fails
    http://code.google.com/p/address-sanitizer/issues/detail?id=120

issue 121: Build system should create/install x86 runtime lib on x86_64 systems
    http://code.google.com/p/address-sanitizer/issues/detail?id=121

  issue 122: ASan crashes in _CFRuntimeSetInstanceTypeID on Mac OS 10.8
    http://code.google.com/p/address-sanitizer/issues/detail?id=122

  issue 123: CHECK failed: ((tsd_key_inited)) != (0) with dynamic runtime
    http://code.google.com/p/address-sanitizer/issues/detail?id=123

  issue 124: strlen() isn't replaced with the dynamic runtime on OS X
    http://code.google.com/p/address-sanitizer/issues/detail?id=124

  issue 125: AddressSanitizer isn't supported on FreeBSD
    http://code.google.com/p/address-sanitizer/issues/detail?id=125

issue 126: AddressSanitizer CHECK failed: ((name_end)) != (0)" (0x0, 0x0) in the use-after-return mode.
    http://code.google.com/p/address-sanitizer/issues/detail?id=126

  issue 127: Enable use-after-return tests on ASan bots.
    http://code.google.com/p/address-sanitizer/issues/detail?id=127

  issue 128: replace kPageSize with a non-constant.
    http://code.google.com/p/address-sanitizer/issues/detail?id=128

  issue 129: __builtin_longjmp is not supported (causing false positives)
    http://code.google.com/p/address-sanitizer/issues/detail?id=129

  issue 132: Stack realignment with dynamic allocas
    http://code.google.com/p/address-sanitizer/issues/detail?id=132

  issue 133: Let ASan unwind the stacks using CFI
    http://code.google.com/p/address-sanitizer/issues/detail?id=133

  issue 134: llvm-symbolizer should "Just Work"
    http://code.google.com/p/address-sanitizer/issues/detail?id=134

  issue 135: ASan should detect thread-hostile fork() usage
    http://code.google.com/p/address-sanitizer/issues/detail?id=135

  issue 136: unify system-dependent macros
    http://code.google.com/p/address-sanitizer/issues/detail?id=136

  issue 139: ASan should support purgeable allocations on Mac
    http://code.google.com/p/address-sanitizer/issues/detail?id=139

issue 143: [GCC] ASan: mallo.c (mallopt): fails to set malloc params with ASan enabled
    http://code.google.com/p/address-sanitizer/issues/detail?id=143

  issue 144: [GCC] fully-qualified names in ASan reports
    http://code.google.com/p/address-sanitizer/issues/detail?id=144

  issue 145: asan_symbolize.py should try to demangle C++ names
    http://code.google.com/p/address-sanitizer/issues/detail?id=145

  issue 146: asan doesn't compile on Linux with GCC 4.4
    http://code.google.com/p/address-sanitizer/issues/detail?id=146

issue 149: [Refactoring] Move large method implementations outside class definitions
    http://code.google.com/p/address-sanitizer/issues/detail?id=149

  issue 150: ASan reports sometimes contain incorrect statements
    http://code.google.com/p/address-sanitizer/issues/detail?id=150

  issue 151: Missing support for long double
    http://code.google.com/p/address-sanitizer/issues/detail?id=151

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

  issue 153: Doesn't build on Snow Leopard 0.6
    http://code.google.com/p/address-sanitizer/issues/detail?id=153

  issue 154: Doesn't build on Snow Leopard 10.6
    http://code.google.com/p/address-sanitizer/issues/detail?id=154

  issue 155: Improve the strlen reports on OOB
    http://code.google.com/p/address-sanitizer/issues/detail?id=155

  issue 156: UAF reported incorrectly
    http://code.google.com/p/address-sanitizer/issues/detail?id=156

issue 157: Error references nonexistent SHT_SYMTAB_SHNDX with -fsanitize=undefined
    http://code.google.com/p/address-sanitizer/issues/detail?id=157

  issue 158: support -Wl,--compress-debug-sections=zlib in llvm-symbolizer
    http://code.google.com/p/address-sanitizer/issues/detail?id=158

  issue 159: ASan doesn't always set DYLD_INSERT_LIBRARIES correctly on OSX
    http://code.google.com/p/address-sanitizer/issues/detail?id=159

  issue 160: qemu-arm / libsanitizer compatibility?
    http://code.google.com/p/address-sanitizer/issues/detail?id=160

  issue 161: llvm-symbolizer fails to symbolize _start
    http://code.google.com/p/address-sanitizer/issues/detail?id=161

issue 162: FastUnwindStack infinite loops occasionally on Chromium net_unittests
    http://code.google.com/p/address-sanitizer/issues/detail?id=162

  issue 163: allocator: configure the the mmap threshold at run-time
    http://code.google.com/p/address-sanitizer/issues/detail?id=163

  issue 167: binary size bloat due to duplicated stack frame descriptions
    http://code.google.com/p/address-sanitizer/issues/detail?id=167

issue 168: binary size bloat due to repetition of the file name in the description of the globals.
    http://code.google.com/p/address-sanitizer/issues/detail?id=168

  issue 169: Symbolizer should respect the .gnu_debuglink section
    http://code.google.com/p/address-sanitizer/issues/detail?id=169

issue 170: binary size bloat due to long function names in stack frame description
    http://code.google.com/p/address-sanitizer/issues/detail?id=170

issue 171: ASan should not instrument the globals in the .cstring section on OS X
    http://code.google.com/p/address-sanitizer/issues/detail?id=171

issue 172: Init-order checking is slow on binaries with huge number of globals
    http://code.google.com/p/address-sanitizer/issues/detail?id=172

  issue 173: asan_test exiting without any output on Android master ToT
    http://code.google.com/p/address-sanitizer/issues/detail?id=173

  issue 174: Colored output in "adb logcat" on Android.
    http://code.google.com/p/address-sanitizer/issues/detail?id=174

issue 175: CHECK failed: asan_fake_stack.cc:146 "((AddrIsInSizeClass(ptr, size_class))) != (0)
    http://code.google.com/p/address-sanitizer/issues/detail?id=175

issue 176: Stop using __libc_malloc and __libc_free from InternalAlloc and InternalFree
    http://code.google.com/p/address-sanitizer/issues/detail?id=176

  issue 178: Init-order checking is dlopen-hostile
    http://code.google.com/p/address-sanitizer/issues/detail?id=178

issue 179: Crash in glibc __run_exit_handlers on data allocated in calloc_memory_for_dlsyms
    http://code.google.com/p/address-sanitizer/issues/detail?id=179

  issue 180: Allow custom SIGSEGV handler on top of ASan's handler
    http://code.google.com/p/address-sanitizer/issues/detail?id=180

issue 182: Manual poisoning of mapped memory should be reseted when unmapping
    http://code.google.com/p/address-sanitizer/issues/detail?id=182

issue 183: CHECK failed while printing a stack if a memory access hits an adjacent allocation
    http://code.google.com/p/address-sanitizer/issues/detail?id=183

issue 184: false positive (or assetion) in C when mixing common and non-common globals
    http://code.google.com/p/address-sanitizer/issues/detail?id=184

  issue 187: CHECK failed when trying to realloc a freed memory block
    http://code.google.com/p/address-sanitizer/issues/detail?id=187

  issue 188: Nuke asan_intercepted_functions.h
    http://code.google.com/p/address-sanitizer/issues/detail?id=188

issue 193: Abort "attempting to call malloc_usable_size() for pointer which is not owned" with posix_memalign and malloc_usable_size
    http://code.google.com/p/address-sanitizer/issues/detail?id=193

  issue 195: Proper support for ioctl on Mac OS X
    http://code.google.com/p/address-sanitizer/issues/detail?id=195

  issue 196: Cache atos processes to make Darwin symbolication faster
    http://code.google.com/p/address-sanitizer/issues/detail?id=196

  issue 197: Symbolizer: wrap filenames in brackets
    http://code.google.com/p/address-sanitizer/issues/detail?id=197

  issue 198: main on Mac is called _main
    http://code.google.com/p/address-sanitizer/issues/detail?id=198

  issue 199: ASan should detect parameter overlaps in inlined memcpy
    http://code.google.com/p/address-sanitizer/issues/detail?id=199

  issue 200: sanitizer attributes lost due to inlining
    http://code.google.com/p/address-sanitizer/issues/detail?id=200

  issue 202: Linux Check fails pthread 32bits
    http://code.google.com/p/address-sanitizer/issues/detail?id=202

issue 203: Incorrect implementation of malloc_create_zone leading to memory corruptions
    http://code.google.com/p/address-sanitizer/issues/detail?id=203

  issue 205: Linux PTRACE_{GET,SET}REGSET may not be avaiable
    http://code.google.com/p/address-sanitizer/issues/detail?id=205

  issue 206: Build isolated non-instrumented in-process symbolizer
    http://code.google.com/p/address-sanitizer/issues/detail?id=206

  issue 207: No filename when using llvm-symbolizer with ASan on Mac
    http://code.google.com/p/address-sanitizer/issues/detail?id=207

  issue 208: OSX asanized program doesn't start
    http://code.google.com/p/address-sanitizer/issues/detail?id=208

  issue 209: [Windows] Revisit how the RTL works in the presence of DLLs
    http://code.google.com/p/address-sanitizer/issues/detail?id=209

issue 211: Report unrecognized arguments before reporting argument incompatibility
    http://code.google.com/p/address-sanitizer/issues/detail?id=211

  issue 214: __lsan_do_leak_check() causes a crash in libpulseaudio
    http://code.google.com/p/address-sanitizer/issues/detail?id=214

  issue 217: use-after-return fake stack allocator is not signal-safe
    http://code.google.com/p/address-sanitizer/issues/detail?id=217

  issue 218: Asan Chromium always shows 'aw, snap!' error windows.
    http://code.google.com/p/address-sanitizer/issues/detail?id=218

issue 220: Standalone LSan reports false positive in __sanitizer::InitTlsSize()
    http://code.google.com/p/address-sanitizer/issues/detail?id=220

  issue 221: [kernel] symbolization of modules
    http://code.google.com/p/address-sanitizer/issues/detail?id=221

issue 222: Unit tests for ASan runtime need to be statically linked with asan_*.o files
    http://code.google.com/p/address-sanitizer/issues/detail?id=222

  issue 223: No debug information on MacOS with gcc 4.8.1
    http://code.google.com/p/address-sanitizer/issues/detail?id=223

  issue 224: fix use_sigaltstack flag and consider enabling it by default.
    http://code.google.com/p/address-sanitizer/issues/detail?id=224

issue 225: False negative in init-order checker when non-dynamically initialized global is overwritten in global constructors.
    http://code.google.com/p/address-sanitizer/issues/detail?id=225

  issue 227: iossim runtime library must differ from the x86 one
    http://code.google.com/p/address-sanitizer/issues/detail?id=227

issue 228: AddressSanitizer CHECK failed on linux kernel that is patched with PaX
    http://code.google.com/p/address-sanitizer/issues/detail?id=228

  issue 229: use-after-return causes false positive leak reports
    http://code.google.com/p/address-sanitizer/issues/detail?id=229

  issue 230: LSan reports a trivial leak non-deterministically
    http://code.google.com/p/address-sanitizer/issues/detail?id=230

  issue 232: Reduce AsanThreadContext size
    http://code.google.com/p/address-sanitizer/issues/detail?id=232

  issue 233: Allocator cache is flushed in a wrong place.
    http://code.google.com/p/address-sanitizer/issues/detail?id=233

  issue 234: Incorrect implementation of atomics on ARM
    http://code.google.com/p/address-sanitizer/issues/detail?id=234

  issue 235: compiling with asan generates wrong DWARF
    http://code.google.com/p/address-sanitizer/issues/detail?id=235

  issue 237: AS requires /proc in chroot jail to function
    http://code.google.com/p/address-sanitizer/issues/detail?id=237

  issue 238: Drop support for use_stack_depot=false
    http://code.google.com/p/address-sanitizer/issues/detail?id=238

  issue 239: Do not rely on malloc context in allocator reports
    http://code.google.com/p/address-sanitizer/issues/detail?id=239

  issue 240: Detect when asan runtime is loaded twice into the same process
    http://code.google.com/p/address-sanitizer/issues/detail?id=240

  issue 242: llvm-symbolizer: implement -x flag and strip_path_prefix
    http://code.google.com/p/address-sanitizer/issues/detail?id=242

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

  issue 245: optimize asan's stack frame layout
    http://code.google.com/p/address-sanitizer/issues/detail?id=245

  issue 251: Unify symbolization in PrintStackTrace and suppression code
    http://code.google.com/p/address-sanitizer/issues/detail?id=251

issue 254: dyld: Symbol not found: ___asan_mapping_offset, when running ASanified binary
    http://code.google.com/p/address-sanitizer/issues/detail?id=254

  issue 255: Forking threads fails with clang 3.4
    http://code.google.com/p/address-sanitizer/issues/detail?id=255

  issue 256: [patch] decrease resident memory usage.
    http://code.google.com/p/address-sanitizer/issues/detail?id=256



--
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.

Reply via email to