System software dumping method and device, electronic equipment and readable storage medium

Abstract

The application discloses a system software dumping method and device, electronic equipment and readable storage medium, and is applied to the technical field of program dumping. The system software dumping method comprises the following steps: when detecting that a device has a fault, starting a boot dumping function according to a dumping peripheral connected with the device; determining a target fault program, cloning the target fault program according to the boot dumping function, and obtaining a fault program mirror file of the target fault program, wherein the target fault program comprises a complete file system program or a partial file system program, and the target fault program comprises a complete file system or a partial file system; and sending the fault program mirror file to the dumping peripheral. The application solves the technical problem that the operation of the dumping process is complex in the prior art.

Description

Technical Field

[0001] This application relates to the field of program dumping technology, and in particular to a system software dumping method, apparatus, electronic device and readable storage medium. Background Technology

[0002] With the development of information technology, various electronic products have gradually developed comprehensive after-sales processes. When users encounter product malfunctions, software developers need to analyze and resolve the issue. However, some malfunctions only occur in the user's environment and cannot be reproduced in the software developer's local environment. Therefore, customer service personnel need to visit the user's location to collect fault information and then provide it to the software developer for analysis. However, this approach, especially considering user feedback in overseas markets, is too costly due to the high cost of traveling to analyze problems on-site, and the process of transferring the entire faulty program from the user's end to the software developer's end is complex. Summary of the Invention

[0003] The main objective of this application is to provide a system software dumping method, apparatus, electronic device, and readable storage medium, aiming to solve the technical problem of complex operation in the dumping process in the prior art.

[0004] To achieve the above objectives, this application provides a system software dumping method, applied to a system software dumping device, the system software dumping method comprising:

[0005] When a device malfunction is detected, the guided dump function is initiated based on the dump peripheral connected to the device.

[0006] Identify the target faulty program, clone the target faulty program according to the boot dump function, and obtain the faulty program image file of the target faulty program, wherein the target faulty program includes a complete file system program or a partial file system program;

[0007] The fault program image file is sent to the dump peripheral.

[0008] Optionally, the step of initiating the boot dump function based on the dump peripheral connected to the device includes:

[0009] Detect whether a dump verification file exists in the dump peripheral;

[0010] If a dump verification file is detected in the dump peripheral, the preset control system is triggered to start, and the boot dump function corresponding to the dump verification file is enabled through the started preset control system.

[0011] Optionally, the step of determining the target fault procedure includes:

[0012] Identify the faulty system software in the device and determine the complete file system program corresponding to the faulty system software;

[0013] By detecting the scope of faults in the complete file system program, the complete file system program or the local file system program is identified as the target fault program.

[0014] Optionally, the step of detecting the scope of faults in the complete file system program includes:

[0015] The complete file system program is divided into multiple program partitions based on the dump verification file;

[0016] Locate the faulty program partition in each of the program partitions;

[0017] The faulty program partition is defined as the fault range of the faulty system software.

[0018] Optionally, the step of locating the faulty program partition in each of the program partitions includes:

[0019] Send a probe request to each program node in each program partition, and receive the probe result fed back by each program node based on the probe request;

[0020] If there is a program node whose detection result is abnormal, then the program partition corresponding to the program node whose detection result is abnormal is regarded as the faulty program partition.

[0021] Optionally, the step of determining whether a complete file system program or a partial file system program is the target faulty program includes:

[0022] If the faulty system software is detected and the fault scope has been determined, then the local file system within the fault scope is designated as the target faulty program;

[0023] If the faulty system software is detected and the scope of the fault cannot be determined, the complete file system program will be used as the target faulty program.

[0024] Optionally, the step of dividing the complete file system program into multiple program partitions based on the dump verification file includes:

[0025] Detect whether a preset program partitioning rule exists in the dump verification file;

[0026] If the preset program partitioning rule exists, the program that has malfunctioned will be divided into multiple program partitions according to the preset program partitioning rule;

[0027] If the preset program partitioning rule does not exist, the program is divided into multiple program partitions based on the functional type of each part.

