| /external/valgrind/main/memcheck/tests/ |
| leak-0.stderr.exp | 0 leaked: 0 bytes in 0 blocks
|
| leak-cases-summary.stderr.exp | 0 leaked: 80 bytes in 5 blocks
|
| error_counts.stderr.exp | 7 leaked: 0 bytes in 0 blocks
14 leaked: 77 bytes in 1 blocks
|
| filter_leak_cases_possible | 4 sed -e 's/^leaked.*$//' -e 's/^dubious.*$//' -e 's/^reachable.*$//' -e 's/^suppressed:.*$//'
8 sed -e 's/^leaked.*$//' -e 's/^dubious.*$//' -e 's/^reachable.*$//' -e 's/^suppressed:.*$//'
|
| leak-0.c | 6 // Live 0-sized blocks were being reported as leaked.
|
| error_counts.c | 13 int* leaked __attribute__((unused)); local
43 leaked = malloc(77);
44 leaked = 0;
|
| leak-tree.c | 40 // help avoid leaving pointers on the stack to supposedly-leaked blocks.
43 t->r = mk(); // C (48(16d,32i)/1 definitely leaked from here)
44 t->l->l = mk(); // D (16/1 definitely leaked from here)
|
| leak-tree.stderr.exp | 0 leaked: 64 bytes in 4 blocks
|
| leak-cycle.stderr.exp | 0 leaked: 288 bytes in 18 blocks
|
| leak.h | 34 fprintf(where,"leaked: %3ld bytes in %2ld blocks\n", \
|
| /external/valgrind/main/memcheck/tests/darwin/ |
| env.c | 14 setenv("MYVAR", val1, /*overwrite*/0); // makes a copy which is later leaked
17 setenv("MYVAR", val2, /*overwrite*/1); // makes a copy which is later leaked
|
| /external/webkit/Source/WebCore/platform/win/ |
| GDIObjectCounter.cpp | 62 int leaked = m_endCount - m_startCount; local
63 if (leaked != 0)
64 LOG(PlatformLeaks, "%s: leaked %d GDI object%s!", m_identifier.latin1().data(), leaked, leaked == 1 ? "" : "s");
|
| /external/valgrind/main/memcheck/ |
| memcheck.h | 191 which there was an increase in leaked bytes or leaked nr of blocks
198 increased or decreased leaked bytes/blocks since previous leak
209 /* Return number of leaked, dubious, reachable and suppressed bytes found by
211 #define VALGRIND_COUNT_LEAKS(leaked, dubious, reachable, suppressed) \
214 specified, which works no matter what type 'leaked', 'dubious', etc
225 leaked = _qzz_leaked; \
231 /* Return number of leaked, dubious, reachable and suppressed bytes found by
233 #define VALGRIND_COUNT_LEAK_BLOCKS(leaked, dubious, reachable, suppressed) \
236 specified, which works no matter what type 'leaked', 'dubious', et
[all...] |
| /external/dbus/tools/ |
| dbus-cleanup-sockets.1 | 33 dbus-cleanup-sockets in a cron job to mop up any leaked sockets.
34 Or you can just ignore the leaked sockets, they aren't really hurting
|
| /external/chromium/base/debug/ |
| leak_tracker.h | 42 // then the allocation callstack for each leaked instances is dumped to
95 LOG_STREAM(ERROR) << "Leaked " << node << " which was allocated by:";
|
| /external/clang/test/Analysis/ |
| cfref_PR2519.c | 28 // reported as being leaked).
|
| retain-release-path-notes.m | 45 id leaked = [[NSObject alloc] init]; // expected-warning{{leak}} expected-note{{Method returns an Objective-C object with a +1 retain count}}
46 return; // expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
50 CFTypeRef leaked = CFCreateSomething(); // expected-warning{{leak}} expected-note{{Call to function 'CFCreateSomething' returns a Core Foundation object with a +1 retain count}}
51 return; // expected-note{{Object leaked: object allocated and stored into 'leaked' is not referenced later in this execution path and has a retain count of +1}}
55 id leaked = [foo methodWithValue]; // expected-warning{{leak}} expected-note{{Method returns an Objective-C object with a +0 retain count}}
56 [leaked retain]; // expected-note{{Reference count incremented. The object now has a +1 retain count}}
57 [leaked retain]; // expected-note{{Reference count incremented. The object now has a +2 retain count}}
58 [leaked release]; // expected-note{{Reference count decremented. The object now has a +1 retain count}
[all...] |
| malloc-annotations.c | 148 // then returned is not leaked. In the absence of known contracts for functions
157 // which is then returned is not leaked. In the absence of known contracts for
|
| /external/llvm/lib/Support/ |
| StringPool.cpp | 22 assert(InternTable.empty() && "PooledStringPtr leaked!");
|
| /external/chromium/testing/gmock/test/ |
| gmock_output_test.py | 105 """Removes the test names of leaked mock objects from the test output."""
127 leaked mocks).
166 # The raw output should contain 2 leaked mock object errors for
|
| gmock_leak_test.py | 32 """Tests that leaked mock objects can be caught be Google Mock."""
|
| /external/chromium/chrome/browser/themes/ |
| theme_service_gtk.cc | 54 // This bitmap will be leaked, but this code should never be hit.
|
| /external/chromium/net/disk_cache/ |
| stats_histogram.cc | 35 // To avoid racy destruction at shutdown, the following will be leaked.
|
| /external/icu4c/test/cintltst/ |
| cctest.c | 17 /* This makes sure that a converter isn't leaked when an error is passed to
|
| /system/extras/tests/bionic/libc/other/ |
| test_vfprintf_leak.c | 29 * the initial code leaked heap memory each time a formatted double was printed
|
