Searched refs:follow (Results 1 – 10 of 10) sorted by relevance
| /xnu-11417.101.15/tools/trace/ |
| H A D | parse_ipc_trace.py | 484 def print_follow_graph(self, ofile, follow, visited = None): argument 489 for f in follow: 493 while len(follow) > 0: 498 if e.src.nicename in follow: 502 visited.extend(follow) 503 follow = [] 506 follow.append(n.nicename) 508 for f in follow: 518 def print_graph(self, ofile, follow): argument 890 if args.follow and len(args.follow) > 0: [all …]
|
| /xnu-11417.101.15/security/ |
| H A D | mac_base.c | 1361 mac_get_filelink(proc_t p, user_addr_t mac_p, user_addr_t path_p, int follow) in mac_get_filelink() argument 1371 LOCKLEAF | (follow ? FOLLOW : NOFOLLOW) | AUDITVNPATH1, in mac_get_filelink() 1476 int follow) in mac_set_filelink() argument 1498 LOCKLEAF | (follow ? FOLLOW : NOFOLLOW) | AUDITVNPATH1, in mac_set_filelink()
|
| /xnu-11417.101.15/tools/lldbmacros/ |
| H A D | README.md | 184 To easily reload your changes in lldb please follow the below example. 314 … 2 weeks later again messing with it for a new field, it is recommended to follow these guidelines. 329 It is very very HIGHLY RECOMMENDED to follow these guidelines for writing any python code. 373 To contribute new commands or fixes to existing one, it is recommended that you follow the procedur…
|
| /xnu-11417.101.15/libkern/zlib/ |
| H A D | README | 17 To compile all files and run the test program, follow the instructions given at
|
| /xnu-11417.101.15/bsd/vfs/ |
| H A D | vfs_syscalls.c | 5716 int follow; in linkat_internal() local 5731 follow = (flag & AT_SYMLINK_FOLLOW) ? FOLLOW : NOFOLLOW; in linkat_internal() 5736 NDINIT(&nd, LOOKUP, OP_LOOKUP, AUDITVNPATH1 | follow, in linkat_internal() 7108 int follow; in fstatat_internal() local 7127 follow = (flag & (AT_SYMLINK_NOFOLLOW | AT_SYMLINK_NOFOLLOW_ANY)) ? NOFOLLOW : FOLLOW; in fstatat_internal() 7129 NDINIT(ndp, LOOKUP, OP_GETATTR, follow | AUDITVNPATH1, in fstatat_internal() 7821 int follow, error; in chmodat() local 7828 follow = (flag & (AT_SYMLINK_NOFOLLOW | AT_SYMLINK_NOFOLLOW_ANY)) ? NOFOLLOW : FOLLOW; in chmodat() 7829 NDINIT(&nd, LOOKUP, OP_SETATTR, follow | AUDITVNPATH1 | wantparent, in chmodat() 8132 int follow; in fchownat_internal() local [all …]
|
| /xnu-11417.101.15/doc/primitives/ |
| H A D | atomics.md | 341 However, unlike the *consume* memory ordering where the compiler had to follow
|
| /xnu-11417.101.15/doc/allocators/ |
| H A D | api-basics.md | 126 or C++ `class`. Fixed-size types must follow certain rules:
|
| /xnu-11417.101.15/doc/debugging/ |
| H A D | debugging.md | 268 Then to profile commands, follow this sequence:
|
| /xnu-11417.101.15/doc/mach_ipc/ |
| H A D | guard_exceptions.md | 48 in terms of the kernel defined fields, they follow this template:
|
| /xnu-11417.101.15/ |
| H A D | README.md | 426 The VM headers follow the following naming conventions:
|