A software fault debugging method, device, smart container and storage medium

Abstract

The present application discloses a software fault debugging method, device, smart container and storage medium, the method comprising: when the boot program of the smart container determines that the application software on the first operating system of the smart container fails and the debugging function of the application software fails, the boot program of the smart container enters the debugging software on the second operating system of the smart container; the first operating system and the second operating system are in different disk partitions; the debugging software sends the fault information of the application software to a server, so that the server can debug the application software.

Description

Technical Field

[0001] The present application relates to the field of network technology, and relates to but is not limited to a software fault debugging method, device, smart container and storage medium. Background Art

[0002] In the related art, daily debugging of smart containers is achieved by connecting to the cloud through separately developed software to realize interconnected debugging. When this software fails, if other software fails, the only option is to go to the site or send the parts of the smart container back to the manufacturer for debugging and repair, which is time-consuming and labor-intensive. Summary of the invention

[0003] In view of this, embodiments of the present application provide a software fault debugging method, device, smart container and storage medium.

[0004] In a first aspect, an embodiment of the present application provides a software fault debugging method, the method comprising: when the boot program of the smart container determines that the application software on the first operating system of the smart container fails and the debugging function of the application software fails, the boot program of the smart container enters the debugging software on the second operating system of the smart container; the first operating system and the second operating system are in different disk partitions; the debugging software sends the fault information of the application software to a server, so that the server can debug the application software.

[0005] In a second aspect, an embodiment of the present application provides a software fault debugging device, the device comprising: a boot program, application software and debugging software, wherein: the boot program is used to enter the debugging software on the second operating system of the smart container when it is determined that the application software on the first operating system of the smart container fails and the debugging function of the application software fails; the first operating system and the second operating system are in different disk partitions; the debugging software is used to send the fault information of the application software to a server so that the server can debug the application software.

[0006] In a third aspect, an embodiment of the present application provides a smart container, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the steps in the software fault debugging method described in the embodiment of the present application are implemented.

[0007] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the software fault debugging method described in the embodiment of the present application are implemented.

[0008] In the embodiment of the present application, by providing a dual operating system for the smart container, when the application software and the debugging function of the application software of the first operating system fail at the same time, most software problems can be solved remotely through the debugging software of the second operating system, without the need to go to the site or send back the components of the smart container for debugging, thereby enabling the software failures of the smart container to be debugged more conveniently, efficiently, timely and intelligently. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A flowchart of a software fault debugging method according to an embodiment of the present application;

[0010] Figure 2 A flowchart of another software fault debugging method according to an embodiment of the present application;

[0011] Figure 3 A flowchart of another software fault debugging method according to an embodiment of the present application;

[0012] Figure 4 A flowchart of another software fault debugging method according to an embodiment of the present application;

[0013] Figure 5 A flowchart of a software fault debugging method according to an embodiment of the present application is provided;

[0014] Figure 6 A flowchart of a software fault debugging method according to an embodiment of the present application is provided;

[0015] Figure 7a A flowchart of a software fault debugging method according to an embodiment of the present application is provided;

[0016] Figure 7b A flowchart of a software fault debugging method according to an embodiment of the present application is provided;

[0017] Figure 7c A flowchart of a software fault debugging method according to an embodiment of the present application is provided;

[0018] Figure 8 A flowchart of a software fault debugging method according to an embodiment of the present application is provided;

[0019] Fig. 9 A flowchart of a software fault debugging method according to an embodiment of the present application is provided;

[0020] Fig.10 A schematic diagram of the structure of a software fault debugging device according to an embodiment of the present application;

[0021] Fig.11 A schematic diagram of a hardware entity of the smart container according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] The technical solution of the present application is further described in detail below with reference to the accompanying drawings and embodiments.

[0023] Figure 1 FIG. 1 is a flow chart of a software fault debugging method according to an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0024] Step 102: When determining that the application software on the first operating system of the smart container fails and the debugging function of the application software fails, the boot program of the smart container enters the debugging software on the second operating system of the smart container; the first operating system and the second operating system are in different disk partitions;

