Home
last modified time | relevance | path

Searched refs:fault (Results 1 – 25 of 171) sorted by relevance

1234567

/ohos5.0/base/hiviewdfx/hiview/
H A Dkernel_vendor.yaml40 REASON: {type: STRING, desc: fault reason}
42 SUMMARY: {type: STRING, desc: fault summary}
43 LOG_PATH: {type: STRING, desc: fault log dir}
54 REASON: {type: STRING, desc: fault reason}
56 SUMMARY: {type: STRING, desc: fault summary}
68 REASON: {type: STRING, desc: fault reason}
82 REASON: {type: STRING, desc: fault reason}
96 REASON: {type: STRING, desc: fault reason}
110 REASON: {type: STRING, desc: fault reason}
124 REASON: {type: STRING, desc: fault reason}
[all …]
H A Dhisysevent.yaml33 SUMMARY: {type: STRING, desc: fault summary}
34 FAULT_TYPE: {type: STRING, desc: fault type}
35 LOG_PATH: {type: STRING, desc: fault log path}
94 REASON: {type: STRING, desc: fault reason}
97 SUMMARY: {type: STRING, desc: fault summary}
98 FAULT_TYPE: {type: STRING, desc: fault type}
120 REASON: {type: STRING, desc: fault reason}
136 REASON: {type: STRING, desc: fault reason}
139 SUMMARY: {type: STRING, desc: fault summary}
154 SUMMARY: {type: STRING, desc: fault summary}
[all …]
/ohos5.0/docs/en/application-dev/reference/apis-performance-analysis-kit/
H A Djs-apis-faultLogger.md15 Enumerates the fault types.
21 | NO_SPECIFIC | 0 | No specific fault type.|
28 Defines the data structure of the fault log information.
38 | reason | string | Yes| Reason for the fault.|
39 | module | string | Yes| Module on which the fault occurred.|
40 | summary | string | Yes| Summary of the fault.|
47fault information about the current process. This API uses an asynchronous callback to return the
104fault information about the current process. This API uses a promise to return the fault informati…
118 …rn the fault information array. You can obtain the fault information instance in its **then()** me…
168fault information about the current process. This API uses an asynchronous callback to return the
[all …]
/ohos5.0/docs/en/application-dev/dfx/
H A Dperformance-analysis-kit-overview.md3 …lp you check the running status of your application for further behavior, fault, security, and sta…
7 …ging: provides the HiLog function to help you record and obtain log information for fault analysis.
15 - HiAppEvent: provides application event logging, which allows you to record fault, behavior, secur…
16 - FaultLogger: manages fault logs and provides a channel for querying fault logs.
39fault detection and exception handling. As faults vary in causes and symptoms, locating faults is …
41 …ers locate and rectify application stability faults, common fault locating methods and fault analy…
H A Dapprecovery-guidelines.md53 …mework offers three methods for application fault management: fault listening, fault rectification…
59 …../reference/apis-performance-analysis-kit/js-apis-faultLogger.md) to obtain the fault information.
61 …pis-performance-analysis-kit/js-apis-faultLogger.md) to query information about the previous fault.
69fault types include JavaScript application crash, application freezing, and C++ application crash.…
77 **State Saving** in the table header means saving of the application state when a fault occurs. To …
H A Djscrash-guidelines.md5 This topic describes the JS Crash exception capture scenario, JS Crash fault analysis, and typical …
56 The process crash log is a type of fault log managed together with the app freeze and JS applicatio…
60 …Log](https://developer.huawei.com/consumer/en/doc/harmonyos-guides-V5/ide-fault-log-V5)<!--RP1End-…
64 …hiAppEvent provides APIs to subscribe to various fault logs. For details, see [Introduction to HiA…
69 …When a process crashes, you can find fault logs in **/data/log/faultlog/faultlogger/** on the devi…
76 Generally, the cause of the fault can be found by locating the problematic code based on the except…
80 In JS Crash fault logs, the **StackTrace** field provides the call stack information about the JS C…
283 …application encounters a fault that cannot be rectified, a JS exception is thrown to terminate the…
295 Based on the fault logs collected by DevEco Studio FaultLog, you can locate the exception based on …
299 To solve this problem, locate the problematic code line based on the fault log and review the conte…
H A Dappfreeze-guidelines.md10 Currently, appfreeze detection supports the fault types listed in the following table.
30 This fault occurs when the system does not respond to a click event within 5 seconds.
104 | EVENTNAME | One or more fault events that constitute the cause of main thread freeze event.|
108 | MSG | Dump information or description of the fault.|
444 #### Obtain the fault occurrence time
452 TIMESTAMP: 2024/04/10-16:40:52:743 --> The timestamp when the fault is reported.
471 The fault occurrence time can be obtained based on the detection duration and the fault reporting t…
753 View [Obtain the fault occurrence time](#obtain-the-fault-occurrence-time), and determine the fault
828 Extract the key fault logs.
1020 This appfreeze fault occurs when the thread is busy.
[all …]
/ohos5.0/foundation/distributeddatamgr/datamgr_service/services/distributeddataservice/adapter/dfx/test/
H A DBUILD.gn24 "../src/fault",
68 "../src/fault",
85 "../src/fault/communication_fault_impl.cpp",
86 "../src/fault/database_fault_impl.cpp",
87 "../src/fault/fault_reporter.cpp",
88 "../src/fault/runtime_fault_impl.cpp",
89 "../src/fault/service_fault_impl.cpp",
/ohos5.0/foundation/distributeddatamgr/datamgr_service/services/distributeddataservice/adapter/dfx/
H A DBUILD.gn27 "src/fault/communication_fault_impl.cpp",
28 "src/fault/database_fault_impl.cpp",
29 "src/fault/runtime_fault_impl.cpp",
30 "src/fault/service_fault_impl.cpp",
42 "./src/fault",
/ohos5.0/foundation/distributeddatamgr/datamgr_service/
H A Dhisysevent.yaml43 __BASE: {type: FAULT, level: CRITICAL, desc: The event is database fault }
47 ERROR_TYPE: {type: INT32, desc: fault type }
50 __BASE: {type: FAULT, level: CRITICAL, desc: The event is database fault }
54 ERROR_TYPE: {type: INT32, desc: fault type }
57 __BASE: {type: FAULT, level: CRITICAL, desc: The event is database fault }
61 ERROR_TYPE: {type: INT32, desc: fault type }
64 __BASE: {type: FAULT, level: CRITICAL, desc: The event is database fault }
68 ERROR_TYPE: {type: INT32, desc: fault type }
71 __BASE: {type: FAULT, level: CRITICAL, desc: The event is communication fault }
/ohos5.0/foundation/communication/netmanager_base/
H A Dhisysevent.yaml17 __BASE: {type: FAULT, level: CRITICAL, desc: send supplier fault event}
38 __BASE: {type: FAULT, level: CRITICAL, desc: send request fault event}
51 __BASE: {type: FAULT, level: CRITICAL, desc: send monitor fault event}
62 __BASE: {type: FAULT, level: CRITICAL, desc: send setup fault event}
69 __BASE: {type: FAULT, level: CRITICAL, desc: send cancel fault event}
81 __BASE: {type: FAULT, level: CRITICAL, desc: send request fault event}
91 __BASE: {type: FAULT, level: CRITICAL, desc: send setup fault event}
98 __BASE: {type: FAULT, level: CRITICAL, desc: start distributed network fault event}
109 __BASE: {type: FAULT, level: CRITICAL, desc: get remote device info fault event}
/ohos5.0/base/theme/wallpaper_mgr/
H A Dhisysevent.yaml43 __BASE: {type: FAULT, level: CRITICAL, desc: The event is service fault }
44 FAULT_TYPE: {type: INT32, desc: fault id }
49 __BASE: {type: FAULT, level: CRITICAL, desc: The event is runtime fault }
50 FAULT_TYPE: {type: INT32, desc: fault id }
/ohos5.0/base/hiviewdfx/hisysevent/interfaces/js/kits/napi/src/
H A Dnapi_hisysevent_init.cpp46 napi_value fault = nullptr; in InitEventTypeEnum() local
47 napi_create_int32(env, HiSysEvent::FAULT, &fault); in InitEventTypeEnum()
55 eventTypeMap["FAULT"] = fault; in InitEventTypeEnum()
/ohos5.0/docs/zh-cn/device-dev/kernel/
H A Dkernel-small-debug-shell-error.md10 prefetch_abort fault fsr:0x5, far:0x00000000
11 Translation fault, section
71 prefetch_abort fault fsr:0x5, far:0x00000000
72 Translation fault, section
/ohos5.0/docs/en/device-dev/kernel/
H A Dkernel-small-debug-shell-error.md7 prefetch_abort fault fsr:0x5, far:0x00000000
8 Translation fault, section
66 prefetch_abort fault fsr:0x5, far:0x00000000
67 Translation fault, section
H A Dkernel-small-debug-trace-other-faqs.md24 …the fault only with the exception information. Sometimes, the fault cannot be located due to incor…
/ohos5.0/foundation/multimedia/player_framework/
H A Dhisysevent.yaml38 __BASE: {type: FAULT, level: CRITICAL, desc: Source fault}
47 __BASE: {type: FAULT, level: CRITICAL, desc: Demuxer fault}
73 __BASE: {type: FAULT, level: CRITICAL, desc: DRM decryption fault}
83 __BASE: {type: FAULT, level: CRITICAL, desc: DRM common fault}
91 __BASE: {type: FAULT, level: CRITICAL, desc: AudioCodec fault}
99 __BASE: {type: FAULT, level: CRITICAL, desc: VideoCodec fault}
107 __BASE: {type: FAULT, level: CRITICAL, desc: Muxer fault}
/ohos5.0/base/print/print_fwk/
H A Dhisysevent.yaml98 __BASE: {type: FAULT, level: CRITICAL, desc: The event is runtime fault }
100 FAULT_TYPE: {type: INT32, desc: fault id }
103 __BASE: {type: FAULT, level: CRITICAL, desc: The event is service fault }
105 FAULT_TYPE: {type: INT32, desc: fault id }
/ohos5.0/docs/en/release-notes/changelogs/v4.0-beta1/
H A Dchangelogs-ability.md6 …Flag** are changed from **NO_RESTART** upon a specific fault to **RESTART** upon a specific fault.
/ohos5.0/docs/en/release-notes/changelogs/OpenHarmony_3.2.10.6/
H A Dchangelogs-ability.md5 …Flag** are changed from **NO_RESTART** upon a specific fault to **RESTART** upon a specific fault.
/ohos5.0/docs/en/release-notes/changelogs/OpenHarmony_4.0.2.3/
H A Dchangelogs-ability.md5 …Flag** are changed from **NO_RESTART** upon a specific fault to **RESTART** upon a specific fault.
/ohos5.0/base/powermgr/thermal_manager/
H A Dthermalmgr.yaml32 __BASE: {type: FAULT, level: MINOR, tag: PowerStats, desc: fan fault information}
33 ID: {type: INT32, desc: fault id}
/ohos5.0/base/security/device_auth/
H A Dhisysevent.yaml25 __BASE: {type: FAULT, level: CRITICAL, desc: fault event}
27 FAULT_REASON: {type: INT32, desc: fault reason}
/ohos5.0/base/web/webview/
H A Dhisysevent.yaml22 __BASE: {type: FAULT, level: MINOR, tag: fault, desc: audio play error, preserve: true}
29 __BASE: {type: FAULT, level: MINOR, tag: fault, desc: camera capture error, preserve: true}
80 __BASE: {type: FAULT, level: MINOR, tag: fault, desc: input method error, preserve: true}
115 __BASE: {type: FAULT, level: MINOR, tag: fault, desc: page download error, preserve: true}
165 __BASE: {type: FAULT, level: MINOR, tag: fault, desc: paste board error, preserve: true}
194 __BASE: {type: FAULT, level: MINOR, tag: fault, desc: video play error, preserve: true}
/ohos5.0/base/hiviewdfx/hicollie/
H A DREADME.md14 …ware watchdog capability. It implements a unified framework for fault detection and fault log gene…

1234567