CN112527558A - Method, system and terminal equipment for analyzing crash of subsystem - Google Patents
Method, system and terminal equipment for analyzing crash of subsystem Download PDFInfo
- Publication number
- CN112527558A CN112527558A CN202011424291.9A CN202011424291A CN112527558A CN 112527558 A CN112527558 A CN 112527558A CN 202011424291 A CN202011424291 A CN 202011424291A CN 112527558 A CN112527558 A CN 112527558A
- Authority
- CN
- China
- Prior art keywords
- subsystem
- crash
- analyzing
- dump
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000006870 function Effects 0.000 claims description 16
- 238000004891 communication Methods 0.000 claims description 12
- 230000002159 abnormal effect Effects 0.000 abstract description 22
- 238000012423 maintenance Methods 0.000 abstract description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000002354 daily effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention belongs to the field of mobile terminals, and provides a method, a system and terminal equipment for analyzing the crash of a subsystem, wherein the method comprises the following steps: embedding points on a kernel layer of a subsystem so as to obtain the embedded point data when the subsystem crashes; and receiving the attribute data packet, and selecting and storing the corresponding dump file for analyzing the crash of the subsystem. By obtaining the memory file when the subsystem is abnormal and analyzing the reason of the subsystem crash, the problem that some subsystems which are difficult to reproduce appear in the user equipment are abnormal is solved, meanwhile, the terminal equipment does not need to return to reproduce, and the after-sale maintenance cost is reduced.
Description
Technical Field
The invention relates to the field of mobile terminals, in particular to a method, a system and terminal equipment for analyzing the crash of a subsystem.
Background
For android devices with more and more abundant functions, besides the frequently mentioned CPU, DDR, Disk and TP, there are various subsystem modules, such as Wifi-related module (wcnss subsytem), communication-related module (modem subsytem), and Sensor-related module (adsp subsytem). When we analyze the android system crash, we inevitably encounter kernel panel caused by the crash of the subsystems. The problem of such a subsystem crash is more serious for general user equipment, because the usage of the subsystems is more susceptible to the usage scenario of the user. Three more common subsystems, such as wcnss, modem, and adsp, are easily affected by factors such as the local complex network and communication environment.
There are two current approaches to analyzing the crash problem of such subsystems: one is that when the user equipment feedbacks the abnormality, because there is no site, the tester can only be arranged to reproduce according to the user's use scene by sending back the machine, but the subsystem crash problem is generally difficult to reproduce after being sent back; the other is that when the user equipment is abnormal, the ramdump of the DDR of the user equipment is remotely acquired through the network, but with the increasing DDR of the current android equipment (the DDR of the mobile phone reaches 12G), if all the ramdump (which is equal to the size of the DDR) on the DDR of the user equipment is directly and remotely captured, the data volume is acquired, which inevitably has a great influence on the data traffic of the user, and the acquisition overhead through the network platform is relatively large. Therefore, it is very necessary to solve the above problems.
Disclosure of Invention
The invention provides a method, a system and terminal equipment for analyzing the crash of a subsystem, which are used for solving the problem of the crash of the analysis subsystem.
The technical scheme provided by the invention is as follows:
in one aspect, the invention provides a method for analyzing the crash of a subsystem, which comprises the following steps:
embedding points on a kernel layer of a subsystem so as to obtain the embedded point data when the subsystem crashes;
and receiving the attribute data packet, and selecting and storing the corresponding dump file for analyzing the crash of the subsystem.
Further preferably, before the embedding the point at the kernel layer of the subsystem so that the terminal device obtains the embedded point data when the subsystem crashes, the method further includes the steps of:
and setting the restart level of each subsystem of the user edition in the terminal equipment to be related.
Further preferably, after the setting of the restart level of each subsystem of the user edition in the terminal device to related, the method further includes the steps of:
and when the restart level of the subsystem is set to be related and the crash occurs, restarting the subsystem.
Further preferably, after the setting of the restart level of each subsystem of the user edition in the terminal device to related, the method further includes the steps of:
and when the restart level of each subsystem is set to be related and the subsystem crashes, generating dump files of the subsystem.
Further preferably, the embedding a point at a kernel layer of the subsystem so that the terminal device obtains the embedded point data when the subsystem crashes includes the steps of:
transmitting the buried point of the kernel layer to a framwork layer interface function through android JNI communication;
inserting the buried point data into a launcher database through the frawork layer interface function;
and transmitting the data of the buried point to the webpage end in real time through the launcher database.
Further preferably, the receiving the attribute data packet and selecting the corresponding dump file for storage to analyze the crash of the subsystem includes:
analyzing and acquiring attributes and attribute values by using the attribute data packet;
selecting and storing the dump file of the subsystem according to the attribute and the attribute value;
wherein the dump file comprises a memory file when the subsystem is halted.
Further preferably, the receiving the attribute data packet and selecting the corresponding dump file for storage to analyze the crash of the subsystem includes:
receiving an attribute data packet, and opening a dump file collection switch of the subsystem by the terminal equipment;
and when the subsystem crashes again, automatically collecting dump files of the subsystem based on the attribute data packet so as to analyze the crash of the subsystem.
Further preferably, after receiving the attribute data packet and selecting the corresponding dump file for saving, for analyzing the crash of the subsystem, the method includes the steps of:
after the dump files are collected, compressing the dump files to generate dump compressed files;
and saving the dump compressed file and deleting the dump file.
A terminal device is applied to the method for analyzing the crash of the subsystem.
A system for analyzing the crash of a subsystem comprises the terminal equipment and a webpage end;
and the webpage end is used for sending an attribute data packet for opening a dump file collection switch of the subsystem according to the buried point data so that the terminal equipment selects and stores the corresponding dump file for analyzing the crash of the subsystem.
The method, the system and the terminal equipment for analyzing the crash of the subsystem, provided by the invention, have the following beneficial effects at least:
1) by setting the restart level of the subsystem to related, the subsystem cannot be crashed when the subsystem is crash, the corresponding subsystem can be restarted by self, and the daily use of a user is not influenced when the subsystem is abnormal.
2) After the restart level is set to be related, elf files of corresponding subsystems can be generated when the crash occurs, the reason of the subsystem crash can be analyzed through the elf files, the problem that some subsystems which are difficult to reproduce appear in user equipment are abnormal is solved, the equipment does not need to be returned to be reproduced, and the after-sale maintenance cost is reduced.
Drawings
The invention is described in further detail below with reference to the following figures and detailed description:
FIG. 1 is a schematic flow chart diagram illustrating one embodiment of a method of analyzing subsystem crashes in accordance with the present invention;
FIG. 2 is a schematic flow chart diagram illustrating another embodiment of a method for analyzing subsystem crash in accordance with the present invention;
FIG. 3 is a schematic flow chart diagram illustrating another embodiment of a method for analyzing subsystem crash in accordance with the present invention;
FIG. 4 is a flow chart illustrating another embodiment of a method for analyzing the crash of a subsystem according to the present invention.
Detailed Description
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically illustrated or only labeled. In this document, "one" means not only "only one" but also a case of "more than one".
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
In this context, it is to be understood that, unless otherwise explicitly stated or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In addition, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not intended to indicate or imply relative importance.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, other drawings and embodiments can be derived from them without inventive effort.
As shown in FIG. 1, the present invention provides one embodiment of a method of analyzing a subsystem crash, comprising the steps of:
in one aspect, the invention provides a method for analyzing the crash of a subsystem, which comprises the following steps:
s100, embedding points in a kernel layer of the subsystem, so that the embedded point data is obtained when the subsystem crashes.
Specifically, the terminal device comprises user equipment such as a mobile phone and a watch for an android system, and the subsystem comprises a Wifi related module (wcnss subsytem), a communication related module (modem subsytem) and a Sensor related module (adsp subsytem).
Illustratively, when a subsystem crash occurs, a big data buried point report is performed, that is, a big data platform at a web end is reported when the subsystem crash occurs.
S200, receiving the attribute data packet, and selecting and storing the corresponding dump file for analyzing the crash of the subsystem.
Specifically, the web platform, i.e., the big data platform at the web end, pushes an attribute value to the user equipment, and opens a switch for collecting the subsystem dump file.
Illustratively, through the attributes and attribute values set by the web platform, the web platform receives the fields (attributes and attribute values) sent by the web end by using the server through the network, and the terminal device analyzes the received fields and selects the corresponding subsystem dump file by itself through the corresponding attributes and attribute values. The dump file refers to a memory file when each subsystem is abnormal, which is needed when the problem of the crash of the subsystem is analyzed.
In the embodiment, the problem that some subsystems which are difficult to reproduce appear in the user equipment is solved, and meanwhile, the user equipment does not need to be returned to reproduce, so that the maintenance cost after sale is reduced; when the subsystem is abnormal, the daily use of the user is not influenced.
Example two
The invention provides a method for analyzing the crash of a subsystem, which comprises the following steps as shown in figure 2:
before embedding points in the kernel layer of the subsystem in step S100 so as to obtain the embedded point data when the subsystem crashes, the method further includes the steps of:
s000, the restart level of each subsystem of the user edition in the terminal equipment is set to be related.
Specifically, the restart level of the subsystem is set to related, which is to prevent the system from crashing when the subsystem is abnormal, and the corresponding subsystem is automatically restarted in the background. After the restart level is set to related, an elf file of the corresponding subsystem is generated when the crash occurs. The reason for the subsystem crash can also be analyzed by these elf files.
The system sets two levels (system and related) for subsystem restart, the subsystem restart level set by the system by default is system, but we need to set related level here, in order to collect elf files when the corresponding subsystem is abnormal when the subsystem is crash.
When the subsystem is abnormal after the system level is set, the whole system is abnormal, the collection of the elf file of the subsystem cannot be carried out, and a user cannot normally use the system. Although in this case, the ramdump of the entire memory may be collected (when the entire system crashes at a certain time point, information of the software when the software crashes is stored in the memory), the size of the ramdump is consistent with the size of the DDR of the corresponding device, the memory data is very large, and when the abnormality of the subsystem is analyzed, the entire ramdump file needs to be analyzed, which is very inefficient.
In this embodiment, the restart level of each subsystem is set to a related level, and when an exception occurs in a subsystem in the system, only the subsystem is automatically restarted, and the restart caused by the exception of the whole system is avoided, so that the normal use of the system by a user is not affected. Meanwhile, the elf file with the subsystem abnormal can be collected, and the size of the collected file is far smaller than that of ramdump.
In this case, the embodiment ensures that only the corresponding subsystem is restarted when a certain subsystem crashes by setting the restart level to the related level, so that the whole system is not restarted. On one hand, the normal operation of the system can be ensured, and the user experience is improved; on the other hand, the size of the collected file is far smaller than that of the ramdump file generated when the system is completely restarted, so that the subsequent abnormal analysis of the subsystem is more efficient and faster.
Preferably, the step S100 of embedding a point in a kernel layer of the subsystem so as to obtain the embedded point data when the subsystem crashes includes the steps of:
transmitting the buried point of the kernel layer to a framwork layer interface function through android JNI communication; inserting the buried point data into a launcher database through the frawork layer interface function; and transmitting the data of the buried point to the webpage end in real time through the launcher database.
Preferably, the receiving the attribute data packet and selecting the corresponding dump file for storage to analyze the crash of the subsystem includes:
analyzing and acquiring attributes and attribute values by using the attribute data packet; selecting and storing the dump file of the subsystem according to the attribute and the attribute value; wherein the dump file comprises a memory file when the subsystem is halted.
Preferably, the receiving the attribute data packet and selecting the corresponding dump file for storage to analyze the crash of the subsystem includes:
receiving an attribute data packet, and opening a dump file collection switch of the subsystem by the terminal equipment; and when the subsystem crashes again, automatically collecting dump files of the subsystem based on the attribute data packet so as to analyze the crash of the subsystem.
Specifically, after the first occurrence of the subsystem crash, the web platform provides the attribute data packet, namely the attribute and the attribute value, to the terminal device, so that the collection switch of the subsystem elf file is opened, and when the subsystem of the android system in the terminal device generates the crash again, the dump file in the elf format can be directly collected.
In the embodiment, the collection switch of the dump file is opened by generating the attribute data packet in advance, so that the dump file can be automatically collected when the subsequent subsystem generates the coast, and the efficiency of analyzing the crash reason of the subsystem is improved.
Preferably, after receiving the attribute data packet and selecting the corresponding dump file for saving, so as to analyze the crash of the subsystem, the method includes the steps of:
after the dump files are collected, compressing the dump files to generate dump compressed files; and saving the dump compressed file and deleting the dump file.
In this embodiment, by compressing the dump file, the storage space can be reduced, and the cache space is saved, so as to avoid incomplete storage of the dump file due to insufficient cache space.
EXAMPLE III
The invention provides a method for analyzing the crash of a subsystem, which comprises the following steps as shown in figure 3:
when the subsystem scratch occurs, the restart level of the user version is set to related.
Specifically, before the subsystem scratch occurs, the default is to set the restart level of the user version to related and the default of the debug version to system.
The User version generally refers to a software version provided for formal release by a User; debug generally refers to an informal version of software used for development debugging.
Illustratively, after the User version subsystem restart level is set to be related, when the subsystem has a coast, the whole android system is not influenced, the system still normally operates, and the subsystem is restarted at the background, so that the whole system is not restarted. The performance in the user experience is that the user is completely unaware of the machine exception and generally does not affect the user's use of other functions during the subsystem restart. The goal of setting the relationship level is that the system crashes and restarts only a portion of the subsystems, rather than all of the subsystems.
When the subsystem crash occurs, the big data is reported by a buried point, namely the big data is reported to a big data platform of a web end when the subsystem crash occurs.
Specifically, when the subsystem crash occurs, the kernel layer embedding point of the android system is generally transmitted to the fragwork layer interface function of the android system through android JNI communication. And the frawork layer interface function inserts the uploaded data into the launcher database again, and finally the launcher sends the uploaded data to the web end in real time through a network (wifi or data traffic).
The web platform pushes an attribute value to the user equipment and opens a switch of a collection subsystem dump file (elf file).
Specifically, through the attributes and attribute values set by the web platform, the web platform receives the fields (attributes and attribute values) sent by the web end through the network, the terminal device receives the fields through the network, analyzes the received fields, and selects the corresponding subsystem dump file by itself according to the corresponding attributes and attribute values. The dump file refers to a memory file when each subsystem is abnormal when the problem of the crash of the subsystem is analyzed, and the file format is an elf file.
When the machine generates the subsystem crash again, dump files of the subsystem are automatically collected, and in order to reduce the occupied space of a user, the elf files are compressed and then stored.
Wherein the compression mechanism is: after each dump file is collected, the files are immediately compressed and the original files are deleted, and only the compressed files are reserved.
And the developer utilizes the web end to pull the dump file of the subsystem through the network and then analyzes the dump file.
Because the reported device list of the generating subsystem is arranged on the web platform every day, when the device generates the subsystem crash again, the dump file can be pulled through the network through the anonymous number of the web platform. Because the method mainly aims at the user equipment, the user equipment is generally pulled through the network, and the user equipment can also obtain the local adb pull file.
In the embodiment, the invention can analyze the subsystem crash equipment which is not easy to reproduce in the market, solves the problems of the analysis and the like at present, can meet the requirement that developers analyze the key dump logs required by the crash, and can not excessively lose the data traffic of users.
The default subsystem restart level of the general equipment is system, after the subsystem is subjected to coast, a kernel company is caused, the whole machine is pulled and hung, and the performance of the user equipment end is the whole machine restart. Except after all ramdump of DDR, analysis can also be performed through elf files of specific subsystems, and the method provided by the invention is characterized in that when the subsystems are in a crash state, the restart level of each subsystem in the android system is set to related, so that the subsystems are not crashed when abnormal, and the corresponding subsystems are automatically restarted in a background. After the restart level is set to related, an elf file of the corresponding subsystem is generated when the crash occurs. The reason for the subsystem crash can also be analyzed by these elf files.
Example four
Based on the foregoing embodiment, as shown in fig. 4, parts of this embodiment that are the same as those of the foregoing embodiment are not necessarily described again, and this embodiment provides an embodiment of a method for analyzing a crash of a subsystem, which specifically includes the following steps:
before embedding points in the kernel layer of the subsystem in step S100 so as to obtain the embedded point data when the subsystem crashes, the method further includes the steps of:
s000, the restart level of each subsystem of the user edition in the terminal equipment is set to be related.
Specifically, the restart level of the subsystem is set to related, which is to prevent the system from crashing when the subsystem is abnormal, and the corresponding subsystem is automatically restarted in the background. After the restart level is set to related, an elf file of the corresponding subsystem is generated when the crash occurs. The reason for the subsystem crash can also be analyzed by these elf files.
Preferably, after the step S000 of setting the restart level of each subsystem of the user version in the terminal device to related, the method further includes the steps of:
and S001, when the restart level of the subsystem is set to be related and the crash occurs, restarting the subsystem.
Preferably, after the step S000 of setting the restart level of each subsystem of the user version in the terminal device to related, the method further includes the steps of:
and S002, when the restart level of each subsystem is set to be related and the subsystem crashes, generating dump files of the subsystem.
Specifically, because the system includes a plurality of subsystems, the restart level of the subsystem is set to related, when the subsystem is crash, that is, when the subsystem is abnormal, all the subsystems are not crashed, and only the corresponding subsystem is automatically restarted in the background. After the restart level is set to related, an elf file of the corresponding subsystem is generated when the crash occurs. The reason for the subsystem crash can also be analyzed by these elf files.
S100, embedding points in a kernel layer of the subsystem, so that the embedded point data is obtained when the subsystem crashes.
Specifically, the terminal device comprises user equipment such as a mobile phone and a watch for an android system, and the subsystem comprises a Wifi related module (wcnss subsytem), a communication related module (modem subsytem) and a Sensor related module (adsp subsytem).
Illustratively, when a subsystem crash occurs, a big data buried point report is performed, that is, a big data platform at a web end is reported when the subsystem crash occurs.
S200, receiving the attribute data packet, and selecting and storing the corresponding dump file for analyzing the crash of the subsystem.
Specifically, the web platform, i.e., the big data platform at the web end, pushes an attribute value to the user equipment, and opens a switch for collecting the subsystem dump file.
Illustratively, through the attributes and attribute values set by the web platform, the web platform receives the fields (attributes and attribute values) sent by the web end through the network, and the terminal device analyzes the received fields and selects the corresponding subsystem dump file by itself according to the corresponding attributes and attribute values. The dump file refers to a memory file when each subsystem is abnormal, which is needed when the problem of the crash of the subsystem is analyzed.
In the embodiment, the problem that some subsystems which are difficult to reproduce appear in the user equipment is solved, and meanwhile, the user equipment does not need to be returned to reproduce, so that the maintenance cost after sale is reduced; when the subsystem is abnormal, the daily use of the user is not influenced.
EXAMPLE five
The invention provides a terminal device, which is applied to the method for analyzing the crash of a subsystem.
Specifically, the terminal device includes a mobile phone, a watch, a tablet and other user devices applying the android system.
The terminal equipment is used for setting the restart level of each subsystem of the user edition in the terminal equipment to be related so as to restart the subsystem which crashes.
The terminal equipment is used for transmitting the buried point of the kernel layer to a framwork layer interface function through android JNI communication; inserting the buried point data into a launcher database through the frawork layer interface function; and transmitting the data of the buried point to the webpage end in real time through the launcher database.
The terminal equipment is used for analyzing and acquiring the attribute and the attribute value by using the attribute data packet; selecting and storing the dump file of the subsystem according to the attribute and the attribute value; wherein the dump file comprises a memory file when the subsystem is halted.
The terminal equipment is used for receiving the attribute data packet, and the terminal equipment opens a dump file collection switch of the subsystem; and when the subsystem crashes again, automatically collecting dump files of the subsystem based on the attribute data packet so as to analyze the crash of the subsystem.
Specifically, after the first occurrence of the subsystem crash, the web platform provides the attribute data packet, namely the attribute and the attribute value, to the terminal device, so that the collection switch of the subsystem elf file is opened, and when the subsystem of the android system in the terminal device generates the crash again, the dump file in the elf format can be directly collected.
In the embodiment, the collection switch of the dump file is opened by generating the attribute data packet in advance, so that the dump file can be automatically collected when the subsequent subsystem generates the coast, and the efficiency of analyzing the crash reason of the subsystem is improved.
Selecting a corresponding dump file for storage in the received attribute data packet so as to analyze the crash of the subsystem, wherein the terminal equipment is used for compressing the dump file to generate a dump compressed file after the dump file is collected; and saving the dump compressed file and deleting the dump file.
In this embodiment, by compressing the dump file, the storage space can be reduced, and the cache space is saved, so as to avoid incomplete storage of the dump file due to insufficient cache space.
EXAMPLE five
The invention provides a system for analyzing the crash of a subsystem, which comprises terminal equipment and a webpage end.
And the webpage end is used for sending an attribute data packet for opening a dump file collection switch of the subsystem according to the buried point data so as to select and store the corresponding dump file for analyzing the crash of the subsystem.
In this embodiment, the web page side sends an attribute data packet for opening a dump file collection switch of a subsystem according to embedded data sent by the terminal device, so that the terminal device starts up collection of the dump for opening the subsystem, and selects a corresponding dump file for storage, so as to analyze the crash of the subsystem.
Illustratively, when a subsystem scratch occurs, the restart level of the user version is set to related.
Specifically, before the subsystem scratch occurs, the default is to set the restart level of the user version to related and the default of the debug version to system.
The User version generally refers to a software version provided for formal release by a User; debug generally refers to an informal version of software used for development debugging.
Illustratively, after the User version subsystem restart level is set to be related, when the subsystem has a coast, the whole android system is not influenced, the system still normally operates, and the subsystem is restarted at the background, so that the whole system is not restarted. The performance in the user experience is that the user is completely unaware of the machine exception and generally does not affect the user's use of other functions during the subsystem restart. The goal of setting the relationship level is that the system crashes and restarts only a portion of the subsystems, rather than all of the subsystems.
When the subsystem crash occurs, the big data is reported by a buried point, namely the big data is reported to a big data platform of a web end when the subsystem crash occurs.
Specifically, when the subsystem crash occurs, the kernel layer embedding point of the android system is generally transmitted to the fragwork layer interface function of the android system through android JNI communication. And the frawork layer interface function inserts the uploaded data into the launcher database again, and finally the launcher sends the uploaded data to the web end in real time through a network (wifi or data traffic).
The web platform pushes an attribute value to the user equipment and opens a switch of a collection subsystem dump file (elf file).
Specifically, through the attributes and attribute values set by the web platform, the web platform receives the fields (attributes and attribute values) sent by the web end through the network, the terminal device receives the fields through the network, analyzes the received fields, and selects the corresponding subsystem dump file by itself according to the corresponding attributes and attribute values. The dump file refers to a memory file when each subsystem is abnormal when the problem of the crash of the subsystem is analyzed, and the file format is an elf file.
When the machine generates the subsystem crash again, dump files of the subsystem are automatically collected, and in order to reduce the occupied space of a user, the elf files are compressed and then stored.
Wherein the compression mechanism is: after each dump file is collected, the files are immediately compressed and the original files are deleted, and only the compressed files are reserved.
And the developer utilizes the web end to pull the dump file of the subsystem through the network and then analyzes the dump file.
Because the reported device list of the generating subsystem is arranged on the web platform every day, when the device generates the subsystem crash again, the dump file can be pulled through the network through the anonymous number of the web platform. Because the method mainly aims at the user equipment, the user equipment is generally pulled through the network, and the user equipment can also obtain the local adb pull file.
In the embodiment, the invention can analyze the subsystem crash equipment which is not easy to reproduce in the market, solves the problems of the analysis and the like at present, can meet the requirement that developers analyze the key dump logs required by the crash, and can not excessively lose the data traffic of users.
The default subsystem restart level of the general equipment is system, after the subsystem is subjected to coast, a kernel company is caused, the whole machine is pulled and hung, and the performance of the user equipment end is the whole machine restart. Except after all ramdump of DDR, analysis can also be performed through elf files of specific subsystems, and the method provided by the invention is characterized in that when the subsystems are in a crash state, the restart level of each subsystem in the android system is set to related, so that the subsystems are not crashed when abnormal, and the corresponding subsystems are automatically restarted in a background. After the restart level is set to related, an elf file of the corresponding subsystem is generated when the crash occurs. The reason for the subsystem crash can also be analyzed by these elf files.
In the embodiment, the invention can analyze the subsystem crash equipment which is not easy to reproduce in the market, solves the problems of the analysis and the like at present, can meet the requirement that developers analyze the key dump logs required by the crash, and can not excessively lose the data traffic of users. The default subsystem restart level of the general equipment is system, after the subsystem is subjected to coast, a kernel company is caused, the whole machine is pulled and hung, and the performance of the user equipment end is the whole machine restart. Except after all ramdump of DDR, the analysis can also be carried out through the elf file of a specific subsystem, and the method of the invention sets the restart level of the subsystem to related when the subsystem has a coast, so that the system can not be crashed when the subsystem is abnormal, and the corresponding subsystem can be automatically restarted in the background. After the restart level is set to related, an elf file of the corresponding subsystem is generated when the crash occurs. The reason for the subsystem crash can also be analyzed by these elf files.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described system embodiments are merely exemplary, and it is exemplary that the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, and it is exemplary that a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
It should be noted that the above embodiments can be freely combined as necessary. The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A method for analyzing the crash of a subsystem is characterized by comprising the following steps:
embedding points on a kernel layer of a subsystem so as to obtain the embedded point data when the subsystem crashes;
and receiving the attribute data packet, and selecting and storing the corresponding dump file for analyzing the crash of the subsystem.
2. The method for analyzing the crash of the subsystem according to claim 1, wherein before the kernel layer embedding point of the subsystem so that the terminal device obtains the embedding point data when the subsystem crashes, the method further comprises the steps of:
and setting the restart level of each subsystem of the user edition in the terminal equipment to be related.
3. The method for analyzing the crash of subsystem as claimed in claim 2, further comprising the step of, after said setting the restart level of each subsystem of the user version in the terminal device to related:
and when the restart level of the subsystem is set to be related and the crash occurs, restarting the subsystem.
4. The method for analyzing the crash of subsystem as claimed in claim 2, further comprising the step of, after said setting the restart level of each subsystem of the user version in the terminal device to related:
and when the restart level of each subsystem is set to be related and the subsystem crashes, generating dump files of the subsystem.
5. The method for analyzing the crash of the subsystem according to claim 1, wherein the step of embedding points in a kernel layer of the subsystem so that the terminal device obtains the embedded points data when the subsystem crashes comprises the steps of:
transmitting the buried point of the kernel layer to a framwork layer interface function through android JNI communication;
inserting the buried point data into a launcher database through the frawork layer interface function;
and transmitting the data of the buried point to the webpage end in real time through the launcher database.
6. The method for analyzing the crash of the subsystem according to claim 1, wherein said receiving the attribute data packet and selecting the corresponding dump file for saving for analyzing the crash of the subsystem comprises the steps of:
analyzing and acquiring attributes and attribute values by using the attribute data packet;
selecting and storing the dump file of the subsystem according to the attribute and the attribute value;
wherein the dump file comprises a memory file when the subsystem is halted.
7. The method for analyzing the crash of the subsystem according to claim 1, wherein said receiving the attribute data packet and selecting the corresponding dump file for saving for analyzing the crash of the subsystem comprises the steps of:
receiving an attribute data packet returned by a webpage end, and opening a dump file collection switch of the subsystem by the terminal equipment;
and when the subsystem crashes again, automatically collecting dump files of the subsystem based on the attribute data packet so as to analyze the crash of the subsystem.
8. The method for analyzing the crash of the subsystem according to any one of claims 1 to 5, wherein after the attribute data packet returned by the receiving webpage end selects the corresponding dump file to be saved for analyzing the crash of the subsystem, the method comprises the following steps:
after the dump files are collected, compressing the dump files to generate dump compressed files;
and saving the dump compressed file and deleting the dump file.
9. A terminal device, which is applied to the method for analyzing the crash of the subsystem according to any one of claims 1 to 8.
10. A system for analyzing the crash of a subsystem, comprising the terminal device according to claim 9, a web page side;
and the webpage end is used for sending an attribute data packet for opening a dump file collection switch of the subsystem according to the buried point data so that the terminal equipment selects and stores the corresponding dump file for analyzing the crash of the subsystem.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011424291.9A CN112527558A (en) | 2020-12-08 | 2020-12-08 | Method, system and terminal equipment for analyzing crash of subsystem |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011424291.9A CN112527558A (en) | 2020-12-08 | 2020-12-08 | Method, system and terminal equipment for analyzing crash of subsystem |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112527558A true CN112527558A (en) | 2021-03-19 |
Family
ID=74998238
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011424291.9A Pending CN112527558A (en) | 2020-12-08 | 2020-12-08 | Method, system and terminal equipment for analyzing crash of subsystem |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112527558A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014106489A1 (en) * | 2013-01-07 | 2014-07-10 | 北京奇虎科技有限公司 | Method and system for processing browser crash information |
| CN106469185A (en) * | 2016-08-29 | 2017-03-01 | 浪潮电子信息产业股份有限公司 | A kind of method carrying out data collection in website statistics |
| CN111488261A (en) * | 2020-03-11 | 2020-08-04 | 北京健康之家科技有限公司 | User behavior analysis system, method, storage medium and computing device |
| CN111782416A (en) * | 2020-06-08 | 2020-10-16 | Oppo广东移动通信有限公司 | Data reporting method, device, system, terminal and computer readable storage medium |
-
2020
- 2020-12-08 CN CN202011424291.9A patent/CN112527558A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014106489A1 (en) * | 2013-01-07 | 2014-07-10 | 北京奇虎科技有限公司 | Method and system for processing browser crash information |
| CN106469185A (en) * | 2016-08-29 | 2017-03-01 | 浪潮电子信息产业股份有限公司 | A kind of method carrying out data collection in website statistics |
| CN111488261A (en) * | 2020-03-11 | 2020-08-04 | 北京健康之家科技有限公司 | User behavior analysis system, method, storage medium and computing device |
| CN111782416A (en) * | 2020-06-08 | 2020-10-16 | Oppo广东移动通信有限公司 | Data reporting method, device, system, terminal and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110320891B (en) | Railway vehicle braking system CAN bus message maintenance monitoring system and monitoring method | |
| CN108958927A (en) | Dispositions method, device, computer equipment and the storage medium of container application | |
| CN104246767A (en) | Telemetry system for a cloud synchronization system | |
| CN108108286A (en) | Method of data capture and device, server, storage medium | |
| CN102891873A (en) | Method for storing log data and log data storage system | |
| CN105550073A (en) | Database backup method and system thereof | |
| CN105589782A (en) | User behavior collection method based on browser | |
| CN102779030B (en) | A kind of manner of execution of registry operations and device | |
| CN113254320A (en) | Method and device for recording user webpage operation behaviors | |
| CN110134447A (en) | The system and method for BMC immediate updating hard disk information based on operating system | |
| CN103778024A (en) | Server system and message processing method thereof | |
| CN114168429A (en) | Error reporting analysis method and device, computer equipment and storage medium | |
| CN110431530B (en) | Expected collection of metrics and logs | |
| CN112527558A (en) | Method, system and terminal equipment for analyzing crash of subsystem | |
| CN102521339A (en) | System and method for dynamic access of data sources | |
| CN106685744A (en) | Fault elimination method, apparatus and system | |
| CN115543746A (en) | Graphics processor monitoring method, system and device and electronic equipment | |
| CN110262917A (en) | Host self-healing method, device, computer equipment and storage medium | |
| US20090055832A1 (en) | System, method and computer program product for evaluatng a test of an alternative system | |
| CN106612195A (en) | Data acquisition system and method of service robot | |
| CN112214407A (en) | Data verification control and execution method and corresponding device, equipment and medium | |
| CN112199568A (en) | Mobile APP data capturing method, device and system | |
| CN111935237B (en) | Log processing method and system, electronic device and storage medium | |
| CN113824651B (en) | Market data caching method and device, storage medium and electronic equipment | |
| CN111258862B (en) | Program log management method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |