CN114880231A - Debugging method, debugging device and computing device for application program control - Google Patents

Abstract

The invention discloses a debugging method, a debugging device and a computing device for an application program control. The method is executed in the computing device and includes the steps of: acquiring a preprocessing source code file, and constructing an application program based on the preprocessing source code file, wherein the preprocessing source code file is used to construct an application program. The processing source code file includes one or more control objects and the prompt code corresponding to each control object, and the interface of the application program includes controls corresponding to each control object; test each control in the application program interface, Determine one or more exception controls in the application program interface; in response to a predetermined operation on the exception control, execute the prompt code corresponding to the exception control to display corresponding prompt information within a predetermined range of the exception control, so as to be based on The prompt information locates the control object corresponding to the exception control in the preprocessing source code file. According to the technical solution of the present invention, the control object corresponding to the abnormal control can be quickly located.

Description

Debugging method, debugging device and computing device for application program control

This application is a divisional application of invention patent application 2022102142779 filed on March 7, 2022.

technical field

The invention relates to the technical field of computer and software debugging, in particular to a debugging method, a debugging device and a computing device for an application program control.

Background technique

In the existing graphical operating system, developers often need to integrate a large number of control units in the software. However, when testing the software, developers can only submit bugs to developers according to the display of the interface. Faced with a large number of control unit objects in code files, developers or subsequent maintainers often cannot quickly and accurately locate them. The exception control is the control object in the code file, which causes a lot of time in this link.

There is a software debugging tool in the prior art, which generates the Tool Tip execution code of the control object by capturing the debugging information embedded by the compiler in the compilation stage, and automatically modifies the machine code of the executable file, and then displays it in the subsequent debugging process. marked content. However, with this technical solution, the generation of machine code and debugging information depends on the compiler version and system environment at that time. When the compiler is upgraded or the system environment is changed, the corresponding software debugging tools also need to be upgraded and adapted. As a result, the software debugging tools written each time have certain limitations.

Therefore, a debugging method for an application control is required to solve the problems existing in the above technical solutions.

SUMMARY OF THE INVENTION

To this end, the present invention provides a debugging method and a debugging device for an application program control, so as to try to solve or at least alleviate the above problems.

According to an aspect of the present invention, there is provided a debugging method for an application program control, which is executed in a computing device and includes the steps of: acquiring a preprocessed source code file, and constructing an application program based on the preprocessed source code file, wherein the preprocessed source code file is used. The processing source code file includes one or more control objects and a prompt code corresponding to each control object, and the interface of the application program includes a control corresponding to each control object; testing to determine one or more abnormal controls in the application program interface; and in response to a predetermined operation on the abnormal control, executing a prompt code corresponding to the abnormal control to be within a predetermined range of the abnormal control Corresponding prompt information is displayed inside, so as to locate the control object corresponding to the abnormal control in the preprocessed source code file based on the prompt information.

Optionally, in the debugging method of the application control according to the present invention, responding to the predetermined operation on the abnormal control includes: responding to the operation of hovering the mouse pointer on the abnormal control for a predetermined time.

Optionally, in the debugging method for an application control according to the present invention, the prompt information includes an object identifier name corresponding to the exception control.

Optionally, in the debugging method for an application program control according to the present invention, before acquiring the preprocessed source code file, the steps include: acquiring one or more source code files corresponding to the application program; All control objects; insert the prompt code corresponding to each control object in the source code file to get the preprocessed source code file.

Optionally, in the debugging method for an application program control according to the present invention, the step of inserting a prompt code corresponding to each control object in the source code file includes: obtaining the code location where each control object first applies for memory. ; Insert a prompt code corresponding to the control object in the source code file based on the code position where each control object first applies for the memory to obtain a preprocessed source code file.

Optionally, in the debugging method for an application program control according to the present invention, the step of acquiring one or more source code files corresponding to the application program includes: acquiring one or more source code file paths corresponding to the application program; Source code file path to get the corresponding source code file.

