| /external/valgrind/main/docs/internals/ |
| xml-output.txt | 69 - File descriptor leak checking is disabled. This could be
72 - Maximum-detail leak checking is selected (--leak-check=full).
158 program, and the result of the final leak check. Hence the
219 that the wrapup (leak checking) is happening.
228 leak checker.
338 memory leak; the referenced blocks are definitely lost
342 memory leak; the referenced blocks are lost because all pointers
347 memory leak; only interior pointers to referenced blocks were
352 memory leak; pointers to un-freed blocks are still availabl
[all...] |
| 3_4_BUGSTATUS.txt | 37 157154 documentation (leak-resolution doc speaks about num-callers
75 188572 Valgrind on Mac should suppress setenv() mem leak
|
| /external/valgrind/main/memcheck/ |
| mc_leakcheck.c | 3 /*--- The leak checker. mc_leakcheck.c ---*/
53 /*--- An overview of leak checking. ---*/
56 // Leak-checking is a directed-graph traversal problem. The graph has
105 // --follow-interior-pointers. By default it would be off, the leak checker
150 // ==20397== by 0x400521: mk (leak-cases.c:49)
151 // ==20397== by 0x400578: main (leak-cases.c:72)
156 // ==20397== by 0x400521: mk (leak-cases.c:49)
157 // ==20397== by 0x400580: main (leak-cases.c:72)
172 // ==20397== by 0x400521: mk (leak-cases.c:49)
173 // ==20397== by 0x400580: main (leak-cases.c:72
[all...] |
| /external/clang/test/Analysis/ |
| NSString.m | 129 CFStringCreateWithFormat(kCFAllocatorDefault, 0, // expected-warning{{leak}}
205 NSString *s = [[NSString alloc] init]; // expected-warning{{leak}}
211 NSString *s = [[[NSString alloc] init] autorelease]; // expected-warning{{leak}}
222 NSString *s = [[NSString alloc] init]; // expected-warning{{leak}}
266 return [[SharedClass alloc] _init]; // expected-warning{{leak}}
346 NSString *s = [[NSString alloc] init]; // expected-warning{{leak}}
368 NSString *str = [TestIsTracked newString]; // expected-warning{{Potential leak}}
382 return CFStringCreateWithFormat(kCFAllocatorDefault, ((void*)0), ((CFStringRef) __builtin___CFStringMakeConstantString ("" "%d" "")), 100); // expected-warning{{leak}}
388 NSString *string = [[NSString stringWithFormat:@"%ld", (long) 100] retain]; // expected-warning {{leak}}
|
| /external/chromium_org/base/third_party/valgrind/ |
| memcheck.h | 185 /* Do a full memory leak check (like --leak-check=full) mid-execution. */
193 /* Do a summary memory leak check (like --leak-check=summary) mid-execution. */
202 all previous leak checks. They must be lvalues. */
224 all previous leak checks. They must be lvalues. */
|
| /external/valgrind/main/docs/xml/ |
| quick-start-guide.xml | 69 <programlisting> valgrind --leak-check=yes myprog arg1 arg2
72 <para>Memcheck is the default tool. The <option>--leak-check</option>
73 option turns on the detailed memory leak detector.</para>
86 and a memory leak.</para>
95 } // problem 2: memory leak -- x not freed
156 <para>Memory leak messages look like this:</para>
|
| /external/valgrind/main/ |
| glibc-2.2.supp | 478 Memcheck:Leak
485 Memcheck:Leak
492 Memcheck:Leak
499 Memcheck:Leak
506 Memcheck:Leak
515 Memcheck:Leak
|
| /external/chromium/chrome/browser/sync/notifier/ |
| chrome_system_resources_unittest.cc | 76 // Make sure current_time() doesn't crash or leak.
83 // Make sure Log() doesn't crash or leak.
|
| non_blocking_invalidation_notifier_unittest.cc | 46 // leak supply one here.
|
| /external/chromium/crypto/ |
| openssl_util.cc | 28 // We allow the SSL environment to leak for multiple reasons:
35 // allowing the global environment to leak at least ensures it is
|
| /external/chromium_org/crypto/ |
| openssl_util.cc | 28 // We allow the SSL environment to leak for multiple reasons:
35 // allowing the global environment to leak at least ensures it is
|
| /external/chromium_org/sync/notifier/ |
| sync_system_resources_unittest.cc | 94 // Make sure current_time() doesn't crash or leak.
101 // Make sure Log() doesn't crash or leak.
|
| /external/chromium_org/third_party/libjingle/source/talk/base/ |
| unittest_main.cc | 88 #ifdef _DEBUG // Turn on memory leak checking on Windows.
107 // clean up logging so we don't appear to leak memory.
|
| /external/clang/include/clang/Basic/ |
| Sanitizers.def | 58 SANITIZER("leak", Leak)
|
| /external/clang/unittests/AST/ |
| DeclTest.cpp | 26 // This is a regression test for a memory leak in APValues for structs that
27 // allocate memory. This test only fails if run under valgrind with full leak
|
| /external/llvm/include/llvm/Support/ |
| LeakDetector.h | 1 //===-- llvm/Support/LeakDetector.h - Provide leak detection ----*- C++ -*-===//
10 // This file defines a class that can be used to provide very simple memory leak
|
| /external/valgrind/main/drd/tests/ |
| custom_alloc.c | 61 array2 = 0; // leak
89 // leak from make_leak()
|
| /external/valgrind/main/memcheck/tests/ |
| big_blocks_freed_list.stderr.exp | 47 For a detailed leak analysis, rerun with: --leak-check=full
|
| /external/webrtc/src/system_wrappers/source/ |
| map.cc | 53 "Potential memory leak in MapWrapper");
57 // memory leak).
|
| /frameworks/base/core/tests/coretests/src/android/content/ |
| MemoryFileProviderTest.java | 49 // tests that we don't leak file descriptors or virtual address space
53 // open enough file descriptors that we will crash something if we leak FDs
|
| /cts/tests/tests/security/src/android/security/cts/ |
| CharDeviceTest.java | 37 * Detect Exynos 4xxx kernel memory leak to userspace. CVE-2012-6422.
|
| /external/chromium/chrome/browser/ui/cocoa/ |
| browser_test_helper.h | 20 // would never be deleted and would report as a leak under Valgrind. Note that
|
| /external/chromium_org/base/debug/ |
| leak_annotations.h | 19 // be annotated as a leak.
|
| /external/chromium_org/base/ |
| tools_sanity_unittest.cc | 80 // A memory leak detector should report an error in this test.
83 int* volatile leak = new int[256]; // Leak some memory intentionally. local
84 leak[4] = 1; // Make sure the allocated memory is used.
|
| /external/chromium_org/extensions/common/matcher/ |
| url_matcher_factory.h | 31 // URLMatcherFactory. Otherwise you leak memory.
|
