Method and apparatus for displaying debugging information, non-volatile storage medium, and processor

Abstract

The present application discloses a method and apparatus for displaying debugging information, a non-volatile storage medium, and a processor. Among them, the method includes: receiving first debugging information, deleting a first protocol header in the first debugging information to obtain second debugging information, where the first debugging information is sent through an interactive page; re-parsing the second debugging information to obtain third debugging information, where the third debugging information is information about values to be read or written by a target algorithm; adding a second protocol header to the third debugging information, and sending the third debugging information after adding the second protocol header to the interactive page to display the third debugging information after adding the second protocol header through the interactive page. The present application solves the technical problems of low fitting degree between the debugging page and the algorithm and low algorithm debugging efficiency caused by the fact that in the prior art, the controller can only provide basic data such as real-time parameter values during algorithm debugging.

Description

Technical Field

[0001] The present application relates to the field of intelligent control, and more specifically, to a method and device for displaying debugging information, a non-volatile storage medium, and a processor in the field of intelligent control of industrial automation. Background Art

[0002] At present, intelligent controllers are widely used in industrial sites to run advanced control algorithms developed for specific processes. In order to achieve the best on-site control effect, the algorithm running on the intelligent controller must be fully debugged before using it, and various control parameters need to be adjusted according to the running status of the algorithm; because different algorithms have different input parameters, output parameters and internal logic, the parameters, trends and other information that need to be paid attention to during debugging are also different; and with the increase in algorithm complexity, the number of contents that need to be paid attention to when debugging the algorithm will also increase greatly; and the controllers that are widely used at present have a single means of debugging algorithms, and the information that can be provided is extremely limited. They can only provide some basic data such as real-time values ​​of parameters. Only real-time values ​​can be seen during debugging, and there is no graphical display. Therefore, the debugging page has a low fit with the algorithm and the debugging efficiency is low.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a method and device for displaying debugging information, a non-volatile storage medium, and a processor, so as to at least solve the technical problems of low fit between the debugging page and the algorithm and low algorithm debugging efficiency caused by the fact that in the prior art, the controller can only provide basic data such as real-time values ​​of parameters when debugging the algorithm.

[0005] According to one aspect of an embodiment of the present application, a method for displaying debugging information is provided, including: receiving first debugging information, deleting a first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is sent through an interactive page; parsing the second debugging information again to obtain third debugging information, wherein the third debugging information is information about a value to be read or a value to be written for a target algorithm; adding a second protocol header to the third debugging information, and sending the third debugging information after the second protocol header is added to the interactive page, so as to display the third debugging information after the second protocol header is added through the interactive page.

[0006] Optionally, first debugging information is received, and a first protocol header in the first debugging information is deleted to obtain second debugging information, including: starting a first preset process, parsing the first protocol header, and determining whether the first debugging information is target information based on a result of parsing the first protocol header, wherein the first preset process is a process that interacts with an interactive page; if the first debugging information is target information, the first protocol header is deleted to obtain second debugging information; if the first debugging information is not target information, the first protocol header is refused to be deleted.

[0007] Optionally, before re-parsing the second debugging information, it includes: starting a second preset process, wherein the second preset process is a process for loading configuration software, and the configuration software is used to control the interactive page to display the third debugging information after adding the second protocol header; sending the first information to the second preset process through the first preset process at a preset time, if the second information sent by the second preset process is received, determining that the second preset process has not failed, wherein the first information and the second information are a set of corresponding information; if the second information is not received, determining that the second preset process has failed, and checking the second preset process.

[0008] Optionally, before displaying the third debugging information after the second protocol header is added through the interactive page, it includes: debugging the interactive page and the second preset process, if the debugging result indicates that the interactive page and the second preset process are not faulty, determining to send fifth information to the target terminal, wherein the fifth information is information indicating that the interactive page is loaded successfully; if the debugging result indicates that the interactive page or the second preset process is faulty, sending sixth information to the target terminal, wherein the sixth information is information prompting the target terminal to make modifications.