Optionally, in the debugging method for an application program control according to the present invention, the step of determining all control objects in each source code file includes: traversing each source code file, and locating each control object in the source code file , and tag each control object.

Optionally, in the debugging method for an application control according to the present invention, the prompt code is a code for executing ToolTip operation.

According to one aspect of the present invention, there is provided a debugging apparatus, resident in a computing device, comprising: a building module adapted to obtain a preprocessed source code file, and build an application program based on the preprocessed source code file, wherein the The preprocessing source code file includes one or more control objects and a prompt code corresponding to each control object, and the interface of the application program includes a control corresponding to each control object; the test module is suitable for the application program interface. Each control in is tested to determine one or more abnormal controls in the application program interface; and a prompt module adapted to perform a prompt corresponding to the abnormal control in response to a predetermined operation on the abnormal control code to display corresponding prompt information within a predetermined range of the exception control, so as to locate a control object corresponding to the abnormal control in the preprocessed source code file based on the prompt information.

According to one aspect of the present invention, there is provided a computing device comprising: at least one processor; and a memory storing program instructions, wherein the program instructions are configured to be adapted to be executed by the at least one processor, the The program instructions include instructions for executing the debugging method of the application control as described above.

According to an aspect of the present invention, there is provided a readable storage medium storing program instructions, which when read and executed by a computing device, cause the computing device to perform the method as described above.

According to the technical solution of the present invention, there is provided a debugging method for an application program control. An application program is constructed based on a preprocessed source code file obtained by pre-embedding the prompt code corresponding to each control in the source code file, and the After each control in the application interface is tested, each abnormal control is determined. According to the prompt code corresponding to each control embedded in the preprocessing source code file, the developer can perform a predetermined operation on the abnormal control in the application interface to trigger the The prompt information related to the exception control is displayed on the interface, so that the developer can quickly and accurately locate the control object corresponding to the abnormal control in the preprocessing source code file according to the prompt information corresponding to the abnormal control, so as to facilitate the detection of the abnormal control. The control object is debugged, which is beneficial to improve the debugging efficiency of the application control.

The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

Description of drawings

To achieve the above and related objects, certain illustrative aspects are described herein in conjunction with the following description and drawings, which are indicative of the various ways in which the principles disclosed herein may be practiced, and all aspects and their equivalents are intended to be within the scope of the claimed subject matter. The above and other objects, features and advantages of the present disclosure will become more apparent by reading the following detailed description in conjunction with the accompanying drawings. Throughout this disclosure, the same reference numbers generally refer to the same parts or elements.

FIG. 1 shows a schematic block diagram of a computing device 100 according to an embodiment of the present invention;

FIG. 2 shows a flowchart of a debugging method 200 of an application control according to an embodiment of the present invention;

Figure 3 shows a flowchart of preprocessing a source code file according to an embodiment of the present invention; and

FIG. 4 shows a schematic diagram of a debugging apparatus 400 according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

FIG. 1 is a schematic block diagram of an example computing device 100 .

As shown in FIG. 1 , in a basic configuration 102 , computing device 100 typically includes system memory 106 and one or more processors 104 . The memory bus 108 may be used for communication between the processor 104 and the system memory 106 .

Depending on the desired configuration, the processor 104 may be any type of process including, but not limited to, a microprocessor (UP), a microcontroller (UC), a digital information processor (DSP), or any combination thereof. Processor 104 may include one or more levels of cache, such as L1 cache 110 and L2 cache 112 , processor core 114 , and registers 116 . Exemplary processor cores 114 may include arithmetic logic units (ALUs), floating point units (FPUs), digital signal processing cores (DSP cores), or any combination thereof. The exemplary memory controller 118 may be used with the processor 104 , or in some implementations, the memory controller 118 may be an internal part of the processor 104 .

Depending on the desired configuration, system memory 106 may be any type of memory including, but not limited to, volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 106 may include operating system 120 , one or more applications 122 , and program data 124 . In some embodiments, applications 122 may be arranged to execute instructions using program data 124 by one or more processors 104 on an operating system.