[0025] The smart cabinet, also known as the smart vending cabinet, is a machine that can automatically pay for goods according to the coins inserted; the smart cabinet is a common equipment for commercial automation, which is not restricted by time and place, can save manpower and facilitate transactions, and is a new form of commercial retail; the smart cabinet includes but is not limited to vending cabinets, retail cabinets, refrigerators, refrigerated cabinets, and normal temperature cabinets. The boot program of the smart cabinet is located on the smart cabinet, which refers to the program that boots the operating system of the smart cabinet.

[0026] The smart container can be installed with multiple application software to realize a variety of different functions. The application software on the smart container may include but is not limited to temperature control software, humidity control software, cabinet door switch state control software, image recognition software, payment software, positioning software, and sales software. The application software generally integrates some debugging functions, which can be realized by software developed separately on the smart container. Daily debugging can be connected to the cloud server through the separately developed software to realize interconnected debugging of the application software on the smart container.

[0027] Step 104: the debugging software sends the fault information of the application software to the server, so that the server can debug the application software;

[0028] Among them, two operating systems can be installed on the smart container: a first operating system and a second operating system. The first operating system can be called a main system, and the application software and the debugging function of the application software can be installed on the main system; the second operating system can be called a sub-system, and the debugging software can be installed on the sub-system. Like the debugging function, the debugging software can also be connected to a cloud server to realize interconnected debugging of the application software; the main system and the sub-system are in two independent disk partitions, and the integrity and security of the sub-system should be guaranteed to the maximum extent. The main system cannot delete or modify files on the sub-system; the fault information may include an exception title, an exception summary, and an exception log, etc.

[0029] In the embodiment of the present application, by providing a dual operating system for the smart container, when the application software and the debugging function of the application software of the first operating system fail at the same time, most software problems can be solved remotely through the debugging software of the second operating system, without the need to go to the site or send back the components of the smart container for debugging, thereby enabling the software failures of the smart container to be debugged more conveniently, efficiently, timely and intelligently.

[0030] In some embodiments, Figure 2 As shown, the method may further include the following steps 1011 to 1013:

[0031] Step 1011: The boot program of the smart container identifies whether a flag bit corresponding to at least one process is abnormal; the process includes an operation process and / or a debugging process of the application software;

[0032] Step 1012: the boot program determines that the application software fails when the flag bit corresponding to the running process of the application software is abnormal;

[0033] Step 1013: When the flag bit corresponding to the debugging process of the application software is abnormal, the boot program determines that the debugging function of the application software fails.

[0034] Among them, the flag bit can be used to indicate whether any running process or debugging process of the application software has a fault. When the flag bit corresponding to the running process of the application software is normal, it can be determined that the application software has no fault. When the flag bit corresponding to the running process of the application software is abnormal, it can be determined that the application software has a fault.

[0035] Among them, similar to the flag bit corresponding to the running process of the application software, the flag bit corresponding to the debugging process of the application software can be used to indicate whether the debugging function of the application software fails. When the flag bit corresponding to the debugging process of the application software is normal, it can be determined that the debugging function of the application software has not failed. When the flag bit corresponding to the debugging process of the application software is abnormal, it can be determined that the debugging function of the application software has failed.

[0036] In an embodiment of the present application, a boot program is used to identify a flag bit of an application software's running process or debugging process, and based on whether the flag bit of the running process or debugging process is abnormal, it is determined whether the application software or the debugging function of the application software has a fault, thereby enabling software faults to be determined more accurately, conveniently, and efficiently.

[0037] In some embodiments, Figure 3 As shown, before step 1011, the method further includes the following steps 1001 to 1003:

[0038] Step 1001: The boot program of the smart container enters the first operating system;

[0039] After the smart container is powered on, since the abnormal flag is not marked at the beginning, the first operating system of the smart container can be started through the boot program.

[0040] Step 1002: When the first operating system determines that an unexpected exception occurs in the running process of the application software and / or the debugging process of the application software, the first operating system marks a flag bit corresponding to the running process and / or the debugging process as abnormal;

[0041] Step 1003: The boot program restarts the smart container to identify the flag corresponding to the running process of the application software and / or the debugging process of the application software.

[0042] The first operating system may detect whether an unexpected exception occurs in a process of the application software on the first operating system, and mark a flag bit corresponding to the process where the unexpected exception occurs as an exception.

