Method and equipment for processing crash information

[0040]The application will be further described in detail below in conjunction with the drawings.

[0041]In a typical configuration of this application, the terminal, the equipment of the service network, and the trusted party all include one or more processors (CPU), input/output interfaces, network interfaces, and memory.

[0042]The memory may include non-permanent memory in a computer readable medium, random access memory (RAM) and/or non-volatile memory, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.

[0043]Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices.

[0044]The equipment referred to in this application includes but is not limited to user equipment, network equipment, or equipment formed by the integration of user equipment and network equipment through a network. The user equipment includes, but is not limited to, any mobile electronic product that can perform human-computer interaction with a user (for example, human-computer interaction through a touch panel), such as a smart phone, a tablet computer, etc., and the mobile electronic product can adopt any operation System, such as android operating system, iOS operating system, etc. Wherein, the network device includes an electronic device that can automatically perform numerical calculation and information processing in accordance with pre-set or stored instructions. Its hardware includes, but is not limited to, a microprocessor, an application specific integrated circuit (ASIC), and programmable logic. Devices (PLD), Field Programmable Gate Array (FPGA), Digital Signal Processor (DSP), embedded devices, etc. The network device includes, but is not limited to, a computer, a network host, a single network server, a set of multiple network servers, or a cloud composed of multiple servers; here, the cloud is composed of a large number of computers or network servers based on Cloud Computing, Among them, cloud computing is a type of distributed computing, a virtual supercomputer composed of a group of loosely coupled computer sets. The network includes, but is not limited to, the Internet, a wide area network, a metropolitan area network, a local area network, a VPN network, and a wireless ad hoc network (Ad Hoc network). Preferably, the device may also be a program running on the user equipment, network equipment, or user equipment and network equipment, network equipment, touch terminal, or a device formed by integrating network equipment and touch terminal through a network.

[0045]Of course, those skilled in the art should understand that the above-mentioned equipment is only an example, and other existing or possible future equipment, if applicable to this application, should also be included in the scope of protection of this application, and is included here by reference. this.

[0046]In the description of the present application, "plurality" means two or more, unless otherwise specifically defined.

[0047]figure 1 A typical scenario of the present application is shown. The user equipment generates a target program task. For example, the user equipment obtains a target application, and executes the target application and detects the fault condition sent in the target application as the The target program task, the user equipment and the network device corresponding to the reading application establish a communication connection through a wired or wireless manner, and based on the communication connection, the network device receives a message sent by the user equipment and detects that the target program task is being executed. According to the crash information and buried point information, the network device determines the requirement (for example, functional stage) for generating the crash information according to the buried point information, and creates a repair requirement task based on the requirement and the crash information to notify the developer and repairer. Wherein, the user equipment includes, but is not limited to, computing devices such as mobile phones, tablets, and laptops (with touch screens), and the device can run any system (for example, including but not limited to IOS, Android).

[0048]referencefigure 1 The system shown,figure 2 A system method for processing crash information according to an embodiment of the present application is shown, and the method includes:

[0049]The user equipment generates a target program task, where the target program task includes one or more requirements to be executed, and information about buried points in each requirement, and the buried point information is set at the start position of each requirement, And in response to a start event in the user equipment, execute the target program task;

[0050]During the execution of the target program task, if crash information is detected when the target demand in the target program task is executed, the user equipment sends the crash information and the buried point information to the corresponding network device ;

[0051]The network device receives the crash information and the buried point information, and queries the buried point information in the mapping relationship between points and requirements to determine the target demand where the buried point information is located, and establishes the target demand and the location. The corresponding relationship between the crash information is described, and repair demand task information is generated according to the corresponding relationship between the target demand and the crash information.

[0052]image 3 A method for processing crash information according to an embodiment of the present application is shown, which is applied to a user equipment, and the method includes step S101, step S102, and step S103.

[0053]Specifically, in step S101, the user equipment generates a target program task, where the target program task includes one or more requirements to be executed, and information about the buried points in each requirement, and the buried point information is set in all the requirements. Describe the starting position of each requirement. For example, the user equipment obtains an application program, for example, the application program is compiled and packaged by the developer in advance, and the user equipment generates a target program task according to the application program, where the target program task includes the application program and is used for subsequent online Then run the application and obtain the log information generated during the running of the application. For example, the application program corresponding to the target program task is used to perform one or more requirements, where the requirements include functional modules that the application program can complete (for example, used to implement a series of functions such as camera, login, and publishing), Each requirement can correspond to a function. In some embodiments, for each requirement, in the application development process, the information of each requirement has been successfully buried in the requirement in advance, and the developer can manually enter the information in the process of compiling the corresponding application. Bury points in the requirements, for example, define a requirement as A, define A1 when A starts, and then define A2 when the requirement ends. You can manually bury the points at the two points A1 and A2, and the application completes the entire logic of the requirement If there is crash information, it must be between A1 and A2, where the buried point is used here to capture the occurrence of the event, and used to locate the start time and end time of the demand, and the buried point is set in code form In the demand, or set in the demand in the form of embedded point SDK. In some embodiments, the user equipment can automatically download points during the program compilation period, such as the above-mentioned requirement A. The development does not need to care when to point A1 and A2, and uniformly passes tools (for example, some compilation tools gradle plug-in Etc.) Operate the points A1 and A2 according to certain rules, where the rules are artificially defined to allow the system to recognize, for example, by identifying the identification of each stage of the program to determine when to bury the point (for example, module program When starting, you must use a designated special identifier such as crash_start, which is convenient for the system to identify).

[0054]In some embodiments, for each requirement, the point is usually buried at the beginning of the requirement. For example, if a point is buried at the beginning of each requirement, then the program logic has a clear start. In this way, the logic between each requirement can be connected. For example, a program has to go through the three requirement stages of ABC, A has a start, C has a start, if B does not, then it cannot be determined when a crash message appears in the AB stage Specifically, is A crashed information, or B crashed information. Therefore, for each requirement, a point is buried at the starting point so that subsequent crash information occurs. Based on the point where the crash information occurs, the previous point information closest to the point where the crash information occurs is used as the crash information correspondence Of buried information.

[0055]In some embodiments, the buried point information is also set at the end position of each demand. For example, in order to ensure the integrity of a requirement (function), the user equipment sets the buried point information at the starting point of each requirement and the ending point of each requirement, thereby ensuring the integrity of the requirement. If crash information occurs during the execution of the program, the user device can trace back to one burial point based on the time when the crash information occurred, and trace back to one burial point, so as to accurately determine the crash information based on the two burial points The generation of demand stage, thereby reducing the probability of false alarms.

[0056]In some embodiments, in step S101, the user equipment sends a burying request to the network device, where the burying request includes the one or more to-be-executed requirements; receiving the network device is the One or more buried point information for the allocation of requirements to be executed; generating a target program task, where the target program task includes one or more requirements to be executed, and the buried point information in each requirement, the buried point Information is set at the beginning of each demand. For example, in the creation phase of the one or more requirements to be executed, the network device will determine the buried point for each requirement and establish a mapping relationship between the requirement and the buried point identifier of the buried point. When the user equipment is in the development stage of the target program, the user equipment sends a request to the network device to register a request, and the network device responds to the request to allocate a request to one or more of the requests to be executed. Point information, where each point information corresponds to a different character string to distinguish different point information. For example, for requirement A, assign point A1 and A2; for requirement B, assign point B1, and so on, in some implementations In an example, the amount of buried information allocated by network equipment for each requirement is usually one or two. For some pending requirements that are marked as key requirements, the amount of buried information allocated by network equipment for the key requirements is not limited. . After the user equipment receives the buried point information of each demand to be executed, the target program task is generated according to the each demand to be executed and the buried point information in each demand, and the target program task is used to execute the target application. . In some embodiments, for some to-be-executed requirements that are marked as key requirements, the amount of information that the network device allocates to the key requirements may not be limited. For example, the key requirements include one or more sub-requirements (for example, camera The shooting function, picture editing function, and social space sharing function are all integrated into a larger range of shooting functions). The network device allocates buried point information for each sub-requirement according to one or more sub-requirements of the key requirement. When the crash information is generated in the demand, the user equipment can store the crash information and the corresponding buried point information (for example, the crash information, including the identification mark, software and hardware information, and time point, etc.). The buried point with the smallest time difference is reported as the corresponding buried point information) to the network device. Based on this, the network device directly repairs the sub-requirement without repairing the entire key demand, thereby improving the efficiency and accuracy of application repair.

[0057]In step S102, the user equipment executes the target program task in response to a start event in the user equipment. For example, after the target application in the target program task is online (that is, running in the user device), the user can manually start the target application or based on other startup events in the user device (for example, the target application is called by other programs). The target application program) starts the target application program, and the user equipment executes the target program task, that is, executes the target application program.

[0058]In step S103, in the process of executing the target program task, if the user equipment detects crash information when executing to the target demand in the target program task, it sends the crash information and the buried point information to the corresponding Network equipment. For example, the user equipment executes in the order of requirements in the target program task, or executes the requirements corresponding to the trigger operation according to the user's trigger operation. When the program detects the crash information in the process of executing the logic of the requirement, the user equipment determines Currently, the target program has a fault, and the crash information and the buried point information corresponding to the target demand are reported to the network device, where the crash information is expressed as a program crash or a crash. In some embodiments, the crash information It can also show that the program does not respond. The reasons for the crash information include code bugs, such as array out of bounds, empty insertion, multi-thread safety, access to wild pointers, sending unimplemented selectors, etc. The user equipment detects whether a crash has occurred by collecting log information Information, when the crash information is generated, it is easy to cause the program to continue to run, data loss, and a bad user experience for the user. The crash information and the corresponding buried point information are reported, and the network device can respond to important needs in a timely manner to generate crash information. Kind of emergency. For example, the user equipment executes the target demand in a logical order of execution. For example, there are ten execution steps 1-10 in the target demand. Step 1 is the starting step of the target demand, and the starting position is set with a buried point. Information, when the five steps of 1-5 are executed, the crash information is generated. If 6-10 is not executed, the user device can store the crash information and the buried information in the executed steps (that is, the buried information in the starting step) Report to the network device.

[0059]In some embodiments, taking a buried point A as an example, there is a multi-thread in demand A, demand A has finished executing demand B, but the thread in demand A is still executing in the process of executing demand B. At this time, if the thread If there is a crash message, the corresponding crash message still corresponds to requirement A. Regardless of whether the execution requirement is single-threaded or multi-threaded, each thread needs to pass in the buried point information set in the corresponding requirement.

[0060]For example, the application in the target program task is already running online. During the running of the application, based on the user's trigger operation, the user device starts to call the camera function and executes the shooting operation, where the camera function is, before being put into operation, For example, in the compiling stage, the user equipment based on the embedding code allocated by the server, embeds the embed in the invocation phase of the function and in the end phase of the function (for example, the stage of saving the picture after the shooting is completed). When the user uses the camera function to shoot, a crash (crash message) is generated and the captured picture is not saved. For example, the shooting screen is stuck, the screen remains motionless, or the function suddenly flashes, causing the user device to return to the desktop interface. Report the crash and the buried point information in the camera function to the server.

[0061]In some embodiments, in step S103, in the process of executing the target program task, if the user equipment does not detect crash information when executing to the target demand in the target program task, execute the target demand sequentially. Next demand, and detect whether crash information is detected during the execution of the next demand. For example, in the process of executing the target program task, based on the user's trigger operation, the user equipment determines that the demand called by the user equipment according to the trigger operation is the target demand, and the user equipment executes the target demand. In the process of the target demand, the user equipment detects whether there is a crash log from the log. If it exists, the user equipment determines that there is crash information; otherwise, the user equipment determines that the crash information is not detected when the target demand is executed. For example, the user equipment can use the system mechanism Obtain crash information directly (the system will throw an exception when there is an exception in the running program, and this exception is the information that can be captured, that is, the exception is determined to be the crash information). On this basis, the user device successfully executes the target demand, It executes the next requirement based on the user’s re-triggered operation or the call of other programs in the user equipment, and detects whether crash information is generated during the execution of the next requirement, and so on, the user equipment will execute the requirements generated in the process Report the crash information.

[0062]In some embodiments, in step S103, in the process of executing the target program task, the user equipment responds to the triggering operation of the target demand in the user equipment, and if crash information is detected while executing the target demand, The crash information and the buried point information are sent to the corresponding network device. For example, in response to the trigger operation on the target demand in the user equipment, the user equipment has not yet executed the target demand, and the user equipment determines the target demand according to the trigger operation (for example, the user manually activates a function and sets the function As the target demand to be executed by the user), the user equipment starts to execute the target demand based on the trigger operation, and detects whether crash information is generated when the target demand is executed, and if so, sends the crash information and the buried point information To the corresponding network device. For the user's need to actively select and start, if a crash information is generated, it can be reported in time to ensure that the user crashes again during subsequent use.

[0063]In some embodiments, in step S103, in the process of executing the target program task, the user equipment selects one of the one or more requirements to be executed; if the crash information is detected when the requirement is executed, the The demand is taken as the target demand, and the crash information and the buried point information are sent to the corresponding network device. For example, in the process of executing the target program task, the user equipment may select a requirement according to the original program sequence of multiple requirements in the target program, or the user equipment may randomly select a requirement and execute the requirement as the target requirement. If the crash information is detected during the execution of the target demand, the crash information and the buried point information are sent to the corresponding network device. For another example, the user equipment selects a requirement and generates crash information in the process of executing the requirement. The user equipment uses this requirement as the target requirement, and reports the crash information and the buried point information in the requirement. If the requirement is being executed No crash information is generated during the process, and the user equipment continues to execute other requirements to determine the target requirement from the other requirements.

[0064]In some embodiments, in step S103, in the process of executing the target program task, the user equipment selects one of the one or more requirements to be executed; if no crash information is detected when the requirement is executed, traverse Execute other requirements among the one or more requirements to be executed until crash information is detected, and use the demand that generates the crash information as the target demand, and send the crash information and the buried point information to the corresponding Network equipment. For example, in the process of executing the target program task, the user equipment can select a requirement according to the original program sequence of multiple requirements in the target program, or the user equipment randomly selects a requirement, and then the user equipment executes the requirement. If no crash information is generated during the execution of the requirement, the user device will continue to extract a requirement from other requirements in the target program task according to the order or according to certain rules for execution. If no crash information is generated during the execution, continue in the remaining Continue to select a requirement from other requirements, and proceed by analogy until it detects that a requirement has crash information, and report the crash information and the buried point information in the requirement. If the target program task has never been generated during the execution of the target program task After the crash information, the user equipment can report the required data according to normal rules.

[0065]In some embodiments, in step S103, in the process of executing the target program task, if the user equipment detects crash information when executing to the target demand in the target program task, the crash information is combined with the The buried point information is bound, and the bound crash information and the buried point information are sent to the corresponding network device. For example, on the premise that the crash information is detected when executing to the target demand in the target program task, the user equipment will establish a mapping relationship between the crash information and the corresponding buried point information, and compare the crash information with the corresponding buried point information The mapping relationship of is reported to the network device, so that the subsequent network device can determine the demand for the buried point information corresponding to the crash information from the complex data according to the mapping relationship. It avoids the situation that developers need to manually analyze the corresponding functions in the user equipment and then repair them due to the large amount of crash information that is usually collected. This reduces the pressure on the user equipment, and the network equipment uniformly controls resources for subsequent processing.

[0066]In some embodiments, the method further includes step S104 (not shown). In step S104, the user equipment executes the shutdown of the target demand in response to a shutdown event in the user equipment. For example, the closing time may be that the user manually ends the target demand according to the system prompt after the crash information is generated, or it may be that the user equipment executes the closing of the target demand based on the closing instruction on the target demand sent by the network device After the target demand is closed, the user equipment can continue to execute other demands without being affected by the target demand being closed. In some embodiments, the user may choose to continue waiting or directly re-execute the target demand when faced with a crash event in the target demand.

[0067]Figure 4 A method for processing crash information according to an embodiment of the present application is shown, which is applied to a network device. The method includes step S201, step S202, and step S203.

[0068]Specifically, in step S201, the network device receives the crash information and the buried point information sent by the user equipment. For example, in the process of the user equipment executing a target demand, if the user equipment detects the crash information, the user equipment reports the crash information and the buried point information in the target demand to the network device for the network device to subsequently base on the buried point information Determine the corresponding target demand.

[0069]In step S202, the network device queries the buried point information in the mapping relationship between points and requirements to determine the target demand where the buried point information is located, and establishes the corresponding relationship between the target demand and the crash information. For example, a network device allocates a buried point for each requirement in the application before each application goes online. Each buried point uses the unique buried point identifier of the buried point to form a mapping relationship with the corresponding demand, and is determined by The user equipment embeds points in each demand, so that the operating data of the application can be obtained in time through the embed points after going online. That is, the network device pre-stores the mapping relationship between the buried point and the demand, and the network device queries the mapping relationship according to the buried point provided by the user equipment to determine the corresponding target demand, and establishes the corresponding relationship between the target demand and the crash information. For subsequent automated repairs.

[0070]In step S203, the network device generates repair demand task information according to the corresponding relationship between the target demand and the crash information. For example, on the premise of determining the correspondence between the target demand and the crash information, the network device automatically creates the demand for repairing the crash information as a repair task. In some embodiments, the method further includes step S204 (not shown) In step S204, the network device provides the repair demand task information to the repair personnel. For example, the network device can directly issue the repair task to the product, development, and testing departments or the corresponding personnel in each department directly responsible for the target demand, where the repair task may include crash information facing the demand. Measures. On the premise that the repair demand task information is directly provided to the repair personnel, the repair personnel can directly receive the corresponding repair tasks, without having to spend time again between various departments to arrange the corresponding repair tasks, and there is no need for personnel to track, thus speeding up the repair Cycle, improve the processing efficiency of repair tasks.

[0071]In some embodiments, the method further includes step S205 (not shown). In step S205, the network device detects whether the quantity information of the crash information is greater than a preset quantity threshold, and if so, sends information to the user equipment The offline instruction of the target demand; receiving feedback information returned by the user equipment based on the offline instruction. For example, in the process of the user equipment executing the target demand, the user equipment judges whether crash information is generated according to the log information, and the amount of crash information, for example, generated during the process from the start of the target demand to the end of the target demand The number of crash messages, or the number of crash messages generated when the user equipment continuously re-executes the target program within a preset time (for example, in this case, the target demand is not executed to the end), and the network device detects the number Whether it is greater than the preset number threshold, if it is greater, the network device can automatically close the online demand according to the corresponding relationship between the demand and the crash information, and perform emergency treatment on the demand (for example, offline), in some embodiments When the target program starts to execute, the user equipment can actively request to obtain offline instructions from the network device in advance, so as to deal with it in a timely manner when too much crash information is subsequently generated, and to improve the maximum usability of the application.

[0072]Figure 5 Shows a flow chart of a method for processing crash information according to an embodiment of the present application. The client is executing an application, and when the logic reaches the requirement A, the user equipment detects whether there is a crash (crash information), where: There is a buried point A in the demand A, and the buried point is set at the start position of the demand A. If the user equipment detects a crash, it will report the crash and the buried point A to the server. If the crash is not detected, the client continues to execute the requirement B, where there is a buried point B in the requirement B, and the buried point is set at the requirement B Start position. After the server receives the crash and the buried point A, the server finds the corresponding requirement A according to the buried point A, and finds the related automatic creation requirement according to the requirement A, and informs the development to repair the requirement.

[0073]Figure 6 A user equipment for processing crash information according to an embodiment of the present application is shown. The user equipment includes a first module 101, a second module 102, and a third module 103.

[0074]Specifically, a module 101 is used to generate a target program task, where the target program task includes one or more requirements to be executed, and the buried point information in each requirement, and the buried point information is set at all Describe the starting position of each requirement. For example, the user equipment obtains an application program, for example, the application program is compiled and packaged by the developer in advance, and the user equipment generates a target program task according to the application program, where the target program task includes the application program and is used for subsequent online Then run the application and obtain the log information generated during the running of the application. For example, the application program corresponding to the target program task is used to perform one or more requirements, where the requirements include functional modules that the application program can complete (for example, used to implement a series of functions such as camera, login, and publishing), Each requirement can correspond to a function. In some embodiments, for each requirement, in the application development process, the information of each requirement has been successfully buried in the requirement in advance, and the developer can manually place the information in the process of compiling the corresponding application. Buried points in demand.

[0075]The one-two module 102 is configured to execute the target program task in response to a start event in the user equipment. For example, after the target application in the target program task is online (that is, running in the user device), the user can manually start the target application or based on other startup events in the user device (for example, the target application is called by other programs). Target application) starts the target application, and the user equipment executes the target program task, that is, executes the target application.