[0009] Optionally, the third debugging information after the second protocol header has been added is displayed through an interactive page, including: if the third debugging information corresponds to multiple display results, sending third information to the target terminal, wherein the third information is information requesting the target terminal to select multiple graphical display results; receiving fourth information detected by the interactive page, and displaying the third debugging information after the second protocol header has been added according to the fourth information, wherein the fourth information is information corresponding to the third information.

[0010] Optionally, the third debugging information after the second protocol header is added is displayed through an interactive page, wherein the result displayed on the interactive page is pre-stored in the interactive page.

[0011] According to another aspect of an embodiment of the present application, a method for displaying debugging information is also provided, including: receiving a debugging file, extracting protocol content, wherein the protocol content is stored in the debugging file; matching a third protocol header for the protocol content, generating fourth debugging information based on the protocol content and the third protocol header, and sending it to a backend; receiving fifth debugging information, parsing the fourth protocol header of the fifth debugging information, and obtaining a parsing result, wherein the fifth debugging information is a result of the backend processing the fourth debugging information; and displaying the fifth debugging information through an interactive page according to the parsing result.

[0012] According to another aspect of the embodiment of the present application, a display device for debugging information is also provided, including: a receiving module, used to receive first debugging information, delete the first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is received through an interactive page; a parsing module, used to parse the second debugging information again to obtain third debugging information, wherein the third debugging information is information about a value to be read or a value to be written for a target algorithm; and a display module, used to add the second protocol header to the third debugging information, and send the third debugging information after the second protocol header is added to the interactive page, so as to display the third debugging information after the second protocol header is added through the interactive page.

[0013] According to another aspect of the embodiments of the present application, a non-volatile storage medium is provided, which includes a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the above-mentioned method for displaying debugging information.

[0014] According to another aspect of the embodiments of the present application, a processor is provided, which is used to run a program stored in a memory, wherein the above-mentioned method for displaying debugging information is executed when the program is running.

[0015] In an embodiment of the present application, a method for displaying debugging information is provided by receiving first debugging information, deleting a first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is sent through an interactive page; parsing the second debugging information again to obtain third debugging information, wherein the third debugging information is information about a value to be read or written by a target algorithm; adding a second protocol header to the third debugging information, and sending the third debugging information after adding the second protocol header to the interactive page, so as to display the third debugging information after adding the second protocol header through the interactive page, and performing multiple parsing on the received debugging information, matching the protocol header for the parsed debugging information, and sending the parsed debugging information with the matched protocol header to the interactive page; the purpose of displaying the parsed debugging information with the matched protocol header by the interactive page is achieved, thereby achieving the technical effect of improving the fit between the debugging page and the algorithm, and further solving the technical problems of low fit between the debugging page and the algorithm and low algorithm debugging efficiency caused by the controller only being able to provide basic data such as real-time values ​​of parameters when debugging the algorithm in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0017] Figure 1 is a flowchart of a method for displaying debugging information according to an embodiment of the present application;

[0018] Figure 2 is a structural diagram of a display device for debugging information according to an embodiment of the present application;

[0019] Figure 3 It is a schematic diagram of the interaction of various processes when debugging an algorithm using a plug-in function block debugging panel based on Hyper Text Markup Language (HTML) according to an embodiment of the present application. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0021] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0022] According to an embodiment of the present application, a method embodiment for displaying debugging information is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0023] According to an embodiment of the present application, a debugging panel is provided, which includes a software development kit (SDK); wherein the SDK includes auxiliary files for developing Hypertext Markup Language (HTML), header files of computer design language (C++), and dynamic libraries (.dll) storing codes and data that can be used by multiple programs simultaneously. The pages and .dll files developed by SDK are imported into the configuration software and the corresponding algorithms are associated; wherein the HTML page can display the reading algorithm parameter list and reading and writing algorithm parameter values ​​provided by SDK, as well as the customized real-time curves, pie charts, etc. drawn based on the above parameter list and parameter values.