Computing device 100 also includes storage device 132 including removable storage 136 and non-removable storage 138 .

Computing device 100 may also include a storage interface bus 134 . Storage interface bus 134 enables communication from storage devices 132 (eg, removable storage 136 and non-removable storage 138 ) to base configuration 102 via bus/interface controller 130 . Operating system 120, applications 122, and at least a portion of data 124 may be stored on removable storage 136 and/or non-removable storage 138, and via the storage interface bus when computing device 100 is powered on or applications 122 are to be executed 134 is loaded into system memory 106 and executed by one or more processors 104 .

Computing device 100 may also include an interface bus 140 that facilitates communication from various interface devices (eg, output device 142 , peripheral interface 144 , and communication device 146 ) to base configuration 102 via bus/interface controller 130 . Exemplary output device 142 includes image processing unit 148 and audio processing unit 150 . They may be configured to facilitate communication via one or more A/V ports 152 with various external devices such as displays or speakers. Example peripheral interfaces 144 may include serial interface controller 154 and parallel interface controller 156, which may be configured to facilitate communication via one or more I/O ports 158 and input devices such as keyboard, mouse, pen , voice input devices, touch input devices) or other peripherals (eg printers, scanners, etc.) The example communication device 146 may include a network controller 160 that may be arranged to facilitate communication via one or more communication ports 164 with one or more other computing devices 162 over a network communication link.

A network communication link may be one example of a communication medium. Communication media may typically embody computer readable instructions, data structures, program modules in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media. A "modulated data signal" may be a signal in which one or more of its data sets or whose changes may be made in the signal in a manner that encodes information. By way of non-limiting example, communication media may include wired media, such as wired or leased line networks, and various wireless media, such as acoustic, radio frequency (RF), microwave, infrared (IR), or other wireless media. The term computer readable medium as used herein may include both storage media and communication media.

Computing device 100 may be implemented as a personal computer including a desktop computer and a notebook computer configuration. Of course, computing device 100 may also be implemented as part of a small form factor portable (or mobile) electronic device such as a cellular telephone, digital camera, personal digital assistant (PDA), personal media player device, wireless web browsing device , personal headsets, application-specific devices, or hybrid devices that can include any of the above. It can even be implemented as a server, such as a file server, database server, application server, and WEB server. The embodiments of the present invention do not limit this.

In an embodiment according to the present invention, the computing device 100 is configured to perform the debugging method 200 of an application control according to the present invention. Wherein, the application of the computing device 100 includes a plurality of program instructions for executing the debugging method 200 of the application program control of the present invention, and these program instructions can be read and executed by the processor, so that the computing device 100 can execute the application of the present invention by executing the program instructions of the present invention. The debugging method 200 of the program control can quickly locate the control object corresponding to the abnormal control after the abnormal control is determined.

According to an embodiment of the present invention, the application of the computing device 100 includes a debugging apparatus 300, and the debugging apparatus 300 includes a plurality of program instructions for executing the debugging method 200 of the application program control of the present invention, so that the application program control of the present invention is The debugging method 200 can be executed in the debugging apparatus 300 .

FIG. 2 shows a flowchart of a debugging method 200 of an application control according to an embodiment of the present invention. The debugging method 200 of an application control can be executed in a debugging apparatus 300 of a computing device (eg, the aforementioned computing device 100 ).

In an embodiment according to the present invention, the application is a GUI application with a graphical user interface, and the interface of the GUI application includes one or more controls.

As shown in FIG. 2, the method 200 includes steps S210-S230.

In step S210, a preprocessing source code file is acquired, and a corresponding application program is constructed based on the preprocessing source code file. Here, the present invention constructs the application program by compiling the preprocessed source code file, and the application program obtained by construction is the application program to be debugged. Wherein, the preprocessing source code file includes one or more control objects and prompt codes corresponding to each control object, and the interface of the application program includes controls corresponding to each control object in the preprocessing source code file.

It should be noted that the application to be debugged may correspond to one or more preprocessed source code files. In other words, the application to be debugged can be constructed based on one or more corresponding preprocessed source code files. Based on this, what is acquired in step S210 may be one or more preprocessed source code files corresponding to the application. Each preprocessed source code file is obtained by preprocessing the corresponding source code file.

Subsequently, in step S220, the constructed application program is run on the operating system of the computing device, and by testing each control in the application program interface, the function and performance of each control are tested, so as to determine the existence of the application program interface. One or more exception controls for the exception.

In one embodiment, the controls tested in the application program interface include, for example, one of a text box, a list box, a check box, a search box, a command button, a radio button, a page turning control, an upload control, and a scroll bar or variety.

In an implementation manner, a GUI-based automated testing tool can be used to automatically test each control in the application interface by writing test scripts and inputting test data, and automatically running the test program. Control operations (including simulated input operations, simulated click operations, simulated sliding operations, etc.) to complete the functional and performance testing of each control.

In an implementation manner, the automated testing process for the controls may include a recording and playback process, and the recording process may use an automated testing tool to test the functions of the controls in the application, record the operation process, and generate corresponding scripts. During the playback process, errors and defects existing in the recording process can be viewed based on the script generated by the recording process to determine one or more abnormal controls existing in the application program interface.

It should be pointed out that the present invention does not limit the specific method for testing the control, and any testing method in the prior art that can realize automatic testing of the control is within the protection scope of the present invention.

Next, for each abnormal control in the application program interface determined after testing, the developer performs a predetermined operation on the abnormal control to trigger the display of prompt information corresponding to the abnormal control. For details, refer to the following step S230.

In step S230, in response to a predetermined operation on the exception widget in the application program interface, a prompt code corresponding to the exception widget (corresponding widget object) is executed to display corresponding prompt information within a predetermined range of the exception widget. Here, the prompt information includes relevant information of the abnormal control. The present invention displays the prompt information corresponding to the abnormal control in response to the predetermined operation on the abnormal control, so that the prompt information corresponding to the abnormal control can be quickly and accurately located in the preprocessing source code file based on the prompt information corresponding to the abnormal control. Control object. In this way, the process of locating the exception control object is more time-saving, so as to facilitate the troubleshooting of the exception control object, thereby improving the overall efficiency of the application control.

It should be noted that the prompt code corresponding to each control object is pre-buried in the preprocessing source code file corresponding to the application, and the predetermined operation on the abnormal control can trigger the execution of the prompt code corresponding to the abnormal control. The prompt code corresponding to the abnormal control can display prompt information corresponding to the abnormal control within a predetermined range around the abnormal control.

It should be noted that, in the embodiment of the present invention, the application to be debugged is constructed based on the preprocessed source code file obtained after preprocessing the source code file and pre-embedding the prompt code corresponding to each control in the source code file , by testing each control in the application program interface to determine each abnormal control, according to the prompt code corresponding to each control embedded in the preprocessing source code file, the developer can perform predetermined operations on the abnormal control in the application program interface The trigger displays the prompt information related to the exception control on the interface, so that the developer can quickly and accurately locate the control object corresponding to the exception control in the preprocessed source code file according to the prompt information corresponding to the exception control.

In one embodiment, after the prompt code corresponding to the exception control is executed, the prompt information displayed within a predetermined range of the exception control specifically includes the object identifier name corresponding to the exception control. In this way, the developer can quickly and accurately locate the control object corresponding to the abnormal control in the preprocessed source code file according to the object identifier corresponding to the abnormal control.

It should be pointed out that the present invention is not limited to the specific operation manner of performing the predetermined operation on the abnormal control. In an implementation manner, the predetermined operation on the exception control may be, for example, an operation in which the mouse pointer hovers over the exception control for a predetermined time. In other words, in step S230, the prompt code corresponding to the abnormal control may be executed in response to the operation of hovering the mouse pointer on the abnormal control for a predetermined time to display corresponding prompt information within a predetermined range of the abnormal control.

According to an embodiment of the present invention, before step S210 is performed to obtain the preprocessed source code file, one or more source code files corresponding to the application are preprocessed to obtain one or more corresponding preprocessed source code files .

FIG. 3 shows a flowchart of preprocessing a source code file according to an embodiment of the present invention.

As shown in Figure 3, the method of preprocessing the source code file can be implemented as:

Get one or more source code files corresponding to the application. Specifically, by acquiring one or more source code file paths corresponding to the application, and then sequentially extracting each source code file path, the corresponding source code file is acquired based on each source code file path.

Next, identify all control objects in each source code file. In an implementation manner, by traversing each source code file, each control object (object belonging to the control) is located in the source code file, and each control object can be marked. Here, the control object may include objects such as pointers, non-pointers, and the like.

Next, insert the prompt code corresponding to each control object in the source code file to obtain the preprocessed source code file. Specifically, extract each control object in turn, obtain the code location where each control object applies for memory for the first time, and insert the code location corresponding to each control object in the source code file based on the code location where each control object applies for memory for the first time. The corresponding prompt code can obtain the preprocessed source code file corresponding to the source code file.

In an implementation manner, each marked control object is successively extracted from the source code file, and the code location where each marked control object first applies for memory is obtained. Furthermore, a prompt code corresponding to the control object may be inserted in the source code file below the code position where the control object first applies for memory.

It should be noted that, by executing the prompt code corresponding to the control object, corresponding prompt information can be generated, and the prompt information includes the object identifier name of the control object.

It should also be pointed out that the steps of preprocessing the source code file in the present invention are all automatically executed in the debugging device, wherein the positioning and marking of each control object in the source code file and the operation of inserting the prompt code are automatically executed, There is no need for developers to find control objects and manually modify code. In this way, the efficiency of inserting prompt codes into the control object during the preprocessing of the source code file is improved.

In one embodiment, the tip code may be specifically implemented as source code for performing a Tool Tip (tool tip) operation. That is, the source code corresponding to the control object for performing the Tool Tip operation is inserted below the code position where the control object first applies for memory in the source code file. It should be noted that inserting the source code to perform the Tool Tip operation in the source code file will not affect the running process of the application, and thus will not affect the testing of the application controls.

As shown in Figure 3, for each control object, after inserting the prompt code corresponding to the control object (source code for executing the Tool Tip operation) below the code position where the control object first applied for memory, it is judged whether the object is a The last control object, if it is not the last control object, extract the next control object in the current source code file, obtain the code location where the next control object first applies for memory, and apply the memory for the first time to the next control object. Insert the prompt code corresponding to the control object below the code position.

If it is the last control object, make sure that the preprocessing of the source code file is completed, save the current modified source code file, and obtain the corresponding preprocessed source code file. Next, determine whether the source code file is the last source code file, if not, extract the next source code file path, and obtain the next source code file based on the next source code file path, and then execute the above-mentioned source code file. The preprocessing step is until the prompt code corresponding to the control object is inserted below the code position where each control object first applies for memory in the next source code file.

If the source code file is the last source code file, the preprocessing process for all source code files ends, and a preprocessed source code file corresponding to each source code file is obtained at this time.

In one embodiment, the source code file and the preprocessed source code file are both C++ source code files, and correspondingly, the control object is a C++ object.

In an implementation manner, after each source code file is obtained, an analysis session may be created based on the source code file, one or more control objects in the source code file are determined through analysis, and each control object is obtained, and then, For each control object, obtain the location where the control object first applied for memory. Next, within the analysis session, insert a hint code into the code position where the control object completes its memory application for the first time. Finally, restore the analysis session to the source code file and save it to get the preprocessed source code file.

FIG. 4 shows a schematic diagram of a debugging apparatus 400 according to an embodiment of the present invention. The debugging apparatus 400 is deployed in a computing device (eg, the aforementioned computing device 100 ), and is suitable for executing the debugging method 200 of the application control of the present invention.

As shown in FIG. 4 , the debugging apparatus 400 includes a preprocessing module 405 , a building module 410 , a testing module 420 and a prompting module 430 coupled in sequence.