[0076]The 13th module 103 is used to send the crash information and the buried point information to the corresponding information if the crash information is detected when the target demand in the target program task is executed during the execution of the target program task Network equipment. For example, the user equipment executes in the order of requirements in the target program task, or executes the requirements corresponding to the trigger operation according to the user's trigger operation. When the program detects the crash information in the process of executing the logic of the requirement, the user equipment determines Currently, the target program has a fault, and the crash information and the corresponding buried point information are reported to the network device. The crash information is expressed as a program crash or crash. The causes of the crash information include code bugs, such as array out of bounds, insertion Empty, multi-threaded safety, access to wild pointers, sending unimplemented selectors, etc. The user equipment detects whether crash information is generated by collecting log information. When the crash information is generated, it is easy to cause the program to fail to continue running and data loss, which will bring bad to users. The user experience, the crash information and the corresponding buried point information are reported, and the network equipment can respond to important needs in a timely manner to generate crash information such emergency events.

[0077]Here, the specific implementations of the above-mentioned one-one module 101, one-two module 102, and one-three module 103 are as follows:image 3 The embodiments of steps S101, S102, and S103 in the above are the same or similar, so they will not be repeated here, and they are included here by reference.

[0078]In some embodiments, the buried point information is also set at the end position of each demand. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0079]In some embodiments, a module 101 is used

[0080]Sending a burial request to the network device, where the burial request includes the one or more requirements to be executed;

[0081]Receiving the buried point information allocated by the network device for the one or more requirements to be executed;

[0082]A target program task is generated, where the target program task includes one or more requirements to be executed, and information about buried points in each requirement, and the buried point information is set at the start position of each requirement. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0083]In some embodiments, a three-module 103 is also used for

[0084]In the process of executing the target program task, if no crash information is detected when the target demand in the target program task is executed, the next demand of the target demand is executed sequentially, and the execution of the next demand is detected Whether the crash information was detected during the process. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0085]In some embodiments, the one-third module 103 is used to respond to the triggering operation of the target demand in the user equipment in the process of executing the target program task, if a crash information is detected when the target demand is executed , Sending the crash information and the buried point information to the corresponding network device. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0086]In some embodiments, a three-module 103 is used

[0087]In the process of executing the target program task, select one of the one or more requirements to be executed;

[0088]If crash information is detected when the demand is executed, the demand is taken as the target demand, and the crash information and the buried point information are sent to the corresponding network device. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0089]In some embodiments, a three-module 103 is used

[0090]In the process of executing the target program task, select one of the one or more requirements to be executed;

[0091]If the crash information is not detected when the requirement is executed, the other requirements in the one or more to-be-executed requirements are traversed and executed until the crash information is detected, and the requirement that generates the crash information is taken as the target requirement, and all The crash information and the buried point information are sent to the corresponding network device. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0092]In some embodiments, a three-module 103 is used

[0093]In the process of executing the target program task, if crash information is detected when the target demand in the target program task is executed, the crash information is bound with the buried point information, and the bound information The crash information and the buried point information are sent to the corresponding network device. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0094]In some embodiments, the user equipment further includes a four-template 104 (not shown), and a four-template 104, which is used to execute the closing of the target demand in response to a shutdown event in the user equipment. Related operations andimage 3 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0095]Figure 7 A network device for processing crash information according to an embodiment of the present application is shown. The network device includes a two-one module 201, a two-two module 202, and a two-three module 203.

[0096]Specifically, the two-to-one module 201 is used to receive crash information and buried point information sent by the user equipment. For example, in the process of the user equipment executing a target demand, if the user equipment detects the crash information, the user equipment reports the crash information and the buried point information in the target demand to the network device for the network device to subsequently base on the buried point information Determine the corresponding target demand.

[0097]The 22nd module 202 is configured to query the buried point information in the mapping relationship between points and requirements to determine the target demand where the buried point information is located, and establish a corresponding relationship between the target demand and the crash information. For example, a network device allocates a burying point for each demand in the application before each application goes online, and the user device burys the point in each demand, so that the application’s information can be obtained in time through the burying point after it goes online. Operating data. That is, the network device pre-stores the mapping relationship between the buried point and the demand, and the network device queries the mapping relationship according to the buried point provided by the user equipment to determine the corresponding target demand, and establishes the corresponding relationship between the target demand and the crash information. For subsequent automated repairs.