[0028] To achieve the above objectives, this application also provides a system software dumping device, which is applied to a system software dumping equipment, and the system software dumping device includes:

[0029] The connection module is used to initiate a guided dump function based on the dump peripheral connected to the device when a device malfunction is detected.

[0030] The cloning module is used to identify the target faulty program, clone the target faulty program according to the boot dump function, and obtain the faulty program image file of the target faulty program, wherein the target faulty program includes a complete file system program or a partial file system program.

[0031] The dump module is used to send the fault program image file to the dump peripheral.

[0032] Optionally, the connection module is further configured to:

[0033] Detect whether a dump verification file exists in the dump peripheral;

[0034] If a dump verification file is detected in the dump peripheral, the preset control system is triggered to start, and the boot dump function corresponding to the dump verification file is enabled through the started preset control system.

[0035] Optionally, the cloning module is further configured to:

[0036] Identify the faulty system software in the device and determine the complete file system program corresponding to the faulty system software;

[0037] By detecting the scope of faults in the complete file system program, the complete file system program or the local file system program is identified as the target fault program.

[0038] Optionally, the cloning module is further configured to:

[0039] The complete file system program is divided into multiple program partitions based on the dump verification file;

[0040] Locate the faulty program partition in each of the program partitions;

[0041] The faulty program partition is defined as the fault range of the faulty system software.

[0042] Optionally, the cloning module is further configured to:

[0043] Send a probe request to each program node in each program partition, and receive the probe result fed back by each program node based on the probe request;

[0044] If there is a program node whose detection result is abnormal, then the program partition corresponding to the program node whose detection result is abnormal is regarded as the faulty program partition.

[0045] Optionally, the cloning module is further configured to:

[0046] If the faulty system software is detected and the fault scope has been determined, then the local file system within the fault scope is designated as the target faulty program;

[0047] If the faulty system software is detected and the scope of the fault cannot be determined, the complete file system program will be used as the target faulty program.

[0048] Optionally, the cloning module is further configured to:

[0049] Detect whether a preset program partitioning rule exists in the dump verification file;

[0050] If the preset program partitioning rule exists, the program that has malfunctioned will be divided into multiple program partitions according to the preset program partitioning rule;

[0051] If the preset program partitioning rule does not exist, the program is divided into multiple program partitions based on the functional type of each part.

[0052] This application also provides an electronic device, the electronic device comprising: a memory, a processor, and a program of the system software dumping method stored in the memory and executable on the processor, wherein when the program of the system software dumping method is executed by the processor, it can implement the steps of the system software dumping method as described above.

[0053] This application also provides a readable storage medium, which is a computer-readable storage medium, and stores a program that implements a system software dumping method. When the program of the system software dumping method is executed by a processor, it implements the steps of the system software dumping method as described above.

[0054] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the system software dumping method described above.

[0055] This application provides a system software dumping method, apparatus, electronic device, and readable storage medium. Specifically, when a device fault is detected, a bootable dumping function is initiated via a dumping peripheral connected to the device. A target faulty program is identified, and the target faulty program is cloned using the bootable dumping function to obtain a faulty program image file. The target faulty program includes a complete file system program or a partial file system program. The target faulty program can be obtained from the complete program based on the specific scope of the fault, and an image file is generated based on the target faulty program. This accurately locates the faulty area, reduces the size of the image file generated during the dumping process, and improves the efficiency of system software dumping. The faulty program image file is sent to the dumping peripheral, enabling the bootable dumping function to be initiated via the dumping peripheral to automatically clone the target faulty program that has malfunctioned in the program. The generated image file is directly stored on the dumping peripheral, eliminating the need for professional personnel to use specialized tools for dumping, saving after-sales costs, and simplifying the software dumping operation. Attached Figure Description

[0056] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0057] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0058] Figure 1 This is a flowchart illustrating the first embodiment of the system software dumping method of this application;

[0059] Figure 2 This is a flowchart illustrating the second embodiment of the system software dumping method of this application;