[0024] For ease of understanding, the following explanation is given:

[0025] iframe: A Hypertext Markup Language (HTML) tag that specifies an inline frame that provides the operating conditions for running the above-mentioned hypertext markup language and is used to embed another document in the current HTML document.

[0026] A network socket represents one end of process communication on the network. It provides a mechanism for application layer processes to exchange data using network protocols. It is an interface for applications to interact with the network protocol stack.

[0027] Network protocol: A collection of rules, standards or conventions established for data exchange in a computer network.

[0028] Protocol header: specifies the transmission protocol to be used, which is used to tell the browser how to handle the file to be opened.

[0029] Figure 1 is a flowchart of a method for displaying debugging information provided in an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0030] Step S102: receiving first debugging information, deleting a first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is sent through an interactive page.

[0031] In step S102, the background framework process receives a message (i.e., the first debugging information) sent by the front-end page (i.e., the interactive page) after the user selects the debugging mode on the front-end page, and deletes the protocol header (i.e., the first protocol header) of the message to obtain a network protocol (i.e., the second debugging information) corresponding to the selected debugging mode and used to implement the debugging function.

[0032] Step S104, parsing the second debugging information again to obtain third debugging information, wherein the third debugging information is information about a value to be read or written to the target algorithm;

[0033] In step S104, the network protocol (i.e., the second debugging information) is parsed using a protocol header corresponding to the network protocol for implementing the debugging function (i.e., the second debugging information) to obtain the protocol content of the network protocol for implementing the debugging function (i.e., the second debugging information), and the protocol content is processed to obtain a processing result (i.e., the third debugging information); specifically, the protocol content will include an algorithm for implementing the debugging function (i.e., the target algorithm) in the selected debugging mode, and the processing result is information related to the debugging parameters, such as the value of the debugging parameters to be read or written when the algorithm for implementing the debugging function (i.e., the target algorithm) is executed.

[0034] Step S106, adding the second protocol header to the third debugging information, and sending the third debugging information after adding the second protocol header to the interactive page, so that the third debugging information after adding the second protocol header is displayed through the interactive page.

[0035] In step S106, the third debugging information is received, and after matching the (second) protocol header, it is sent to the front-end page (ie, the interactive page). The front-end page parses the (second) protocol header and displays the debugging page corresponding to the third debugging information.

[0036] Through the above steps, the debugging results can be displayed according to the debugging information, including but not limited to displaying the real-time values ​​of the debugging parameters corresponding to the debugging information on the front-end page, and dynamically or statically displaying the debugging results corresponding to the debugging information on the front-end page.

[0037] According to another optional embodiment of the present application, first debugging information is received, and the first protocol header in the first debugging information is deleted to obtain second debugging information, including the following steps: starting a first preset process, parsing the first protocol header, and determining whether the first debugging information is target information based on the result of parsing the first protocol header, wherein the first preset process is a process that interacts with an interactive page; if the first debugging information is target information, deleting the first protocol header to obtain second debugging information; if the first debugging information is not target information, refusing to delete the first protocol header.

[0038] The present embodiment provides an optimal method for displaying debugging information, which starts a first preset process for the backend to interact with the front-end interactive page, and the background framework process in the backend receives the message (i.e., the first debugging information) sent by the front-end page (i.e., the interactive page), and parses the (first) protocol header; if, according to the result of parsing the (first) protocol header, it is displayed that the message sent by the front-end page is a debugging message, the (first) protocol header is deleted, and the information in the first debugging information except the first protocol header is retained, and the information in the first debugging information except the first protocol header is the second debugging information; if, according to the result of parsing the (first) protocol header, it is displayed that the message sent by the front-end page is not a debugging message, no operation is performed on the first debugging information.