[0043] In an embodiment of the present application, when an unexpected exception occurs in the running process or debugging process of the application software, the flag bit corresponding to the running process or debugging process of the application software is marked as abnormal, so that it is more convenient to determine whether an abnormality occurs in the application software and the debugging function of the application software based on the flag bit of the process.

[0044] In some embodiments, Figure 4 As shown, the method further includes the following steps 106 to 108:

[0045] Step 106: the debugging software obtains the debugging instruction of the server; wherein the debugging instruction is generated by the server based on the fault information of the application software, or the debugging instruction is generated by the server based on the debugging operation of the operation and maintenance personnel; the debugging operation is generated by the operation and maintenance personnel based on the fault information of the application software;

[0046] Step 108: The debugging software debugs the application software based on the debugging instruction.

[0047] Among them, after the server obtains the software fault information, it can not only intelligently determine the cause of the fault based on the fault information and generate debugging instructions; technical personnel (i.e., operation and maintenance personnel) can also intervene in debugging. If there is a problem, the exception log in the fault information can be analyzed, and the corresponding exception solution (i.e., debugging operation, for example, if a certain software lacks an installation process, the installation process of the software is added) or the debugging instructions are generated by flashing the machine to solve the exception problem.

[0048] In some embodiments, the boot program may also power off and restart the smart container after debugging is completed, or restart the smart container according to a restart instruction from a server.

[0049] In the embodiment of the present application, by debugging the software through the server, software problems can be solved remotely, thereby enabling software failures to be debugged more simply, efficiently and timely.

[0050] In some embodiments, Figure 5 As shown, the method also includes:

[0051] Step 110: When the server successfully debugs the application software, the first operating system modifies the flag corresponding to the running process of the application software to normal, and retains the fault information of the application software.

[0052] In an embodiment of the present application, when the software is successfully debugged, the fault information of the application software is retained, so that when a software abnormality occurs subsequently, the technical staff can refer to the historical fault information to more efficiently determine the fault content and cause of the software, thereby debugging the software more timely.

[0053] In some embodiments, Figure 6 As shown, the method also includes:

[0054] Step 112: When it is determined that the application software has an expected abnormality, the boot program enters the first operating system; or, the debugging software is closed.

[0055] Among them, the expected exception is generally an exception caused by manual debugging by a technician. At this time, the first operating system can be entered regardless of the exception, or the function of entering the debugging software can be turned off by adjusting the boot program to avoid automatically entering the debugging software due to the boot program recognizing the exception.

[0056] In the embodiment of the present application, it is possible to avoid the expected daily operation caused by manual debugging by technicians, which may lead to entering the second operating system.

[0057] In some embodiments, the “closing the debugging software” in step 112 may be implemented by one of the following steps:

[0058] like Figure 7a As shown, step 1121a: the boot program turns off the abnormal flag identification function; the abnormal flag identification function is used to identify whether the flag corresponding to at least one process is abnormal.

[0059] The first operating system can be entered by turning off the function of judging whether the flag bit of the boot program is abnormal.

[0060] like Figure 7b As shown, step 1121b: the boot program enters the first operating system, and closes the debugging software in the first operating system.

[0061] like Figure 7c As shown, step 1121c: the boot program enters the second operating system, and closes the debugging software in the second operating system.

[0062] In the embodiment of the present application, the debugging software may be turned off by adjusting the boot program, or the debugging software may be turned off in the first operating system or the second operating system.

[0063] In some embodiments, Figure 8 As shown, the method further includes the following steps 1051 and 1052:

[0064] Step 1051: the debugging software sends the fault information of the debugging function of the application software to the server, so that the server can debug the debugging function of the application software;

[0065] Step 1052: When the debugging function of the server successfully debugs the application software and the boot program determines that the application software fails again, the debugging function of the application software sends the failure information of the application software to the server for the server to debug the application software.

[0066] In an embodiment of the present application, the debugging software can also send the fault information of the debugging function to the server, and the server can perform Internet debugging on the debugging function; if the subsequent application software fails, the application software can be debugged online through the debugging function of the application software, which is simple, efficient, timely, convenient and more intelligent.