[0060] Figure 3 This is a schematic diagram of the hardware operating environment involved in the system software dumping method in this application embodiment.

[0061] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0062] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0063] Example 1

[0064] This application provides a system software dumping method. In the first embodiment of the system software dumping method of this application, refer to... Figure 1 The system software dumping method includes:

[0065] Step S10: When a device malfunction is detected, the guided dump function is initiated according to the dump peripheral connected to the device.

[0066] Step S20: Determine the target fault program, clone the target fault program according to the boot dump function, and obtain the fault program image file of the target fault program, wherein the target fault program includes a complete file system program or a partial file system program.

[0067] Step S30: Send the fault program image file to the dump peripheral.

[0068] In this embodiment, it should be noted that previous data dumping solutions could only dump partial data. However, in the solution of this application embodiment, the complete system software and the environment required to run the system software can be directly dumped, rather than a portion of the software or data. The dumping peripheral can be any external device that can connect to the faulty device for file transfer, such as a USB flash drive, mobile phone, or PC (personal computer). Devices capable of data dumping, such as personal computers (PCs), iPads, etc., and devices that can perform data dumping via technologies such as WiFi and Bluetooth, are considered to have a successfully established connection when the dumping peripheral and the faulty device can successfully exchange data. The guided dumping function can automatically clone an image of the faulty program that has malfunctioned on the faulty device when a dump verification file is detected in the dumping peripheral. The target faulty program is the abnormal part of the program extracted from the partition where the fault occurred in the entire system software. The target faulty program can be the entire program content, which is a complete file system program, or a single part of the program content, which is a local file system program. It can also include the environment required for the program to run. The faulty program image file is a binary file generated after cloning the target faulty program. The cloned program can be restored to another device using the image file.

[0069] For example, steps S10 to S30 include:

[0070] The dump peripheral is connected to the faulty device. When a fault is detected in the faulty device, the boot dump function of the faulty device is started according to the dump verification file in the dump peripheral. The target faulty program that caused the fault is identified in the faulty device. The target faulty program is cloned according to the started boot dump function to generate a faulty program image file corresponding to the target faulty program. The obtained faulty program image file is sent to the dump peripheral through the connection relationship so that the software developer can restore the faulty program through the dump peripheral and handle the fault.

[0071] Specifically, the system software dumping method can be applied to resolve smart TV system faults. The fault program image file is stored in the dumping peripheral device. The fault program image file is stored as a binary file on the dumping peripheral device such as a USB flash drive. It can be a mirror of the entire system. The fault program image file is obtained through the USB flash drive or other connection. The fault image file in the dumping peripheral device is sent to the software developer. Similar to functions such as cloning a software system or migrating a system, it can completely restore the fault program and software environment of the current problem reported by the customer. It can be used to reproduce the problem, review all the software states and data of the fault program, and resolve the fault in a targeted manner.

[0072] In step S10, the step of activating the boot dump function based on the dump peripheral connected to the device includes:

[0073] Step A10: Detect whether a dump verification file exists in the dump peripheral;

[0074] Step A20: If a dump verification file is detected in the dump peripheral, the preset control system is triggered to start, and the boot dump function corresponding to the dump verification file is enabled through the started preset control system.

[0075] In this embodiment, it should be noted that the dump verification file is typically a dump file. When the faulty device detects the dump file, the dump file drives the boot dump function to start through the connection relationship and begins the fault program cloning process. When the faulty device does not detect the dump file, it will not continue the system software dump and will start the device normally. The preset control system is typically the device control system Boot that comes with the faulty device. Various commands can be run in this system, such as downloading files to memory, erasing, reading and writing Flash, running programs in memory, NOR Flash, and NAND Flash, viewing, modifying, and comparing data in memory, etc. The preset control system contains a command that can clone system software to generate an image file to complete the cloning in this embodiment.

[0076] For example, steps A10 to A30 include:

