In addition to calling APIs to check the memory used by user-mode processes, you can run CLI commands to collect memory statistics, check for memory leaks, and check memory integrity.
阅读全文
开源鸿蒙 Calling APIs
The sample code explicitly calls the related APIs of the memory debugging module to check the memory.
阅读全文
开源鸿蒙 Available APIs
Table 1 Memory debugging module APIs
阅读全文
开源鸿蒙 Working Principles
The memory debugging module maintains 128 (that is the maximum number of threads supported in the system) linked lists for each process. The index of each linked list is the thread ID.
阅读全文
开源鸿蒙 Typical Memory Problems
Requested memory block less than or equal to 0x1c000 bytes:
阅读全文
开源鸿蒙 Basic Concepts
The musl libc library of the debug version provides maintenance and test methods, such as memory leak check, heap memory statistics, memory corruption check, and backtrace, to improve the efficiency of locating memory problems in user space.
阅读全文
openharmony 鸿蒙 kernel-small-debug-trace
Trace Basic Concepts Trace helps you learn about the kernel running process and the execution sequence of modules and tasks. With the information, you can better understand the code running process of
阅读全文
openharmony 鸿蒙 kernel-small-debug-trace-other-lastwords
Dying Gasp When to Use For a device without a serial port, the dying gasp saves the exception information to a non-volatile storage medium to facilitate fault location during system running. Available
阅读全文
openharmony 鸿蒙 kernel-small-debug-trace-other-faqs
Common Fault Locating Methods Locating the Fault Based on Exception Information When the system is suspended unexpectedly, information about key registers is displayed on the serial port, as shown in
阅读全文
开源鸿蒙 Shell
Introduction to the Shell
阅读全文