[0098]The second and third module 203 is configured to generate repair demand task information according to the corresponding relationship between the target demand and the crash information. For example, on the premise of determining the corresponding relationship between the target demand and the crash information, the network device automatically creates the demand for repairing the crash information as a repair task.

[0099]In some embodiments, the network device further includes a two-four module 204 (not shown), and a two-four module 204 is used to provide the repairing personnel with the repair demand task information. Related operations andFigure 4 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0100]In some embodiments, the network device further includes a second-five module 205 (not shown), and a second-five module 205 for

[0101]Detecting whether the quantity information of the crash information is greater than a preset quantity threshold, and if so, sending an offline instruction regarding the target demand to the user equipment;

[0102]Receiving feedback information returned by the user equipment based on the offline instruction. Related operations andFigure 4 The illustrated embodiments are the same or similar, so they will not be repeated here, and are included here by reference.

[0103]Figure 8 A system device for processing crash information according to an embodiment of the present application is shown. The system includes:

[0104]The user equipment generates a target program task, where the target program task includes one or more requirements to be executed, and information about buried points in each requirement, and the buried point information is set at the start position of each requirement, And in response to a start event in the user equipment, execute the target program task;

[0105]In the process of executing the target program task, if crash information is detected when the target demand in the target program task is executed, the user equipment sends the crash information and the buried point information to the corresponding network device ;

[0106]The network device receives the crash information and the buried point information, and queries the buried point information in the mapping relationship between points and requirements to determine the target demand where the buried point information is located, and establishes the target demand and the buried point information. The corresponding relationship between the crash information is described, and the repair demand task information is generated according to the corresponding relationship between the target demand and the crash information.

[0107]In addition to the methods and devices described in the foregoing embodiments, this application also provides a computer-readable storage medium that stores computer code, and when the computer code is executed, such as any one of the preceding items The method described is executed.

[0108]The present application also provides a computer program product. When the computer program product is executed by a computer device, the method described in any of the preceding items is executed.

[0109]This application also provides a computer device, which includes:

[0110]One or more processors;

[0111]Memory, used to store one or more computer programs;

[0112]When the one or more computer programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any one of the preceding items.

[0113]Picture 9Shows an exemplary system that can be used to implement the various embodiments described in this application;

[0114]Such asPicture 9In some embodiments shown, the system 300 can be used as any device in each of the described embodiments. In some embodiments, the system 300 may include one or more computer-readable media having instructions (for example, system memory or NVM/storage device 320) and be coupled with the one or more computer-readable media and configured to execute The instructions are one or more processors (eg, the processor(s) 305) that implement the modules to perform the actions described in this application.

[0115]For one embodiment, the system control module 310 may include any suitable interface controller to provide at least one of the processor(s) 305 and/or any suitable device or component in communication with the system control module 310 Any appropriate interface.

[0116]The system control module 310 may include a memory controller module 330 to provide an interface to the system memory 315. The memory controller module 330 may be a hardware module, a software module, and/or a firmware module.

[0117]The system memory 315 may be used to load and store data and/or instructions for the system 300, for example. For one embodiment, the system memory 315 may include any suitable volatile memory, for example, a suitable DRAM. In some embodiments, the system memory 315 may include a double data rate type quad synchronous dynamic random access memory (DDR4 SDRAM).

[0118]For an embodiment, the system control module 310 may include one or more input/output (I/O) controllers to provide an interface to the NVM/storage device 320 and the communication interface(s) 325.

[0119]For example, NVM/storage device 320 may be used to store data and/or instructions. The NVM/storage device 320 may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable non-volatile storage device(s) (e.g., one or more hard disk drives ( HDD), one or more compact disc (CD) drives and/or one or more digital versatile disc (DVD) drives).

[0120]The NVM/storage device 320 may include storage resources that are physically part of the device on which the system 300 is installed, or it may be accessed by the device without necessarily being a part of the device. For example, the NVM/storage device 320 may be accessed via the communication interface(s) 325 through the network.

[0121]The communication interface(s) 325 may provide an interface for the system 300 to communicate through one or more networks and/or with any other suitable devices. The system 300 can wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols.