[0077] After the faulty device establishes a connection with the dump peripheral, the faulty device is restarted, and the presence of a dump verification file in the dump peripheral is checked. If the dump verification file is detected in the dump peripheral, the preset control system in the faulty device is triggered by the dump verification file. A dump fault program command for the target fault program is issued through the preset control system. The dump fault program command is run to start the boot dump function, and the next step is executed: the target fault program is determined, and the target fault program is cloned according to the boot dump function. If the dump file is not detected in the dump peripheral, the boot dump function will not be started even if there is a fault in the faulty device, and the system software dump will end directly.

[0078] This application provides a software dumping method. Specifically, when a device malfunction is detected, a bootable dumping function is initiated using a dumping peripheral connected to the device. A target faulty program is identified, and the bootable dumping function clones the target faulty program to obtain a faulty program image file. The target faulty program includes a complete file system program or a partial file system program. The target faulty program can be obtained from the complete program based on the specific scope of the fault. An image file is then generated based on the target faulty program, accurately locating the faulty area, reducing the size of the image file generated during the dumping process, and improving the efficiency of system software dumping. The faulty program image file is sent to the dumping peripheral. This method enables the bootable dumping function to be initiated through the dumping peripheral, automatically cloning the target faulty program that has malfunctioned in the program, and directly storing the generated image file on the dumping peripheral. This eliminates the need for professional personnel to use specialized tools for dumping, saving after-sales costs and simplifying the software dumping operation.

[0079] Example 2

[0080] Furthermore, referring to Figure 2 Based on the first embodiment of this application, in another embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description and will not be repeated hereafter. Based on this, in step S20, the step of determining the target fault procedure includes:

[0081] Step B10: Identify the faulty system software in the device and determine the complete file system program corresponding to the faulty system software;

[0082] Step B20: By detecting the fault range in the complete file system program, determine whether the complete file system program or the local file system program is the target fault program.

[0083] In this embodiment, it should be noted that if a program in a faulty device malfunctions, in addition to cloning the entire software program and its data into an image file, the specific location of the malfunction can be further precisely obtained. For example, if a malfunction occurs in a software program, and the specific location of the malfunction in the software program can be detected, this part can be extracted separately, and the extracted part can be cloned to generate an image file. When this image file is sent to the software developer for analysis, only the part of the software program that malfunctioned will be restored. The boot dump function can be executed through commands in Boot, first cloning the malfunctioning part and then converting it into an image file.

[0084] For example, steps B10 to B20 include:

[0085] Identify the faulty system software that has failed in the faulty device; determine the complete file system program based on the faulty system software; detect the specific fault range of the complete file system; and determine the target faulty program as either the complete file system program or a partial file system program based on the fault range.

[0086] In step B20, the step of detecting the scope of faults in the complete file system program includes:

[0087] Step B21: Divide the complete file system program into multiple program partitions based on the dump verification file;

[0088] Step B22: Locate the faulty program partition in each of the program partitions;

[0089] Step B23: The faulty program partition is defined as the fault range of the faulty system software.

[0090] In this embodiment, it should be noted that the program partition is a partition of the entire software program based on the different functions implemented. In addition to the partition based on the dump verification file, it can also be partitioned by the functions of the program itself, or by other methods such as program execution breakpoints. There may be more than one fault in the faulty program. All the faulty program partitions are detected and collected as the fault range of the system software.

[0091] For example, steps B21 to B23 include:

[0092] The complete file system program that failed in the faulty device is divided into multiple program partitions according to the preset program partitioning rules in the dump verification file. The contents of each program partition are checked in turn, and the faulty program partition that failed is located in each program partition. The set of all the faulty program partitions is taken as the fault range of the system software failure.

[0093] In step B22, the step of locating the faulty program partition in each of the program partitions includes:

[0094] Step B221: Send a probe request to the program node in each program partition, and receive the probe result fed back by each program node based on the probe request;

[0095] Step B222: If there is a program node whose detection result is abnormal, then the program partition corresponding to the program node whose detection result is abnormal is taken as the faulty program partition.

[0096] In this embodiment, it should be noted that the detection request is used to detect the location where the program malfunctions, and each node is detected sequentially according to the program's execution flow to obtain the detection results.