[0067] In the related art, the software fault debugging solutions for smart containers are all single systems. The daily debugging of smart containers is connected to the cloud through separately developed software to achieve interconnected debugging. When this software has an abnormality, other software (such as application software) problems can only be repaired on-site or by sending the parts (components of the smart container) back to the manufacturer for debugging and repair. Regardless of going on-site or mailing, the time spent on the journey will result in the failure to solve the software fault problem in a timely manner.

[0068] The embodiments of the present application can improve the efficiency of resolving events in which problems occur in the debugging software while other software also has problems.

[0069] The embodiment of the present application adds a sub-system (ie, a second operating system), and the sub-system may be an extremely streamlined system that only retains the network debugging function.

[0070] The present application embodiment provides a method for debugging software failures, which is applied to a dual-system smart container, such as Fig. 9 As shown, the method comprises the following steps:

[0071] Step 901: The smart container is turned on and starts the boot process;

[0072] Step 902: boot the program to enter the main system;

[0073] Step 903: the main system adds several flags during the process from booting to normal use;

[0074] A flag bit may be added to each process (such as a running process or a debugging process of the application software) of each software (such as an application software) on the main system.

[0075] Step 904: The main system determines whether an unexpected exception occurs in the software;

[0076] Step 905: the main system sends the abnormal flag bit and the abnormal information and abnormal log of the corresponding software to the boot program;

[0077] When an unexpected exception occurs in the software, the main system marks the flag of the corresponding software as abnormal, and records the abnormal information and abnormal log. The abnormal flag and the abnormal information and abnormal log of the corresponding software are sent to the boot program; the boot program guides the smart container to restart and enter the recovery process.

[0078] Step 906: The boot program recognizes the abnormal flag of the software and enters the secondary system;

[0079] Among them, the secondary system is in an independent partition of the disk, and the main system cannot delete or modify the files in the secondary system. If it is necessary to delete, modify, etc. the files in the secondary system, a password or other means must be provided; the secondary system can store a reduced read-only memory (ROM) or other programs, so that it can enter the secondary system mode in case of abnormality, establish a connection with the server, and provide a remote debugging path.

[0080] Step 907: The secondary system sends the software exception information and exception log to the server, requesting technical personnel to debug and troubleshoot;

[0081] After the secondary system is started, it will report the software's abnormal information and abnormal logs to the server, requesting technical personnel to debug and troubleshoot; technical personnel can intervene in the debugging, and if there is a problem, they can analyze the abnormal log and solve the abnormal problem through corresponding abnormal solution methods or flashing the machine.

[0082] Step 908: After the software debugging is successful, the boot program restarts the smart container;

[0083] Among them, the boot program can restart to the smart container after power off, and can also receive the restart command from the server to restart the smart container; the boot program can record the abnormal information and abnormal log of the software, clear the abnormal flag, so that the smart container can start normally and enter the boot program. If the boot program recognizes that the software still has unexpected abnormalities, it will continue to mark the flag bit of the corresponding process of the software as abnormal and restart to the secondary system. If the boot program recognizes that the software has an expected abnormality through the restart command, it can directly restart to the main system, or close the secondary system by adjusting the boot program (turning off the judgment function of whether the boot program's identification flag bit is abnormal). The secondary system can be closed in both the main system and the secondary system.

[0084] In one embodiment, if the main system has been started for ten minutes but no preset software is detected to be started, an exception will be triggered to enter the secondary system, and then the secondary system will report the exception. At this time, the technician will intervene and repair the problem if there is one. If it is an expected exception caused by manual debugging by the technician, the technician can ignore the exception and directly restart to the main system, or directly turn off the function of entering the secondary system by adjusting the boot program.

[0085] In the embodiment of the present application, by providing a dual system for the smart container, most software problems for non-mobile equipment can be solved remotely without going to the site or sending back parts for debugging. This is simple, efficient, timely, convenient, and more intelligent.

[0086] It should be noted that in the embodiments of the present application, if the above-mentioned software fault debugging method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly reflected in the form of a software product, which is stored in a storage medium and includes several instructions for enabling the smart container to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0087] Based on the embodiments of the aforementioned methods, the embodiments of the present application provide a smart container, which includes the components included, and can be implemented by a processor in the smart container; of course, it can also be implemented by a specific logic circuit; in the implementation process, the processor can be a central processing unit (CPU, Central Processing Unit), a microprocessor (MPU, Microprocessor Unit), a digital signal processor (DSP, Digital Signal Processing) or a field programmable gate array (FPGA, Field Programmable Gate Array), etc.