[0122]For one embodiment, at least one of the processor(s) 305 may be packaged with the logic of one or more controllers of the system control module 310 (eg, the memory controller module 330). For one embodiment, at least one of the processor(s) 305 may be packaged with the logic of one or more controllers of the system control module 310 to form a system in package (SiP). For one embodiment, at least one of the processor(s) 305 may be integrated with the logic of one or more controllers of the system control module 310 on the same mold. For one embodiment, at least one of the processor(s) 305 may be integrated with the logic of one or more controllers of the system control module 310 on the same mold to form a system on chip (SoC).

[0123]In various embodiments, the system 300 may be, but is not limited to, a server, a workstation, a desktop computing device, or a mobile computing device (for example, a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.). In various embodiments, the system 300 may have more or fewer components and/or different architectures. For example, in some embodiments, the system 300 includes one or more cameras, keyboards, liquid crystal display (LCD) screens (including touchscreen displays), non-volatile memory ports, multiple antennas, graphics chips, application specific integrated circuits ( ASIC) and speakers.

[0124]It should be noted that this application can be implemented in software and/or a combination of software and hardware. For example, it can be implemented using an application specific integrated circuit (ASIC), a general purpose computer or any other similar hardware device. In an embodiment, the software program of the present application may be executed by a processor to realize the steps or functions described above. Similarly, the software program (including related data structure) of the present application can be stored in a computer-readable recording medium, such as RAM memory, magnetic or optical drive or floppy disk and similar devices. In addition, some steps or functions of the present application may be implemented by hardware, for example, as a circuit that cooperates with a processor to execute each step or function.

[0125]In addition, a part of this application can be applied as a computer program product, such as a computer program instruction, when it is executed by a computer, through the operation of the computer, the method and/or technical solution according to this application can be invoked or provided. Those skilled in the art should understand that the computer program instructions in the computer readable medium include but are not limited to source files, executable files, installation package files, etc. Correspondingly, the manner in which computer program instructions are executed by the computer includes but not Limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction before executing the corresponding post-installation program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium that can be accessed by a computer.

[0126]Communication media includes media by which communication signals containing, for example, computer-readable instructions, data structures, program modules, or other data are transmitted from one system to another system. Communication media may include conductive transmission media (such as cables and wires (for example, optical fiber, coaxial, etc.)) and wireless (unguided transmission) media that can propagate energy waves, such as sound, electromagnetic, RF, microwave, and infrared . Computer readable instructions, data structures, program modules or other data may be embodied as, for example, a modulated data signal in a wireless medium such as a carrier wave or similar mechanism such as embodied as part of spread spectrum technology. The term "modulated data signal" refers to a signal whose one or more characteristics have been altered or set in such a way as to encode information in the signal. Modulation can be analog, digital or mixed modulation techniques.

[0127]By way of example and not limitation, computer-readable storage media may include volatile, nonvolatile, and nonvolatile, nonvolatile, nonvolatile, and nonvolatile, or Removable and non-removable media. For example, computer-readable storage media include, but are not limited to, volatile memory, such as random access memory (RAM, DRAM, SRAM); and non-volatile memory, such as flash memory, various read-only memories (ROM, PROM, EPROM) , EEPROM), magnetic and ferromagnetic/ferroelectric memory (MRAM, FeRAM); and magnetic and optical storage devices (hard disks, tapes, CDs, DVDs); or other currently known media or future developments that can be stored for computer systems Computer readable information/data used.

[0128]Here, an embodiment according to the present application includes a device including a memory for storing computer program instructions and a processor for executing the program instructions, wherein, when the computer program instructions are executed by the processor, trigger The operation of the device is based on the aforementioned methods and/or technical solutions according to multiple embodiments of the present application.

[0129]For those skilled in the art, it is obvious that the present application is not limited to the details of the foregoing exemplary embodiments, and the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the application. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-limiting. The scope of this application is defined by the appended claims rather than the above description, and therefore it is intended to fall into the claims. All changes within the meaning and scope of the equivalent elements of is included in this application. Any reference signs in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "including" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the device claims can also be implemented by one unit or device through software or hardware. Words such as first and second are used to denote names, but do not denote any specific order.