[0097] For example, steps B221 to B222 include:

[0098] The system sends a probe request to each program node of each program partition to locate the fault and receives the probe result fed back by each program node based on the probe request. When the probe result of the probe node is abnormal, the program partition corresponding to the program node with the abnormal probe result is regarded as the faulty program partition.

[0099] In step B20, the step of determining whether the complete file system program or the partial file system program is the target faulty program includes:

[0100] Step B24: If the faulty system software has been detected and the fault range has been determined, then the local file system within the fault range is designated as the target faulty program.

[0101] Step B25: If the faulty system software is detected and the fault range is not determined, then the complete file system program is taken as the target faulty program.

[0102] In this embodiment, it should be noted that the fault range can be a program of a single functional segment, or it can be all file systems, data, software and operating environment in the entire system. The image file generated based on the target faulty program needs to be able to completely restore the faulty segment or faulty software on another device. If the faulty segment or software requires special environment support, then the data of the special environment is also part of the fault range.

[0103] For example, steps B24 to B25 include:

[0104] If the faulty system software has been detected and the fault range has been determined, then the local file system within the fault range is designated as the target faulty program; if the detection results of each program node show no abnormalities and the faulty system software has not been detected and the fault range has not been determined, then the specific location of the fault in the faulty software program cannot be determined, nor can the program partition where the fault is located. In this case, the complete file system program needs to be designated as the target faulty program, and the complete file system program is directly cloned to obtain an image file.

[0105] In step B21, the step of dividing the complete file system program into multiple program partitions based on the dump verification file includes:

[0106] Step B211: Detect whether a preset program partitioning rule exists in the dump verification file;

[0107] Step B212: If the preset program partitioning rule exists, the program that has malfunctioned is divided into multiple program partitions according to the preset program partitioning rule.

[0108] Step B213: If the preset program partitioning rule does not exist, the program is divided into multiple program partitions according to the functional type of each part.

[0109] In this embodiment, it should be noted that the dump verification file can contain dump-related script logic, including the preset program partitioning rules, to inform the program which part of the data needs to be dumped. The preset program partitioning rules can be rules specified by the software developer to partition and dump faulty programs. When the dump verification file does not specify preset program partitioning, the program can be partitioned directly according to the program's function type or other classification methods.

[0110] For example, steps B211 to B213 include:

[0111] The system checks whether a preset program partitioning rule is written in advance in the dump verification file. If the preset program partitioning rule is detected, the program that has malfunctioned is directly partitioned according to the preset program partitioning rule. If the preset program partitioning rule is not detected, the program can be partitioned according to the functional type of each part of the program, making the program dumping more flexible.

[0112] This application provides a method for obtaining and cloning a target faulty program. Specifically, it involves identifying faulty system software within a device and determining the corresponding complete file system program; identifying the faulty file system program or a partial file system program as the target faulty program by detecting the fault range within the complete file system program; and converting the cloned target faulty program into a faulty program image file. This method achieves accurate identification of the target faulty program by obtaining it from the complete program based on the specific fault range, and then generating an image file from the target faulty program. This reduces the size of the image file generated during the dumping process and improves the efficiency of system software dumping.

[0113] Example 3

[0114] This application embodiment also provides a system software dumping device, which is applied to a system software dumping equipment, and the system software dumping device includes:

[0115] The connection module is used to initiate a guided dump function based on the dump peripheral connected to the device when a device malfunction is detected.

[0116] The cloning module is used to identify the target faulty program, clone the target faulty program according to the boot dump function, and obtain the faulty program image file of the target faulty program, wherein the target faulty program includes a complete file system program or a partial file system program.

[0117] The dump module is used to send the fault program image file to the dump peripheral.

[0118] Optionally, the connection module is further configured to:

[0119] Detect whether a dump verification file exists in the dump peripheral;

[0120] If a dump verification file is detected in the dump peripheral, the preset control system is triggered to start, and the boot dump function corresponding to the dump verification file is enabled through the started preset control system.

[0121] Optionally, the cloning module is further configured to:

