Home
last modified time | relevance | path

Searched refs:failure (Results 1 – 21 of 21) sorted by relevance

/xnu-8796.141.3/SETUP/config/
H A Dsearchp.c72 int failure; in searchp() local
91 failure = (*func)(fullname); in searchp()
92 }while (failure && (*lastchar)); in searchp()
93 return failure ? -1 : 0; in searchp()
/xnu-8796.141.3/libsyscall/mach/
H A Derr_libkern.sub49 "(libkern/metaclass) allocation failure, internal data", /* 4 */
50 "(libkern/metaclass) allocation failure, class tracking dictionaries", /* 5 */
51 "(libkern/metaclass) allocation failure, no kext/class set", /* 6 */
64 "(libkern/kext) allocation failure", /* 0x2 */
75 "(libkern/kext) validation failure (plist/executable)", /* 0xc */
76 "(libkern/kext) authentication failure (file ownership/permissions)", /* 0xd */
77 "(libkern/kext) dependency resolution failure", /* 0xe */
H A Derr_mach_ipc.sub86 /* 0 */ "(ipc/mig) client type check failure",
90 /* 4 */ "(ipc/mig) server type check failure",
H A Derr_kern.sub42 "(os/kern) protection failure",
45 "(os/kern) failure", /* 5 */
49 "(os/kern) memory failure",
H A Derr_iokit.sub57 "(iokit/common) misc. VM failure", // 0x2c8
68 "(iokit/common) rld failure", // 0x2d3
69 "(iokit/common) DMA failure", // 0x2d4
H A Derr_ipc.sub67 "(ipc/mig) type check failure in message interface", /* 0 (-300) */
H A Derr_server.sub153 "(server/sunrpc) failure in sending call",
154 "(server/sunrpc) failure in receiving result",
/xnu-8796.141.3/osfmk/kern/
H A Dhv_support_kext.h94 uint32_t failure, uint32_t error);
/xnu-8796.141.3/bsd/miscfs/devfs/
H A Ddevfs_vnops.c1160 goto failure; in devfs_mkdir()
1169 failure: in devfs_mkdir()
1242 goto failure; in devfs_make_symlink()
1254 failure: in devfs_make_symlink()
1298 goto failure; in devfs_mknod()
1303 goto failure; in devfs_mknod()
1311 failure: in devfs_mknod()
/xnu-8796.141.3/osfmk/tests/
H A DREADME.md48 …* And you are set. Use KERN_SUCCESS to report successful run and any other error for failure. Here…
77 …* T_ASSERT macros will check for condition and upon failure return with KERN_FAILURE. This way it …
78 * T_EXPECT will just report failure of that test case, but will continue to run further test code.
/xnu-8796.141.3/libkern/kxld/
H A Dkxld_vtable.c499 boolean_t failure = FALSE; in kxld_vtable_patch() local
602 failure = TRUE; in kxld_vtable_patch()
662 require_action(!failure, finish, rval = KERN_FAILURE); in kxld_vtable_patch()
H A Dkxld_kext.c838 boolean_t failure = FALSE; in patch_vtables() local
894 if (failure) { in patch_vtables()
997 require_action(!failure, finish, rval = KERN_FAILURE); in patch_vtables()
998 failure = (nprogress == 0); in patch_vtables()
/xnu-8796.141.3/osfmk/mach/
H A Dtask_access.defs43 * Access granted by return value (success/failure)
H A Dhost_priv.defs158 * In addition to all the failure modes of its cousin,
/xnu-8796.141.3/makedefs/
H A DMakeInc.rule80 $(ERR) Parse failure for $$<; \
117 $(ERR) Parse failure for $$<; \
442 $(ERR) Parse failure for $<; \
/xnu-8796.141.3/osfmk/conf/
H A Dcopyright.osf47 # failure to abide by the terms of this license.
/xnu-8796.141.3/doc/
H A Datomics.md233 will always be `expected`, however in case of failure it will be filled with
239 for the failure case ordering, as it is what is used most of the time.
/xnu-8796.141.3/tools/lldbmacros/
H A DREADME.md401 isolate possible causes of failure, and eventually filing a bug with kernel team. Following are som…
409 …s particularly tricky. Many parts of memory may not be readable. There could be failure in network,
413 …orruption, the lldbmacros may have followed wrong pointer dereferencing. This might lead to failure
/xnu-8796.141.3/
H A DAPPLE_LICENSE213 systems, or air traffic control machines in which case the failure of
/xnu-8796.141.3/osfmk/ipc/
H A Dipc_kmsg.c784 goto failure; in ikm_validate_sig_internal()
806 failure: in ikm_validate_sig_internal()
/xnu-8796.141.3/tests/
H A Dstackshot_tests.m2668 * check_shared_cache_uuid() will assert on failure, so if
2918 * check_shared_cache_uuid() asserts on failure, so we must have