| /external/valgrind/main/memcheck/tests/linux/ |
| lsframe1.stderr.exp | 9 For a detailed leak analysis, rerun with: --leak-check=full
|
| lsframe2.stderr.exp | 9 For a detailed leak analysis, rerun with: --leak-check=full
|
| /external/chromium_org/content/public/test/ |
| DEPS | 6 # Ensure we don't leak internal content headers through public headers.
|
| /external/compiler-rt/lib/tsan/lit_tests/ |
| thread_leak.c | 17 // CHECK-NOT: WARNING: ThreadSanitizer: thread leak
|
| thread_leak2.c | 17 // CHECK-NOT: WARNING: ThreadSanitizer: thread leak
|
| thread_leak4.c | 18 // CHECK-NOT: WARNING: ThreadSanitizer: thread leak
|
| thread_leak5.c | 18 // CHECK: WARNING: ThreadSanitizer: thread leak
|
| /external/valgrind/main/memcheck/tests/ |
| leak-0.c | 3 #include "leak.h"
|
| custom-overlap.c | 2 // with normal malloc() blocks in leak-checking -- if it happens, we ignore
3 // the malloc() block during the leak check.
|
| describe-block.stderr.exp | 12 For a detailed leak analysis, rerun with: --leak-check=full
|
| addressable.stderr.exp | 7 For a detailed leak analysis, rerun with: --leak-check=full
36 For a detailed leak analysis, rerun with: --leak-check=full
45 For a detailed leak analysis, rerun with: --leak-check=full
59 For a detailed leak analysis, rerun with: --leak-check=full
78 For a detailed leak analysis, rerun with: --leak-check=ful
[all...] |
| /external/chromium_org/third_party/sqlite/src/test/ |
| memleak.test | 31 # grows, it may mean there is a memory leak in the library.
72 if {[info exists Leak]} {
73 lappend LeakList $Leak
77 puts -nonewline memory-leak-test-$tail...
82 fail_test memory-leak-test-$tail
91 # Run the malloc tests and the misuse test after memory leak detection.
92 # Both tests leak memory.
|
| /external/chromium/testing/gmock/test/ |
| gmock_leak_test_.cc | 35 // caught by Google Mock's leak detector.
65 // In order to test the leak detector, we deliberately leak foo.
67 // Makes sure Google Mock's leak detector can change the exit code
77 // In order to test the leak detector, we deliberately leak foo.
79 // Makes sure Google Mock's leak detector can change the exit code
92 // In order to test the leak detector, we deliberately leak foo1 and
95 // Makes sure Google Mock's leak detector can change the exit cod
[all...] |
| /external/valgrind/main/gdbserver_tests/ |
| mcleak.stderr.exp | 7 by 0x........: f (leak-delta.c:14)
8 by 0x........: main (leak-delta.c:60)
25 by 0x........: f (leak-delta.c:14)
26 by 0x........: main (leak-delta.c:60)
30 by 0x........: f (leak-delta.c:23)
31 by 0x........: main (leak-delta.c:60)
35 by 0x........: f (leak-delta.c:28)
36 by 0x........: main (leak-delta.c:60)
40 by 0x........: f (leak-delta.c:28)
41 by 0x........: main (leak-delta.c:60
[all...] |
| mcsignopass.stderr.exp | 19 For a detailed leak analysis, rerun with: --leak-check=full
|
| mcsigpass.stderr.exp | 19 For a detailed leak analysis, rerun with: --leak-check=full
|
| mcwatchpoints.stderr.exp | 24 For a detailed leak analysis, rerun with: --leak-check=full
|
| /cts/tests/tests/renderscript/src/android/renderscript/cts/ |
| LeakTest.java | 40 * The code to generate leak.bc is in the previous comment block.
52 Log.w(TAG, "Leak test iteration " + i);
53 ScriptC_leak leak = new ScriptC_leak(mRS); local
56 leak.set_a(A);
59 leak.destroy();
|
| /external/chromium_org/tools/valgrind/drmemory/ |
| suppressions_full.txt | 18 LEAK
24 LEAK
25 name=GoogleDesktop LEAK
35 # Intentional leak in WebKit Template Framework for ThreadData.
36 LEAK
37 name=intentional WTF ThreadData leak
42 LEAK
52 LEAK
87 LEAK
107 LEAK
[all...] |
| /external/clang/test/Analysis/ |
| coverage.c | 36 } // expected-warning {{Potential leak of memory pointed to by 'm'}}
43 } // expected-warning {{Potential leak of memory pointed to by 'm'}}
49 } // expected-warning {{Potential leak of memory pointed to by 'm'}}
55 } // expected-warning {{Potential leak of memory pointed to by 'm'}}
69 } // expected-warning {{Potential leak of memory pointed to by 'm'}}
81 } // expected-warning {{Potential leak of memory pointed to by 'm'}}
|
| CGColorSpace.c | 9 CGColorSpaceRef X = CGColorSpaceCreateDeviceRGB(); // expected-warning{{leak}}
|
| /external/chromium_org/third_party/tcmalloc/vendor/doc/ |
| heap_checker.html | 6 <title>Gperftools Heap Leak Checker</title>
49 <h2><a name="whole_program">Whole-program Heap Leak Checking</a></h2>
57 describing how to track down the memory leak (using <A
93 initialization, meaning you can leak some memory in your
95 and not trigger a leak message. If you frequently (and purposefully)
96 leak data in one-time global initializers, "minimal" mode is useful
100 reports a leak for any data that is not reachable via a live object
108 it, that will prompt a leak message in "strict" mode, though not in
114 not do "live object" checking at all, so it reports a leak unless
131 turn on any whole-program leak checking.</p
[all...] |
| /external/chromium_org/third_party/WebKit/ManualTests/ |
| leak-observer-nonmain-world.html | 3 <p>Test that using mutation observers from the non-main world doesn't leak the document.</p>
4 <p>Expected output of this test is LEAK: 28 WebCoreNode</p>
|
| /external/valgrind/main/memcheck/tests/darwin/ |
| env.c | 5 // This tests that the suppression for the leak in setenv() works. See bug
23 putenv("MYVAR=xxxx"); // no leak for putenv()
|
| /external/chromium_org/ppapi/tests/ |
| test_instance_deprecated.h | 24 // Leak a reference to the given var, but ignore the leak in the leak checking
|