[0039] According to another optional embodiment of the present application, before re-parsing the second debugging information, it includes: starting a second preset process, wherein the second preset process is a process for loading configuration software, and the configuration software is used to control the interactive page to display the third debugging information after adding the second protocol header; sending the first information to the second preset process through the first preset process at a preset time, and if the second information sent by the second preset process is received, determining that the second preset process has not failed, wherein the first information and the second information are a set of corresponding information; if the second information is not received, determining that the second preset process has failed, and checking the second preset process.

[0040] In this embodiment, the debugging information is parsed multiple times by the backend, wherein the backend is divided into two modules: a background framework process and a dynamic library. The background framework process interacts with the front-end web page to parse and transmit the debugging information; and the dynamic library interacts with the background framework process to parse and transmit the debugging information; in addition, the dynamic library is also used for loading the controller configuration software. The above-mentioned backend and front-end web pages together constitute a configuration software. Before starting the configuration software, the dynamic library of the configuration software needs to be loaded in advance. In order to reduce the risk of loading the dynamic library, the controller configuration software will start a new sub-process (i.e., the second preset process), and the dynamic library will be loaded by this new sub-process, thereby realizing process isolation, and achieving the effect that even if there is a problem in the dynamic library, it will only stop the sub-process from running, and will not cause the configuration software to crash.

[0041] The above-mentioned subprocess (i.e., the second preset process) and the entire process of interaction between the backend and the front-end page (i.e., the first preset process), these two processes communicate through a network socket, and use a question-and-answer method to exchange debugging information; from the start, the first preset process will send a heartbeat packet (i.e., the first information) to the subprocess every second, and if the subprocess is running normally, it will immediately reply with the corresponding information (i.e., the second information); if the subprocess does not send a reply message, it means that there is a problem with the subprocess and it needs to be checked. Among them, the heartbeat packet mentioned above is a custom command word that regularly notifies the sender of the heartbeat packet status during the client and service. It is sent at a certain time interval. After receiving the heartbeat packet, the receiver will reply with a fixed message. If the receiver does not reply within a specified time, it is considered that there is a problem with the receiver and the receiver needs to be checked.

[0042] According to another optional embodiment of the present application, before the third debugging information after the second protocol header is added is displayed through the interactive page, the following operations are included: debugging the interactive page and the second preset process, if the debugging result indicates that the interactive page and the second preset process are not faulty, determining to send fifth information to the target terminal, wherein the fifth information is information indicating that the interactive page has been loaded successfully; if the debugging result indicates that the interactive page or the second preset process is faulty, sending sixth information to the target terminal, wherein the sixth information is information prompting the target terminal to make modifications.

[0043] According to the method provided in this embodiment, before displaying the third debugging information after adding the second protocol header through the interactive page, it is necessary to load the custom debugging panel file and verify it at the same time to prevent the loaded file from failing to work properly. Method for debugging interactive pages: For the front-end page (i.e., the interactive page), it is necessary to run the HTML page to see if it is loaded normally; since the dynamic library calls all interfaces through the above-mentioned sub-process (i.e., the second preset process) to implement the functions of the dynamic library, the debugging of the dynamic library only needs to debug the second preset process. Method for debugging dynamic libraries: For dynamic libraries, a new sub-process needs to be started to call all interfaces to check whether all interfaces are implemented and whether they will crash. For the above-mentioned checks, if all pass, the user is prompted that the loading is successful (i.e., the fifth information is sent to the target terminal); if there is a failed check, a prompt of the failed check is popped up (i.e., the sixth information is sent to the target terminal) to allow the user to modify the content of the file.

[0044] According to some optional embodiments of the present application, the third debugging information after the second protocol header has been added is displayed through an interactive page, including: if the third debugging information corresponds to multiple display results, sending third information to the target terminal, wherein the third information is information requesting the target terminal to select multiple graphical display results; receiving fourth information detected by the interactive page, and displaying the third debugging information after the second protocol header has been added according to the fourth information, wherein the fourth information is information corresponding to the third information.

