Searched refs:faults (Results 1 – 25 of 54) sorted by relevance
123
33 bt#02: 0xffffffff80106655 => call_dispatch_user_exception at ../../zircon/kernel/arch/x86/faults.cp…34 (inlined by) try_dispatch_user_exception at ../../zircon/kernel/arch/x86/faults.cpp:9335 bt#03: 0xffffffff80106c90 => try_dispatch_user_exception at ../../zircon/kernel/arch/x86/faults.cpp…36 (inlined by) x86_invop_handler at ../../zircon/kernel/arch/x86/faults.cpp:14637 (inlined by) x86_exception_handler at ../../zircon/kernel/arch/x86/faults.cpp:344
80 …010659d => exception_die(x86_64_iframe*, char const*) at ../../zircon/kernel/arch/x86/faults.cpp:7281 bt#01: 0xffffffff80106eaa => x86_fatal_pfe_handler at ../../zircon/kernel/arch/x86/faults.cpp:22382 … (inlined by) x86_exception_handler at ../../zircon/kernel/arch/x86/faults.cpp:379
37 bt#05: 0xffffffff80106808 => x86_pfe_handler at ../../zircon/kernel/arch/x86/faults.cpp:27338 (inlined by) x86_exception_handler at ../../zircon/kernel/arch/x86/faults.cpp:378
44 uint64_t faults; member197 result.faults = usage_end.ru_majflt - usage_start.ru_majflt; in main()
16 This test uses memtester to find memory subsystem faults. The quick test
14 This test uses memtester to find memory subsystem faults. Amount of memory
8 of future memory faults, at least the fixed filesystem will be fully
55 and hardware faults.
195 | ``6`` | :attr:`ru_minflt` | page faults not requiring I/O |197 | ``7`` | :attr:`ru_majflt` | page faults requiring I/O |
23 used incorrectly it may cause segmentation faults, crashes or other incorrect
163 * DrawSetStrokeDashArray() no longer faults for an array of one element198 * CloneDrawingWand() no longer faults when the supplied drawing wand has not
293 | ``6`` | :attr:`ru_minflt` | page faults not requiring I/O |295 | ``7`` | :attr:`ru_majflt` | page faults requiring I/O |
57 of faults are supported:
133 …`LDR``, we'd still need to use ``LD1`` in some places to avoid alignment faults (the result of the…135 Most operating systems however do not run with alignment faults enabled, so this is often not an is…
34 or needs. This library is provided with all faults, and the entire
31 …A Aware). When using non-CUDA aware MPI libraries and GPU buffers you will get segmentation faults.
85 Use valgrind to find faults in the optimization phase. This will allow
83 Use valgrind to find faults in the optimization phase. This will allow
23 segmentation faults with different causes.
1937 const ExtFaults faults[] = { in START_TEST() local1958 const ExtFaults *fault = faults; in START_TEST()3490 ExtFaults faults[] = { in START_TEST() local3508 for (fault = &faults[0]; fault->parse_text != NULL; fault++) { in START_TEST()4508 ExtFaults faults[] = { in START_TEST() local4532 for (fault = &faults[0]; fault->parse_text != NULL; fault++) { in START_TEST()
292 could straddle page boundaries and cause segmentation faults due to