[0122] Identify the faulty system software in the device and determine the complete file system program corresponding to the faulty system software;

[0123] By detecting the scope of faults in the complete file system program, the complete file system program or the local file system program is identified as the target fault program.

[0124] Optionally, the cloning module is further configured to:

[0125] The complete file system program is divided into multiple program partitions based on the dump verification file;

[0126] Locate the faulty program partition in each of the program partitions;

[0127] The faulty program partition is defined as the fault range of the faulty system software.

[0128] Optionally, the cloning module is further configured to:

[0129] Send a probe request to each program node in each program partition, and receive the probe result fed back by each program node based on the probe request;

[0130] If there is a program node whose detection result is abnormal, then the program partition corresponding to the program node whose detection result is abnormal is regarded as the faulty program partition.

[0131] Optionally, the cloning module is further configured to:

[0132] If the faulty system software is detected and the fault scope has been determined, then the local file system within the fault scope is designated as the target faulty program;

[0133] If the faulty system software is detected and the scope of the fault cannot be determined, the complete file system program will be used as the target faulty program.

[0134] Optionally, the cloning module is further configured to:

[0135] Detect whether a preset program partitioning rule exists in the dump verification file;

[0136] If the preset program partitioning rule exists, the program that has malfunctioned will be divided into multiple program partitions according to the preset program partitioning rule;

[0137] If the preset program partitioning rule does not exist, the program is divided into multiple program partitions based on the functional type of each part.

[0138] The system software dumping device provided by this invention, employing the system software dumping method in Embodiment 1 or Embodiment 2 described above, solves the technical problem of complex operation during the dumping process. Compared with the prior art, the beneficial effects of the system software dumping device provided by this invention are the same as those of the system software dumping method provided in the above embodiments, and other technical features in this system software dumping device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0139] Example 4

[0140] This invention provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the system software dumping method described in Embodiment 1 or Embodiment 2 above.

[0141] The following is for reference. Figure 3 The diagram illustrates a structural schematic of an electronic device suitable for implementing embodiments of the present disclosure. The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 3 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0142] like Figure 3 As shown, an electronic device may include a processing unit (such as a central processing unit, graphics processing unit, etc.) that can perform various appropriate actions and processes based on a program stored in read-only memory (ROM) or a program loaded from a storage device into random access memory (RAM). The RAM also stores various programs and data required for the operation of the electronic device. The processing unit, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.

[0143] Typically, the following systems can be connected to the I / O interface: input devices including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices including, for example, magnetic tapes, hard disks, etc.; and communication devices. Communication devices allow electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although electronic devices with various systems are shown in the figures, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.

[0144] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, it performs the functions defined above in the methods of embodiments of this disclosure.

[0145] The electronic device provided by this invention employs the system software dumping method described in Embodiment 1 or Embodiment 2 above, solving the technical problem of complex operation during the dumping process. Compared with the prior art, the beneficial effects of the electronic device provided by this invention are the same as those of the system software dumping method described in Embodiment 1 or Embodiment 2 above, and other technical features of this electronic device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0146] It should be understood that various parts of this disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.

[0147] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

[0148] Example 5

[0149] This embodiment provides a computer-readable storage medium having computer-readable program instructions stored thereon, which are used to execute the system software dumping method in Embodiment 1 or Embodiment 2 described above.

[0150] The computer-readable storage medium provided in this embodiment of the invention may be, for example, a USB flash drive, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0151] The aforementioned computer-readable storage medium may be included in an electronic device or may exist independently without being assembled into an electronic device.

[0152] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by an electronic device, the electronic device: when a device malfunction is detected, initiates a boot dump function according to a dump peripheral connected to the device; determines a target faulty program, clones the target faulty program according to the boot dump function, and obtains a faulty program image file of the target faulty program, wherein the target faulty program includes a complete file system program or a partial file system program; and sends the faulty program image file to the dump peripheral.