[0045] In some preferred embodiments, when debugging an algorithm, different debugging versions such as a normal version or an expert version can be provided for the user to choose. When debugging an algorithm, multiple versions are loaded together. If different versions of debugging files are found to exist for the same algorithm when debugging the algorithm, a third message will be sent to the target terminal when initiating the debugging, and the third message will be displayed on the front-end interactive page, allowing the user to select the displayed result; then the user's selection result (i.e., the fourth message) will be received, and different debugging pages will be displayed according to the selection result.

[0046] According to an optional embodiment of the present application, the third debugging information after the second protocol header is added is displayed through an interactive page, wherein the result displayed by the interactive page is pre-stored in the interactive page.

[0047] The front-end page (i.e., the interactive interface) embeds the debugging interface corresponding to the debugging information (e.g., the third debugging information after adding the second protocol header) for display into the document of the front-end page file through the provided frame (iframe) embedded interface, and reloading can be achieved without refreshing the interface.

[0048] According to other optional embodiments of the present application, a method for displaying debugging information is also provided, the method comprising: receiving a debugging file, extracting protocol content, wherein the protocol content is stored in the debugging file; matching a third protocol header for the protocol content, generating fourth debugging information based on the protocol content and the third protocol header, and sending the fourth debugging information to a backend; receiving fifth debugging information, parsing the fourth protocol header of the fifth debugging information, and obtaining a parsing result, wherein the fifth debugging information is a result of the backend processing the fourth debugging information; and displaying the fifth debugging information through an interactive page based on the parsing result.

[0049] According to the method provided in this embodiment, after the front-end page process displays the embedded debugging front-end page, the user can operate in it. The user uploads the written debugging file to the front-end page and performs related operations; the front-end page recognizes the debugging file uploaded by the user and the operations performed, extracts the part of the protocol content in the debugging file uploaded by the user, and matches it with the corresponding (third) protocol header, combines the protocol content, i.e., the (third) protocol header, and generates the (fourth) debugging information to be sent to the back-end (framework process). The background framework process parses the (third) protocol header, and after determining that it is debugging information, sends the remaining protocol content (i.e., the fourth debugging information) to the dynamic library of the back-end for parsing, and finally matches the (fourth) protocol header for the parsed result, combines it into the fifth debugging information and sends it to the front-end interactive page, and the front-end interactive page displays the corresponding debugging result.

[0050] It should be noted that if the protocol content is HTML protocol content, it has the following characteristics: the HTML protocol content design includes two layers of protocol headers, in which the outer layer protocol header is parsed by the configuration software, and the inner layer protocol header and protocol content are forwarded to the back-end dynamic library for processing and parsing.

[0051] Figure 2 FIG. 1 is a structural diagram of a display device for debugging information provided in an embodiment of the present application. Figure 2 As shown, the device comprises:

[0052] The receiving module 20 is used to receive first debugging information, and delete the first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is received through the interactive page;

[0053] The parsing module 22 is used to parse the second debugging information again to obtain third debugging information, wherein the third debugging information is information about a value to be read or written for the target algorithm;

[0054] The display module 24 is used to add the second protocol header to the third debugging information, and send the third debugging information after the second protocol header is added to the interactive page, so as to display the third debugging information after the second protocol header is added through the interactive page.

[0055] According to this embodiment, a specific implementation method is provided, in which the above method is applied to a plug-in function block debugging panel based on HTML. Figure 3 It is a plug-in function block debugging panel based on HTML. It is a schematic diagram of the interaction between each process when debugging the algorithm. Figure 3 As shown, after the front-end page process displays the embedded debugging front-end page, the user can operate in it, and the message sent is sent by the front-end page process to the background framework process; after the background framework process receives the message, it parses the protocol header and finds that it is a debugging message, so it forwards the protocol content to the corresponding debugging dynamic library after stripping off the protocol header; after the debugging dynamic library receives the message, it specifically parses the protocol according to the second-layer protocol header and processes it, and replies to the background framework process after completion; after the background framework process receives the message, it adds the debugging message protocol header to the message and forwards it to the front-end page process, thereby completing an interactive process of the page and displaying the debugging result.

[0056] In the specific implementation, the above method is used to realize an HTML-based plug-in function block debugging panel integration method, so that users (such as algorithm engineers) can customize the debugging panel and freely add graphical displays; users (such as algorithm developers) can customize the debugging interface they want through the agreed file format, so that the debugging page is more closely aligned with the algorithm, thereby greatly improving the efficiency of algorithm debugging.

[0057] An embodiment of the present application further provides a non-volatile storage medium, the non-volatile storage medium including a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the above method for displaying debugging information.

[0058] The above-mentioned non-volatile storage medium is used to store a program that performs the following functions: receiving first debugging information, deleting the first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is sent through an interactive page; re-parsing the second debugging information to obtain third debugging information, wherein the third debugging information is; adding the second protocol header to the third debugging information, and sending the third debugging information after the second protocol header is added to the interactive page, so as to display the third debugging information after the second protocol header is added through the interactive page.

[0059] The embodiment of the present application further provides a processor, which is used to run a program stored in a memory, wherein the above method for displaying debugging information is executed when the program is running.

[0060] The above-mentioned processor is used to run a program that performs the following functions: receiving first debugging information, deleting the first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is sent through an interactive page; re-parsing the second debugging information to obtain third debugging information, wherein the third debugging information is; adding the second protocol header to the third debugging information, and sending the third debugging information after the second protocol header is added to the interactive page, so as to display the third debugging information after the second protocol header is added through the interactive page.

[0061] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0062] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0063] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0064] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0065] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0066] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0067] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for displaying debugging information, characterized in that, it includes: Receiving first debugging information, deleting a first protocol header in the first debugging information to obtain second debugging information, wherein the first debugging information is sent through an interaction page, the first debugging information is received by a background framework process in a backend that interacts with the interaction page, the backend and the interaction page together form a configuration software, before starting the configuration software, loading a dynamic library of the configuration software, and the loading of the dynamic library is executed by a new subprocess, and the new subprocess is a process different from the process that interacts with the interaction page and the backend; Re-parsing the second debugging information to obtain third debugging information, wherein the third debugging information is information about a value to be read or written by a target algorithm; Adding a second protocol header to the third debugging information, and sending the third debugging information after adding the second protocol header to the interaction page to display the third debugging information after adding the second protocol header through the interaction page. Before displaying the third debugging information after adding the second protocol header through the interaction page, it includes: debugging the interaction page and debugging the dynamic library. In the case where the result of debugging the interaction page is passed and the result of debugging the dynamic library is passed, it is determined that the interaction page is successfully loaded. In the case where there is a failure in the result of debugging the interaction page and the result of debugging the dynamic library, a prompt for failed check is popped up. Wherein, debugging the interaction page includes: running an HTML page and determining whether it is normally loaded; debugging the dynamic library includes: calling all interfaces that implement the functions of the dynamic library through the new subprocess to check whether all interfaces are implemented and whether it will crash.

2. The method according to claim 1, characterized in that, Receiving first debugging information and deleting the first protocol header in the first debugging information includes: Starting a first preset process, parsing the first protocol header, and determining whether the first debugging information is target information according to the result of parsing the first protocol header, wherein the first preset process is a process that interacts with the interaction page; If the first debugging information is the target information, deleting the first protocol header to obtain the second debugging information; If the first debugging information is not the target information, then refusing to delete the first protocol header.

3. The method according to claim 2, characterized in that, Before re-parsing the second debugging information, it includes: Starting a second preset process, wherein the second preset process is a process for loading a configuration software, and the configuration software is used to control the interaction page to display the third debugging information after adding the second protocol header; Sending a first message from the first preset process to the second preset process at a preset moment, and if receiving a second message sent by the second preset process, determining that the second preset process has not failed, wherein the first message and the second message are a set of corresponding messages; If the second information is not received, determine that the second preset process has failed and check the second preset process.