[0088] Fig.10 FIG. 1 is a schematic diagram of the structure of a software fault debugging device according to an embodiment of the present application. Fig.10 As shown, the device 1000 includes a boot program 1001, application software 1002 and debugging software 1003, wherein:

[0089] The boot program 1001 is used to enter the debugging software 1003 on the second operating system of the smart container when it is determined that the application software 1002 on the first operating system of the smart container fails and the debugging function of the application software 1002 fails; the first operating system and the second operating system are in different disk partitions;

[0090] The debugging software 1003 is used to send the fault information of the application software 1002 to the server, so that the server can debug the application software 1002 .

[0091] In some embodiments, the boot program 1001 is used to identify whether a flag bit corresponding to at least one process is abnormal; the process includes the running process and / or debugging process of the application software; when the flag bit corresponding to the running process of the application software 1002 is abnormal, it is determined that the application software 1002 has a fault; when the flag bit corresponding to the debugging process of the application software 1002 is abnormal, it is determined that the debugging function of the application software 1002 has a fault.

[0092] In some embodiments, the boot program 1001 is also used to enter the first operating system; the first operating system is used to mark the flag bit corresponding to the running process and / or the debugging process of the application software 1002 as abnormal when it is determined that an unexpected exception occurs in the running process of the application software 1002 and / or the debugging process of the application software 1002; the boot program 1001 is used to restart the smart container to identify the flag bit corresponding to the running process of the application software 1002 and / or the debugging process of the application software 1002.

[0093] In some embodiments, the debugging software 1003 is used to obtain debugging instructions from the server; wherein, the debugging instructions are generated by the server based on the fault information of the application software 1002, or, the debugging instructions are generated by the server based on the debugging operations of the operation and maintenance personnel; the debugging operations are generated by the operation and maintenance personnel based on the fault information of the application software 1002; the debugging software 1003 is also used to debug the application software 1002 based on the debugging instructions.

[0094] In some embodiments, when the server successfully debugs the application software 1002, the first operating system is used to modify the flag corresponding to the running process of the application software 1002 to normal, and retain the fault information of the application software 1002.

[0095] In some embodiments, the boot program 1001 is used to enter the first operating system when it is determined that the application software 1002 has an expected exception; or to close the debugging software 1003.

[0096] In some embodiments, the boot program 1001 is used to disable an abnormal flag identification function; the abnormal flag identification function is used to identify whether a flag corresponding to at least one process is abnormal.

[0097] In some embodiments, the boot program 1001 is used to enter the first operating system and close the debugging software 1003 in the first operating system.

[0098] In some embodiments, the boot program 1001 is used to enter the second operating system and close the debugging software 1003 in the second operating system.

[0099] In some embodiments, the debugging software is used to send fault information of the debugging function of the application software 1002 to the server, so that the server can debug the debugging function of the application software 1002; when the server successfully debugs the debugging function of the application software 1002 and the boot program determines that the application software 1002 fails again, the debugging function of the application software 1002 sends the fault information of the application software 1002 to the server, so that the server can debug the application software 1002.

[0100] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.

[0101] Correspondingly, the embodiment of the present application provides a smart container, Fig.11 A schematic diagram of a hardware entity of the smart container in the embodiment of the present application is shown as follows: Fig.11 As shown, the hardware entity of the smart container 1100 includes: a memory 1101 and a processor 1102, wherein the memory 1101 stores a computer program that can be run on the processor 1102, and the processor 1102 implements the steps of the software fault debugging method in the above embodiment when executing the program.

[0102] The memory 1101 is configured to store instructions and applications executable by the processor 1102, and can also cache data to be processed or processed by the processor 1102 and each module in the smart container 11100 (for example, image data, audio data, voice communication data, and video communication data), which can be implemented through flash memory (FLASH) or random access memory (Random Access Memory, RAM).

[0103] Correspondingly, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the software fault debugging method in the above embodiment are implemented.

[0104] It should be noted here that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects as the device embodiments. For technical details not disclosed in the storage medium and method embodiments of this application, please refer to the description of the device embodiments of this application for understanding.

