Searched refs:lost (Results 1 – 25 of 728) sorted by relevance
12345678910>>...30
| /third_party/e2fsprogs/tests/f_expand/ |
| D | expect.1.gz | |
| /third_party/e2fsprogs/tests/f_rebuild_csum_rootdir/ |
| D | expect.1 | 17 Connect to /lost+found? yes
19 /lost+found not found. Create? yes
26 Connect to /lost+found? yes
31 Connect to /lost+found? yes
36 Connect to /lost+found? yes
41 Connect to /lost+found? yes
46 Connect to /lost+found? yes
51 Connect to /lost+found? yes
56 Connect to /lost+found? yes
61 Connect to /lost+found? yes
[all …]
|
| /third_party/openssl/test/ |
| D | memleaktest.c | 30 char *lost; in main() local
38 lost = OPENSSL_malloc(3); in main()
39 if (!TEST_ptr(lost)) in main()
43 OPENSSL_free(lost); in main()
44 lost = NULL; in main()
52 return TEST_int_eq(lost != NULL, noleak == 0) ? EXIT_SUCCESS : EXIT_FAILURE; in main()
|
| /third_party/e2fsprogs/tests/f_lpffile/ |
| D | expect.1 | 4 /lost+found is not a directory (ino=11)
7 /lost+found not found. Create? yes
11 Connect to /lost+found? yes
14 Connect to /lost+found? yes
19 Connect to /lost+found? yes
24 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_nospc_create_lnf/ |
| D | expect.1 | 4 /lost+found not found. Create? yes
6 Cannot allocate space for /lost+found.
7 Place lost files in root directory instead? yes
9 Insufficient space to recover lost files!
15 Connect to /lost+found? yes
|
| D | expect.2 | 4 /lost+found not found. Create? yes
6 Cannot allocate space for /lost+found.
7 Place lost files in root directory instead? yes
9 Insufficient space to recover lost files!
|
| /third_party/e2fsprogs/tests/f_encrypted_lpf/ |
| D | expect.1 | 5 Connect to /lost+found? yes
7 /lost+found is encrypted
10 /lost+found not found. Create? yes
17 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_bad_encryption/ |
| D | expect.1 | 58 Connect to /lost+found? yes
61 Connect to /lost+found? yes
64 Connect to /lost+found? yes
68 Connect to /lost+found? yes
75 Connect to /lost+found? yes
82 Connect to /lost+found? yes
87 Connect to /lost+found? yes
94 Connect to /lost+found? yes
99 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_noroot/ |
| D | expect.1 | 7 Entry '..' in /lost+found (11) has deleted/unused inode 2. Clear? yes
15 Connect to /lost+found? yes
17 /lost+found not found. Create? yes
20 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_lpf/ |
| D | expect.1 | 8 /lost+found not found. Create? yes
12 Connect to /lost+found? yes
17 Connect to /lost+found? yes
22 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_reconnect/ |
| D | expect.1 | 6 Connect to /lost+found? yes
11 Connect to /lost+found? yes
16 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_badroot/ |
| D | expect.1 | 13 Connect to /lost+found? yes
15 /lost+found not found. Create? yes
21 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_lpf2/ |
| D | expect.1 | 5 Connect to /lost+found? yes
7 /lost+found not found. Create? yes
10 Connect to /lost+found? yes
|
| D | name | 1 create lost+found and reconnect lost directory
|
| /third_party/e2fsprogs/tests/f_imagic/ |
| D | expect.1 | 10 /lost+found not found. Create? yes
16 Connect to /lost+found? yes
21 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_orphan_dotdot_ft/ |
| D | expect.1 | 21 Connect to /lost+found? yes
24 Connect to /lost+found? yes
27 Connect to /lost+found? yes
|
| /third_party/e2fsprogs/tests/f_filetype/ |
| D | expect.1 | 17 Setting filetype for entry 'lost+found' in / (2) to 2.
33 Setting filetype for entry '.' in /lost+found (11) to 2.
34 Setting filetype for entry '..' in /lost+found (11) to 2.
|
| /third_party/skia/third_party/externals/angle2/extensions/ |
| D | EGL_ANGLE_device_creation_d3d11.txt | 79 "If a Direct3D 11 device used to create a device experiences a "lost device"
81 undefined. It is the caller's responsibility to monitor for "lost device"
83 more information on "lost device", see the Direct3D documentation."
|
| /third_party/flutter/skia/third_party/externals/angle2/extensions/ |
| D | EGL_ANGLE_device_creation_d3d11.txt | 79 "If a Direct3D 11 device used to create a device experiences a "lost device"
81 undefined. It is the caller's responsibility to monitor for "lost device"
83 more information on "lost device", see the Direct3D documentation."
|
| /third_party/e2fsprogs/tests/f_badtable/ |
| D | expect.1 | 11 Entry 'lost+found' in / (2) points to inode (11) located in a bad block.
15 /lost+found not found. Create? yes
|
| /third_party/boost/libs/outcome/doc/src/content/reference/functions/ |
| D | strong_swap.md | 6 …lost. This ADL discovered function provides the strong guarantee instead: that if any of these ope…
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/NV/ |
| D | NV_robustness_video_memory_purge.txt | 47 (FBOs), will be lost. As the OpenGL specification makes no mention
53 memory content has been lost, so that the application can re-populate
115 memory content has been lost. This will only take effect if the
128 memory content has been lost. This will only take effect if the
|
| /third_party/openGLES/extensions/NV/ |
| D | NV_robustness_video_memory_purge.txt | 47 (FBOs), will be lost. As the OpenGL specification makes no mention
53 memory content has been lost, so that the application can re-populate
115 memory content has been lost. This will only take effect if the
128 memory content has been lost. This will only take effect if the
|
| /third_party/node/doc/guides/ |
| D | investigating_native_memory_leak.md | 77 ==28993== definitely lost: 0 bytes in 0 blocks
78 ==28993== indirectly lost: 0 bytes in 0 blocks
79 ==28993== possibly lost: 304 bytes in 1 blocks
170 ==1504== definitely lost: 996,064 bytes in 997 blocks
171 ==1504== indirectly lost: 0 bytes in 0 blocks
172 ==1504== possibly lost: 3,304 bytes in 4 blocks
185 definitely lost and the question is how to find where that memory was
221 ==4174== 64 bytes in 1 blocks are definitely lost in loss record 17 of 35
236 ==4174== 304 bytes in 1 blocks are possibly lost in loss record 27 of 35
249 ==4174== 2,000 bytes in 2 blocks are possibly lost in loss record 33 of 35
[all …]
|
| /third_party/flutter/flutter/packages/flutter/lib/src/rendering/ |
| D | performance_overlay.dart | 21 /// step exceeds the frame slice, a frame is lost.
27 /// the bar turns red, a frame is lost.
35 /// this step exceeds the frame slice, a frame is lost.
41 /// turns red, a frame is lost.
|
12345678910>>...30