Wherein, the preprocessing module 405 is configured to execute the aforementioned preprocessing process for source code files (refer to FIG. 3 for details), and obtain corresponding one or more source code files by preprocessing one or more source code files corresponding to the application program. Preprocess source code files.

The building module 410 can obtain preprocessed source code files obtained by preprocessing the source code files by the preprocessing module, and build an application program based on the preprocessed source code files. The preprocessing source code file includes one or more control objects and prompt codes corresponding to each control object, and the interface of the application program includes controls corresponding to each control object.

By running the application on the operating system, each control in the application interface is tested using the testing module 420 to determine one or more abnormal controls in the application interface.

The prompt module 430, in response to a predetermined operation on the exception control, executes the prompt code corresponding to the exception control, so as to display corresponding prompt information within a predetermined range of the abnormal control, so as to locate in the preprocessed source code file based on the prompt information. The control object corresponding to the exception control.

It should be noted that the preprocessing module 405 is configured to perform the aforementioned preprocessing process for source code files, by preprocessing one or more source code files corresponding to the application program to obtain one or more corresponding preprocessed source code files . The building module 410 is used for executing the foregoing step S210, the testing module 420 is used for executing the foregoing step S220, and the prompting module 430 is used for executing the foregoing step S230. Here, for the specific execution logic of the preprocessing module 405 , the building module 410 , the testing module 420 and the prompting module 430 , refer to the description of the preprocessing flow before step S210 and the descriptions of steps S210 to S230 in the foregoing method 200 , which will not be repeated here.

The debugging method 200 of an application program control according to the present invention is to construct an application program based on the preprocessed source code file obtained after pre-embedding the prompt code corresponding to each control in the source code file, and by adjusting the information in the application program interface After each control is tested, each abnormal control is determined. According to the prompt code corresponding to each control embedded in the preprocessing source code file, the developer can perform a predetermined operation on the abnormal control in the application program interface to trigger the display on the interface. In this way, developers can quickly and accurately locate the control object corresponding to the abnormal control in the preprocessed source code file according to the corresponding prompt information of the abnormal control, so as to troubleshoot the abnormal control object. processing, thereby helping to improve the debugging efficiency of application controls.

The various techniques described herein can be implemented in conjunction with hardware or software, or a combination thereof. Thus, the method and apparatus of the present invention, or certain aspects or portions of the method and apparatus of the present invention, may take the form of an embedded tangible medium, such as a removable hard disk, a USB stick, a floppy disk, a CD-ROM, or any other machine-readable storage medium. in the form of program code (ie, instructions) that, when the program is loaded into a machine, such as a computer, and executed by the machine, the machine becomes an apparatus for practicing the invention.

Where the program code is executed on a programmable computer, the computing device typically includes a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. Wherein, the memory is configured to store program codes; the processor is configured to execute the debugging method of the application program control of the present invention according to the instructions in the program codes stored in the memory.

By way of example and not limitation, readable media include readable storage media and communication media. Readable storage media store information such as computer readable instructions, data structures, program modules or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of readable media.

In the specification provided herein, the algorithms and displays are not inherently related to any particular computer, virtual system, or other device. Various general purpose systems may also be used with examples of the present invention. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not directed to any particular programming language. It is to be understood that various programming languages may be used to implement the inventions described herein, and that the descriptions of specific languages above are intended to disclose the best mode for carrying out the invention.

In the description provided herein, numerous specific details are set forth. It will be understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it is to be understood that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or its description. This disclosure, however, should not be interpreted as reflecting an intention that the invention as claimed requires more features than are expressly recited in each claim. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules or units or components of the apparatus in the examples disclosed herein may be arranged in the apparatus as described in this embodiment, or alternatively may be positioned differently from the apparatus in this example in one or more devices. The modules in the preceding examples may be combined into one module or further divided into sub-modules.

