| /external/compiler-rt/test/lsan/TestCases/ |
| suppressions_default.cc | 28 // CHECK: SUMMARY: {{(Leak|Address)}}Sanitizer: 1337 byte(s) leaked in 1 allocation(s)
|
| register_root_region.cc | 32 // CHECK: SUMMARY: {{(Leak|Address)}}Sanitizer: 1337 byte(s) leaked in 1 allocation(s)
|
| /external/jemalloc/msvc/projects/vc2015/test_threads/ |
| test_threads.cpp | 82 size_t leaked = allocated2 - allocated1; local
83 printf("\nDone. Leaked: %zd bytes\n", leaked);
84 bool failed = leaked > 65536; // in case C++ runtime allocated something (e.g. iostream locale or facet)
|
| /prebuilts/go/darwin-x86/misc/cgo/test/ |
| issue8517_windows.go | 38 t.Fatalf("too many handles leaked: issue8517counter=%v c1=%v c2=%v", issue8517counter, c1, c2)
|
| /prebuilts/go/linux-x86/misc/cgo/test/ |
| issue8517_windows.go | 38 t.Fatalf("too many handles leaked: issue8517counter=%v c1=%v c2=%v", issue8517counter, c1, c2)
|
| /external/valgrind/memcheck/ |
| memcheck.h | 194 which there was an increase in leaked bytes or leaked nr of blocks
201 increased or decreased leaked bytes/blocks since previous leak
212 /* Return number of leaked, dubious, reachable and suppressed bytes found by
214 #define VALGRIND_COUNT_LEAKS(leaked, dubious, reachable, suppressed) \
217 specified, which works no matter what type 'leaked', 'dubious', etc
228 leaked = _qzz_leaked; \
234 /* Return number of leaked, dubious, reachable and suppressed bytes found by
236 #define VALGRIND_COUNT_LEAK_BLOCKS(leaked, dubious, reachable, suppressed) \
239 specified, which works no matter what type 'leaked', 'dubious', et
[all...] |
| /external/webrtc/webrtc/base/ |
| iosfilesystem.mm | 35 // Return a (leaked) copy of a directory name suitable for application data.
43 // Return a (leaked) copy of a directory name suitable for use as a $TEMP.
|
| /system/core/libmemunreachable/ |
| LeakFolding.h | 41 bool Leaked(allocator::vector<Leak>& leaked, size_t* num_leaks_out, size_t* leak_bytes_out);
|
| README.md | 8 In the default (zero-overhead) mode, the returned data on leaks is limited to the address, approximate (upper bound) size, and the the first 32 bytes of the contents of the leaked allocation. If malloc_debug backtraces are enabled they will be included in the leak information, but backtracing allocations requires significant overhead.
18 Writes a description of leaked memory to the log. A summary is always written, followed by details of up to `limit` leaks. If `log_contents` is `true`, details include up to 32 bytes of the contents of each leaked allocation.
30 Returns a description of leaked memory. A summary is always written, followed by details of up to `limit` leaks. If `log_contents` is `true`, details include up to 32 bytes of the contents of each leaked allocation.
|
| HeapWalker.cpp | 119 bool HeapWalker::Leaked(allocator::vector<Range>& leaked, size_t limit, size_t* num_leaks_out,
121 leaked.clear();
136 leaked.push_back(it->first);
|
| /external/valgrind/memcheck/tests/ |
| leak_cpp_interior.stderr.exp | 34 To see details of leaked memory, give 'full' arg to leak_check
46 To see details of leaked memory, give 'full' arg to leak_check
58 To see details of leaked memory, give 'full' arg to leak_check
70 To see details of leaked memory, give 'full' arg to leak_check
84 To see details of leaked memory, give 'full' arg to leak_check
98 To see details of leaked memory, give 'full' arg to leak_check
112 To see details of leaked memory, give 'full' arg to leak_check
|
| leak_cpp_interior.stderr.exp-64bit | 34 To see details of leaked memory, give 'full' arg to leak_check
46 To see details of leaked memory, give 'full' arg to leak_check
58 To see details of leaked memory, give 'full' arg to leak_check
70 To see details of leaked memory, give 'full' arg to leak_check
84 To see details of leaked memory, give 'full' arg to leak_check
98 To see details of leaked memory, give 'full' arg to leak_check
112 To see details of leaked memory, give 'full' arg to leak_check
|
| leak_cpp_interior.stderr.exp-64bit-solaris | 34 To see details of leaked memory, give 'full' arg to leak_check
46 To see details of leaked memory, give 'full' arg to leak_check
58 To see details of leaked memory, give 'full' arg to leak_check
70 To see details of leaked memory, give 'full' arg to leak_check
84 To see details of leaked memory, give 'full' arg to leak_check
98 To see details of leaked memory, give 'full' arg to leak_check
112 To see details of leaked memory, give 'full' arg to leak_check
|
| leak_cpp_interior.stderr.exp-solaris | 34 To see details of leaked memory, give 'full' arg to leak_check
46 To see details of leaked memory, give 'full' arg to leak_check
58 To see details of leaked memory, give 'full' arg to leak_check
70 To see details of leaked memory, give 'full' arg to leak_check
84 To see details of leaked memory, give 'full' arg to leak_check
98 To see details of leaked memory, give 'full' arg to leak_check
112 To see details of leaked memory, give 'full' arg to leak_check
|
| leak-tree.stderr.exp | 0 leaked: 64 bytes in 4 blocks
|
| /cts/hostsidetests/security/securityPatch/CVE-2016-2460/ |
| poc.cpp | 66 ALOGE("IGraphicBufferProducer_InfoLeak leaked data = 0x%08x",
70 ALOGE("IGraphicBufferProducer_Info is Leaked");
|
| /external/clang/docs/ |
| LeakSanitizer.rst | 30 p = 0; // The memory is leaked here.
39 SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).
|
| /external/libchrome/base/third_party/valgrind/ |
| memcheck.h | 203 /* Return number of leaked, dubious, reachable and suppressed bytes found by
205 #define VALGRIND_COUNT_LEAKS(leaked, dubious, reachable, suppressed) \
208 specified, which works no matter what type 'leaked', 'dubious', etc
219 leaked = _qzz_leaked; \
225 /* Return number of leaked, dubious, reachable and suppressed bytes found by
227 #define VALGRIND_COUNT_LEAK_BLOCKS(leaked, dubious, reachable, suppressed) \
230 specified, which works no matter what type 'leaked', 'dubious', etc
241 leaked = _qzz_leaked; \
|
| /external/libchrome/base/threading/ |
| post_task_and_reply_impl.cc | 27 // leaked. Leaking is considered preferable to having a thread-safetey
86 // side though, it is intentionally leaked if the |task| doesn't complete
|
| /external/linux-kselftest/tools/testing/selftests/powerpc/tm/ |
| tm-vmxcopy.c | 8 * See if the altivec state is leaked out of an aborted transaction due to
88 printf("FAILED: vector state leaked on abort %f != %f\n",
|
| /cts/hostsidetests/security/securityPatch/CVE-2017-0334/ |
| poc.c | 39 printf("Leaked ptr is %p\n", open_args.context);
|
| /cts/hostsidetests/security/src/android/security/cts/ |
| Poc16_05.java | 32 assertNotMatches("[\\s\\n\\S]*IGraphicBufferProducer_Info is Leaked[\\s\\n\\S]*", logcat);
|
| /external/autotest/frontend/afe/ |
| readonly_connection.py | 9 # connections get leaked, which will lead to Django not cleaning them up
|
| /external/v8/src/inspector/ |
| v8-injected-script-host.h | 16 // a reference to the InjectedScriptHost may be leaked to the page being
|
| /hardware/libhardware_legacy/include/hardware_legacy/ |
| wifi_config.h | 26 // statistics like average the TSF offset or average number of frame leaked
|
