Home
last modified time | relevance | path

Searched refs:how (Results 1 – 13 of 13) sorted by relevance

/art/sigchainlib/
Dsigchain.cc447 int __sigprocmask(int how, const SigsetType* new_set, SigsetType* old_set, in __sigprocmask() argument
451 return linked(how, new_set, old_set); in __sigprocmask()
459 if (how == SIG_BLOCK || how == SIG_SETMASK) { in __sigprocmask()
471 return linked(how, new_set_ptr, old_set); in __sigprocmask()
474 extern "C" int sigprocmask(int how, const sigset_t* new_set, in sigprocmask() argument
477 return __sigprocmask(how, new_set, old_set, linked_sigprocmask); in sigprocmask()
481 extern "C" int sigprocmask64(int how, const sigset64_t* new_set, in sigprocmask64() argument
484 return __sigprocmask(how, new_set, old_set, linked_sigprocmask64); in sigprocmask64()
Dsigchain_test.cc52 static int RealSigprocmask(int how, const sigset64_t* new_sigset, sigset64_t* old_sigset) { in RealSigprocmask() argument
54 return syscall(__NR_rt_sigprocmask, how, new_sigset, old_sigset, NSIG/8); in RealSigprocmask()
/art/test/1978-regular-obsolete-then-structural-obsolescence/
Dexpected.txt4 how do you do Alex
11 how do you do Alex
/art/test/575-checker-string-init-alias/
Dinfo.txt2 sure the compiler knows how to handle dex aliases.
/art/test/991-field-trace-2/
Dinfo.txt3 This test specifically examines how the runtime responds to exceptions occurring
/art/test/081-hot-exceptions/
Dinfo.txt1 Make a hot exception-throwing path to stress test how the trace builder handles
/art/test/664-aget-verifier/
Dinfo.txt1 Tests how the verifier handles aget on an array that was initially null.
/art/tools/jvmti-agents/simple-force-redefine/
DREADME.md3 ForceRedefine is a JVMTI agent designed for testing how redefiniton affects running processes. It
/art/tools/jvmti-agents/field-counts/
DREADME.md4 how large the objects referenced by these fields are.
/art/tools/jvmti-agents/ti-alloc-sample/
DREADME.md21 * sample_rate is an integer specifying how frequently an event is reported.
/art/tools/checker/
DREADME147 The example above also shows how we can use environment variables to perform custom checks.
/art/cmdline/
DREADME.md33 // See variant_map_test.cc for how to completely define a custom map.
/art/test/
DAndroid.bp503 // many problems with how we export headers that are making doing this the 'right' way