[0153] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0154] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0155] The modules described in the embodiments of this disclosure can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0156] The computer-readable storage medium provided by this invention stores computer-readable program instructions for executing the above-described system software dumping method, thus solving the technical problem of complex operation during the dumping process. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the embodiments of this invention are the same as the beneficial effects of the system software dumping method provided in Embodiment 1 or Embodiment 2, and will not be repeated here.

[0157] Example 6

[0158] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the system software dumping method described above.

[0159] The computer program product provided in this application solves the technical problem of complex operation in the dumping process. Compared with the prior art, the beneficial effects of the computer program product provided in the embodiments of this invention are the same as the beneficial effects of the system software dumping method provided in Embodiment 1 or Embodiment 2 above, and will not be repeated here.

[0160] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent scope of this application.

Claims

1. A system software dump method, characterized by, The system software dumping method comprises: when detecting that the device has a fault, starting a boot dumping function according to a dumping peripheral connected with the device; determining a target fault program, cloning the target fault program according to the boot dumping function, and obtaining a fault program mirror file of the target fault program, wherein the target fault program comprises a complete file system program or a partial file system program; sending the fault program mirror file to the dumping peripheral; the step of determining the target fault program comprises: determining a fault system software in the device and determining a complete file system program corresponding to the fault system software; determining the complete file system program or the partial file system program as the target fault program by detecting a fault range in the complete file system program; the step of detecting the fault range in the complete file system program comprises: dividing the complete file system program into a plurality of program partitions according to a dumping verification file; locating a fault program partition in each of the program partitions; taking the fault program partition as the fault range of the fault system software.

2. The system software dump method of claim 1, wherein, the step of starting the boot dumping function according to the dumping peripheral connected with the device comprises: detecting whether a dumping verification file exists in the dumping peripheral; if it is detected that the dumping verification file exists in the dumping peripheral, triggering a preset control system to start, and starting the boot dumping function corresponding to the dumping verification file through the started preset control system.

3. The system software dump method of claim 1, wherein, the step of locating the fault program partition in each of the program partitions comprises: sending a detection request to a program node in each of the program partitions, and receiving a detection result fed back by each of the program nodes based on the detection request; if there is a program node with an abnormal detection result, taking a program partition corresponding to the program node with the abnormal detection result as the fault program partition.

4. The system software dump method of claim 3, wherein, the step of determining the complete file system program or the partial file system program as the target fault program comprises: if it is detected that the fault range of the fault system software has been determined, taking a partial file system in the fault range as the target fault program; if it is detected that the fault range of the fault system software has not been determined, taking the complete file system program as the target fault program.

5. The system software dump method of claim 1, wherein, the step of dividing the complete file system program into the plurality of program partitions according to the dumping verification file comprises: detecting whether a preset program partition rule exists in the dumping verification file; if the preset program partition rule exists, dividing the fault program into the plurality of program partitions according to the preset program partition rule; if the preset program partition rule does not exist, dividing the fault program into the plurality of program partitions according to a function type of each part of the program.

6. A system software dump apparatus, characterized by comprising: the system software dumping device comprises: a connection module configured to start a boot dumping function according to a dumping peripheral connected with the device when detecting that the device has a fault; The cloning module is configured to determine a target fault program, clone the target fault program according to the guided dump function, and obtain a fault program image file of the target fault program, wherein the target fault program comprises a complete file system program or a partial file system program, the target fault program comprises a complete file system or a partial file system, the cloning module is further configured to determine a fault system software that is faulty in the device and determine a complete file system program corresponding to the fault system software, determine the complete file system program or the partial file system program as the target fault program by detecting a fault range in the complete file system program, and divide the complete file system program into a plurality of program partitions according to a dump verification file, locate a fault program partition that is faulty in each of the program partitions, and take the fault program partition as the fault range of the fault system software. The dump module is configured to send the fault program image file to the dump peripheral device.

7. An electronic device, comprising: The electronic device comprises: at least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the steps of the system software dump method in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a program for implementing a system software dump method, and the program for implementing the system software dump method is executed by a processor to implement the steps of the system software dump method in any one of claims 1 to 5.

Images