[0105] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned sequence numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0106] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0107] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0108] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, the functional units in the embodiments of the present application may be all integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0109] It can be understood by those skilled in the art that all or part of the steps of the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiment are executed; and the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, read-only memory (ROM), magnetic disks or optical disks. Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application can be essentially or partly reflected in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a mobile phone, a tablet computer, a desktop computer, a personal digital assistant, a navigator, a digital phone, a video phone, a television, a sensor device, etc.) to execute all or part of the methods described in each embodiment of the present application. And the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, magnetic disks or optical disks.

[0110] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain a new method embodiment. The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain a new product embodiment. The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain a new method embodiment or device embodiment.

[0111] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A software fault debugging method, characterized in that: The method comprises: The boot program of the smart container enters the debugging software on the second operating system of the smart container when determining that the application software on the first operating system of the smart container fails and the debugging function of the application software fails; the first operating system and the second operating system are in different disk partitions; The first operating system sends the fault information of the application software to the boot program; The debugging software obtains the fault information of the application software from the boot program; The debugging software sends the fault information of the application software to the server; The debugging software obtains the debugging instruction of the server; wherein the debugging instruction is generated by the server based on the fault information of the application software, or the debugging instruction is generated by the server based on the debugging operation of the operation and maintenance personnel; the debugging operation is generated by the operation and maintenance personnel based on the fault information of the application software; The debugging software debugs the application software based on the debugging instruction.

2. The method according to claim 1, characterized in that: The method further comprises: The boot program identifies whether a flag bit corresponding to at least one process is abnormal; the process includes an operation process and / or a debugging process of the application software; The boot program determines that the application software fails when the flag bit corresponding to the running process of the application software is abnormal; The boot program determines that a debugging function of the application software fails when the flag bit corresponding to the debugging process of the application software is abnormal.

3. The method according to claim 2, characterized in that The method further comprises: The boot program enters the first operating system; When determining that an unexpected exception occurs in the running process of the application software and / or the debugging process of the application software, the first operating system marks a flag bit corresponding to the running process and / or the debugging process as abnormal; The boot program restarts the smart container to identify the flag bit corresponding to the running process of the application software and / or the debugging process of the application software.

4. The method according to claim 1, characterized in that The method further comprises: When the server successfully debugs the application software, the first operating system modifies the flag bit corresponding to the running process of the application software to normal, and retains the fault information of the application software.

5. The method according to claim 1, characterized in that The method further comprises: When determining that the application software has an expected abnormality, the boot program enters the first operating system; or closes the debugging software.

6. The method according to claim 5, characterized in that The shutting down of the debugging software includes any of the following methods: The boot program turns off the abnormal flag bit identification function; the abnormal flag bit identification function is used to identify whether the flag bit corresponding to at least one process is abnormal; The boot program enters the first operating system, and closes the debugging software in the first operating system; Therefore, the boot program enters the second operating system, and the debugging software is closed in the second operating system.

7. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The debugging software sends the fault information of the debugging function of the application software to the server, so that the server can debug the debugging function of the application software; When the debugging function of the server successfully debugs the application software and the boot program determines that the application software fails again, the debugging function of the application software sends the failure information of the application software to the server for the server to debug the application software.

8. A software fault debugging device, characterized in that: The device comprises: a boot program, application software and debugging software, wherein: The boot program is used to enter the debugging software on the second operating system of the smart container when it is determined that the application software on the first operating system of the smart container fails and the debugging function of the application software fails; the first operating system and the second operating system are in different disk partitions; The debugging software is used to send the fault information of the application software to the server; the fault information of the application software is obtained by the debugging software from the boot program; the fault information of the application software in the boot program is sent by the first operating system; The debugging software is further used to obtain a debugging instruction of the server; wherein the debugging instruction is generated by the server based on the fault information of the application software, or the debugging instruction is generated by the server based on the debugging operation of the operation and maintenance personnel; the debugging operation is generated by the operation and maintenance personnel based on the fault information of the application software; The debugging software is further used to debug the application software based on the debugging instruction.

9. A smart container, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, characterized in that: When the processor executes the program, the steps of the software fault debugging method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the software fault debugging method described in any one of claims 1 to 7 are implemented.

Images