Those skilled in the art will understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. The modules or units or components in the embodiments may be combined into one module or unit or component, and further they may be divided into multiple sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method so disclosed may be employed in any combination, unless at least some of such features and/or procedures or elements are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that although some of the embodiments described herein include certain features, but not others, included in other embodiments, that combinations of features of different embodiments are intended to be within the scope of the invention within and form different embodiments.

Furthermore, some of the described embodiments are described herein as methods or combinations of method elements that can be implemented by a processor of a computer system or by other means for performing the described functions. Thus, a processor having the necessary instructions for implementing the method or method element forms means for implementing the method or method element. Furthermore, an element of an apparatus embodiment described herein is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

As used herein, unless otherwise specified, the use of the ordinal numbers "first," "second," "third," etc. to describe common objects merely refers to different instances of similar objects, and is not intended to imply such The objects being described must have a given order in time, space, ordinal, or in any other way.

While the invention has been described in terms of a limited number of embodiments, those skilled in the art will appreciate, having the benefit of the above description, that other embodiments are conceivable within the scope of the invention thus described. Furthermore, it should be noted that the language used in this specification has been principally selected for readability and teaching purposes, rather than to explain or define the subject matter of the invention. Accordingly, many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the appended claims. This disclosure is intended to be illustrative, not restrictive, as to the scope of the present invention, which is defined by the appended claims.

Claims (10)

1. A debugging method of an application control is executed in a computing device and comprises the following steps:

acquiring one or more source code files corresponding to the application program;

determining all control objects in each source code file;

inserting a prompt code corresponding to each control object in a source code file to obtain a preprocessed source code file;

acquiring a preprocessing source code file, and constructing an application program based on the preprocessing source code file, wherein an interface of the application program comprises a control corresponding to each control object;

testing each control in an application program interface to determine one or more abnormal controls in the application program interface; and

and responding to a preset operation on an abnormal control, executing prompt codes corresponding to the abnormal control to display corresponding prompt information in a preset range of the abnormal control, so as to locate a control object corresponding to the abnormal control in the preprocessing source code file based on the prompt information.

2. The method of claim 1, wherein responding to a predetermined operation on an exception control comprises:

and responding to the operation that the mouse pointer hovers over the abnormal control for the preset time.

3. The method of claim 1 or 2, wherein the hint information includes an object identifier name corresponding to the exception control.

4. The method of any of claims 1-3, wherein inserting hinting code corresponding to each control object in a source code file comprises:

acquiring a code position of a first memory application of each control object;

and inserting a prompt code corresponding to each control object into the source code file based on the code position of the memory which is applied for the first time by each control object to obtain a preprocessed source code file.

5. The method of any one of claims 1-4, wherein obtaining one or more source code files corresponding to the application comprises:

acquiring one or more source code file paths corresponding to an application program;

and acquiring a corresponding source code file based on each source code file path.

6. The method of any of claims 1-5, wherein determining all control objects in each source code file comprises:

and traversing each source code file, positioning each control object in the source code file, and marking each control object.

7. The method of any one of claims 1-6,

the prompt code is code for executing a Tool Tip operation.

8. A debugging apparatus, resident in a computing device, comprising:

the construction module is suitable for acquiring one or more source code files corresponding to the application program, determining all control objects in each source code file, and inserting a prompt code corresponding to each control object into the source code file to obtain a preprocessed source code file; the method comprises the steps of obtaining a preprocessing source code file, and constructing an application program based on the preprocessing source code file, wherein an interface of the application program comprises a control corresponding to each control object;

the testing module is suitable for testing each control in the application program interface so as to determine one or more abnormal controls in the application program interface; and

and the prompt module is suitable for responding to a preset operation on an abnormal control, executing prompt codes corresponding to the abnormal control to display corresponding prompt information in a preset range of the abnormal control, so that a control object corresponding to the abnormal control is positioned in the preprocessing source code file based on the prompt information.

9. A computing device, comprising:

at least one processor; and

a memory storing program instructions, wherein the program instructions are configured to be adapted to be executed by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 1-7.

10. A readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform the method of any of claims 1-7.

Images