4. The method according to claim 3, wherein, before displaying the third debugging information after adding the second protocol header through the interactive page, it includes: Debug the interactive page and the second preset process. If the debugging result indicates that the interactive page and the second preset process have not failed, determine to send a fifth message to the target terminal, where the fifth message is a message indicating that the interactive page has been successfully loaded; If the debugging result indicates that the interactive page or the second preset process has failed, send a sixth message to the target terminal, where the sixth message is a message prompting the target terminal to make modifications.

5. The method according to claim 4, wherein, displaying the third debugging information after adding the second protocol header through the interactive page includes: If the third debugging information corresponds to multiple display results, send a third message to the target terminal, where the third message is a message requesting the target terminal to select from multiple graphical display results; Receive the fourth information detected by the interactive page, and display the third debugging information after adding the second protocol header according to the fourth information, where the fourth information is information corresponding to the third message.

6. The method according to claim 1, wherein, display the third debugging information after adding the second protocol header through the interactive page, where the result displayed by the interactive page is pre-stored in the interactive page.

7. A method for displaying debugging information, wherein, it includes: Receive a debugging file and extract protocol content, where the protocol content is stored in the debugging file; Match a third protocol header for the protocol content, generate fourth debugging information according to the protocol content and the third protocol header, and send it to the backend; Receive fifth debugging information, parse the fourth protocol header of the fifth debugging information to obtain a parsing result, where the fifth debugging information is the result of the backend processing the fourth debugging information; Display the fifth debugging information through an interactive page according to the parsing result; The fifth debugging information is obtained by the following method: Parse the fourth debugging information by a dynamic library, combine the result of parsing the fourth debugging information with the fourth protocol header to form the fifth debugging information, where the dynamic library is used for loading by a controller configuration software, and the dynamic library is debugged by the following method: Start a new subprocess, call all interfaces that implement the functions of the dynamic library through the new subprocess, check whether all interfaces are implemented and whether it will crash, and the new subprocess is different from the first preset process, and the first preset process is the process for the backend to interact with the interactive page.

8. A device for displaying debugging information, wherein, it includes: A receiving module, configured to receive first debugging information, delete a first protocol header in the first debugging information to obtain second debugging information, where the first debugging information is sent through an interactive page, the first debugging information is received by a background framework process in a backend that interacts with the interactive page, the backend and the interactive page together form a configuration software, before starting the configuration software, load a dynamic library of the configuration software, and the loading of the dynamic library is executed by a new subprocess, and the new subprocess is a process different from the process that interacts with the interactive page and the backend; A parsing module, configured to re-parse the second debugging information to obtain third debugging information, where the third debugging information is information about a value to be read or written by a target algorithm; A display module, configured to add a second protocol header to the third debugging information, and send the third debugging information after adding the second protocol header to the interactive page, so as to display the third debugging information after adding the second protocol header through the interactive page. Before displaying the third debugging information after adding the second protocol header through the interactive page, it includes: debugging the interactive page and debugging the dynamic library. When the result of debugging the interactive page is passed and the result of debugging the dynamic library is passed, it is determined that the interactive page is successfully loaded. When there is a failure in the result of debugging the interactive page and the result of debugging the dynamic library, a prompt for failed check is popped up. Wherein, debugging the interactive page includes: running an HTML page and determining whether it is normally loaded; debugging the dynamic library includes: calling all interfaces that implement the functions of the dynamic library through the new subprocess, and checking whether all interfaces are implemented and whether there will be a crash.

9. A non-volatile storage medium, characterized in that, the non-volatile storage medium includes a stored program, wherein when the program runs, it controls the device where the non-volatile storage medium is located to execute the method for displaying debugging information according to any one of claims 1 to 7.

10. A processor, characterized in that, the processor is used to run a program stored in a memory, wherein when the program runs, it executes the method for displaying debugging information according to any one of claims 1 to 7.

Images