CN110781080A - Program debugging method and device and storage medium - Google Patents
Program debugging method and device and storage medium Download PDFInfo
- Publication number
- CN110781080A CN110781080A CN201910963097.9A CN201910963097A CN110781080A CN 110781080 A CN110781080 A CN 110781080A CN 201910963097 A CN201910963097 A CN 201910963097A CN 110781080 A CN110781080 A CN 110781080A
- Authority
- CN
- China
- Prior art keywords
- debugging
- page
- refreshing
- debug
- platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4812—Task transfer initiation or dispatching by interrupt, e.g. masked
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure relates to a program debugging method and device and a storage medium. The method comprises the following steps: in a debugging process aiming at a debugging object, receiving a page refreshing signal sent by a debugging front end, wherein the debugging object comprises: fast applications and/or applets; interrupting the operation of the debugging object according to the page refreshing signal; determining a page refreshing mode according to the page refreshing signal; and after the operation of the debugging object is interrupted, refreshing the page of the debugging object displayed at the debugging front end based on the determined page refreshing mode. Through the technical scheme, different refreshing modes are selected, the debugging front end and the debugging platform do not need to be restarted every time when the page is refreshed, and therefore debugging efficiency is improved.
Description
Technical Field
The present disclosure relates to computer communication termination, and in particular, to a program debugging method and apparatus, an electronic device, and a storage medium.
Background
Currently, mobile electronic devices, such as mobile phones, tablet computers, smart wearable devices, and the like, have been widely used in various fields such as communication, entertainment, education, and the like. The user may implement corresponding functions, e.g., fast applications, applets, etc., based on the application program on the mobile terminal.
Taking the fast application as an example, the fast application is a novel application form based on a mobile phone hardware platform, and a user can enjoy the performance experience of the native application without downloading and installing the fast application, namely, using the fast application on the spot. In the process of developing the quick application, a developer can write JS codes to realize the running of the quick application at multiple ends of an Android system, an IOS system, WebView and the like.
In the process of developing the fast application, a developer needs to check the operation effect of the fast application and check the correctness of the page, the style, the logic and the like of the fast application. In the debugging process, the fast application and the debugging front end need to be refreshed, and the debugging result needs to be checked. But the debugging platform and the debugging front end need to be restarted every time of refreshing, and the debugging efficiency is low.
Disclosure of Invention
The disclosure provides a program debugging method and device and a storage medium.
According to a first aspect of the embodiments of the present disclosure, there is provided a program debugging method, which is applied to a debugging platform, and includes:
in a debugging process aiming at a debugging object, receiving a page refreshing signal sent by a debugging front end, wherein the debugging object comprises: fast applications and/or applets;
interrupting the operation of the debugging object according to the page refreshing signal;
determining a page refreshing mode according to the page refreshing signal;
and after the operation of the debugging object is interrupted, refreshing the page of the debugging object displayed at the debugging front end based on the determined page refreshing mode.
In some embodiments, the determining a page refresh mode according to the refresh signal includes:
when the page refreshing signal is a restarting refreshing signal, determining that the page refreshing mode is that page refreshing is carried out through restarting of the debugging object;
and when the page refreshing signal is a hot loading page signal, determining that the page refreshing mode is to re-render the page of the debugging object.
In some embodiments, when the page refresh manner is a page refresh by restarting the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh manner includes:
according to the page refreshing signal, the debugging object is rerun to a target breakpoint and is suspended;
and refreshing the page of the debugging object displayed by the debugging front end after restarting based on the running result of the debugging object at the target breakpoint.
In some embodiments, when the page refresh mode is to re-render the page of the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh mode includes:
after the debugging front end and the debugging platform finish the initialization of the debugging object, the debugging platform re-renders the page of the debugging object and obtains re-rendered page data;
and sending the page data to the debugging object.
In some embodiments, the method further comprises:
interacting the synchronous information initialized by the debugging object with the debugging front end;
and determining whether the debugging front end and the debugging platform finish the initialization of the debugging object or not based on the synchronous information.
In some embodiments, the interacting with the debug front-end of the synchronization information for the initialization of the debug object includes:
receiving first-class synchronization information sent by the debugging front end after the debugging object is finished; if the debugging platform does not finish the initialization of the debugging object, the debugging platform initializes the debugging object according to the first type of synchronous information;
alternatively, the first and second electrodes may be,
and the debugging platform sends second-class synchronization information to the debugging front end after the debugging object is finished, wherein the second-class synchronization information is used for triggering the debugging object to initialize the debugging object.
In some embodiments, the method further comprises:
sending interruption information to the debugging front end when the debugging object runs to a target breakpoint in the debugging process;
the receiving a page refresh signal sent by a debugging front end in a debugging process aiming at a debugging object comprises the following steps:
and receiving a page refreshing signal sent by the debugging front end based on the interrupt information in the debugging process aiming at the debugging object.
In some embodiments, the method further comprises:
determining whether the debugging object is started for the first time in the debugging process according to the recorded starting times;
the interrupting the running of the debugging object according to the page refreshing signal comprises:
and when the debugging object is not started for the first time in the debugging process, interrupting the operation of the debugging object according to the page refreshing signal.
In some embodiments, the method further comprises:
and when the debugging object is started for the first time in the debugging process, continuing the operation of the debugging object in the debugging platform.
According to a second aspect of the embodiments of the present disclosure, there is provided a program debugging apparatus, which is applied to a debugging platform, including:
a receiving module, configured to receive a page refresh signal sent by a debug front end in a debugging process for a debug object, where the debug object includes: fast applications and/or applets;
the interruption module is used for interrupting the operation of the debugging object according to the page refreshing signal;
the determining module is used for determining a page refreshing mode according to the page refreshing signal;
and the refreshing module is used for refreshing the page of the debugging object displayed at the debugging front end based on the determined page refreshing mode after the operation of the debugging object is interrupted.
In some embodiments, the determining module comprises:
the first determining submodule is used for determining that the page refreshing mode is that the page refreshing is carried out through the restarting of the debugging object when the page refreshing signal is a restarting refreshing signal;
and the second determining submodule determines that the page refreshing mode is to re-render the page of the debugging object when the page refreshing signal is a hot loading page signal.
In some embodiments, when the page refresh manner is a page refresh by restarting the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh manner includes:
according to the page refreshing signal, the debugging object is rerun to a target breakpoint and is suspended;
and refreshing the page of the debugging object displayed by the debugging front end after restarting based on the running result of the debugging object at the target breakpoint.
In some embodiments, when the page refresh mode is to re-render the page of the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh mode includes:
after the debugging front end and the debugging platform finish the initialization of the debugging object, the debugging platform re-renders the page of the debugging object and obtains re-rendered page data;
and sending the page data to the debugging object.
In some embodiments, the apparatus further comprises:
interacting the synchronous information initialized by the debugging object with the debugging front end;
and determining whether the debugging front end and the debugging platform finish the initialization of the debugging object or not based on the synchronous information.
In some embodiments, the interacting with the debug front-end of the synchronization information for the initialization of the debug object includes:
receiving first-class synchronization information sent by the debugging front end after the debugging object is finished; if the debugging platform does not finish the initialization of the debugging object, the debugging platform initializes the debugging object according to the first type of synchronous information;
alternatively, the first and second electrodes may be,
and the debugging platform sends second-class synchronization information to the debugging front end after the debugging object is finished, wherein the second-class synchronization information is used for triggering the debugging object to initialize the debugging object.
In some embodiments, the apparatus further comprises:
sending interruption information to the debugging front end when the debugging object runs to a target breakpoint in the debugging process;
the receiving a page refresh signal sent by a debugging front end in a debugging process aiming at a debugging object comprises the following steps:
and receiving a page refreshing signal sent by the debugging front end based on the interrupt information in the debugging process aiming at the debugging object.
In some embodiments, the apparatus further comprises:
determining whether the debugging object is started for the first time in the debugging process according to the recorded starting times;
the interrupting the running of the debugging object according to the page refreshing signal comprises:
and when the debugging object is not started for the first time in the debugging process, interrupting the operation of the debugging object according to the page refreshing signal.
In some embodiments, the apparatus further comprises:
and when the debugging object is started for the first time in the debugging process, continuing the operation of the debugging object in the debugging platform.
According to a third aspect of the embodiments of the present disclosure, there is provided a program debugging apparatus including at least: a processor and a memory for storing executable instructions operable on the processor, wherein:
when the processor is used for executing the executable instructions, the executable instructions execute the steps in any program debugging method.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, implement the steps in any of the program debugging methods described above.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: through the technical scheme, the operation of the debugging object is interrupted when the page is required to be refreshed, different refreshing modes are provided, the refreshing mode required at present can be determined according to different conditions or requirements, the debugging front end and the debugging platform do not need to be restarted when the page is refreshed at each time, the debugging method can be suitable for more debugging scenes, and the page can be directly refreshed when the mode which is not restarted is selected to be refreshed, so that the debugging efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a flow diagram illustrating a method of program debugging in accordance with an illustrative embodiment;
FIG. 2 is a flow diagram illustrating another method of program debugging in accordance with an illustrative embodiment;
FIG. 3 is a flowchart illustrating yet another method of program debugging in accordance with an illustrative embodiment;
FIG. 4 is a flowchart illustrating yet another method of program debugging in accordance with an illustrative embodiment;
FIG. 5 is a flowchart illustrating yet another method of program debugging in accordance with an illustrative embodiment;
FIG. 6 is a flowchart illustrating yet another method of program debugging in accordance with an illustrative embodiment;
FIG. 7 is a block diagram illustrating an architecture of a program debugging apparatus in accordance with an illustrative embodiment;
fig. 8 is a block diagram illustrating a physical structure of a program debugging apparatus according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating a program debugging method applied to a debugging platform according to an exemplary embodiment, where the method includes the following steps:
step S101, in the debugging process aiming at a debugging object, receiving a page refreshing signal sent by a debugging front end, wherein the debugging object comprises: fast applications and/or applets;
step S102, interrupting the operation of the debugging object according to the page refreshing signal;
step S103, determining a page refreshing mode according to the page refreshing signal;
and step S104, after the operation of the debugging object is interrupted, refreshing the page of the debugging object displayed at the debugging front end based on the determined page refreshing mode.
The quick application is a novel application form based on a mobile phone hardware platform, and a user does not need to download and install the quick application, namely the quick application is used on demand. The fast application framework is deeply integrated in the operating system of the terminal equipment, seamless connection between user requirements and application services can be formed on the level of the operating system of the terminal equipment, a plurality of functions which can be used only in native applications can be realized conveniently in the fast application, and performance experience of the native applications can be enjoyed. The running of the fast application is executed by the fast application platform, the running result is displayed at the fast application front end, and the fast application front end can also be used for receiving the fast application running instruction. For example, if a click operation for a fast application is received based on the fast application front end, the process of specifically performing the click operation is performed by the fast application platform. Therefore, the process of actually running the fast application is mainly realized based on the fast application platform and the network architecture constructed by the fast application front end.
The small program is an application which can be used without downloading and installing, and can realize the functions of message notification, offline code scanning, public number association and the like, wherein the user can realize mutual skipping between the public number and the small program through the public number association.
Taking a fast application as an example, a fast application program can be divided into a component tree (DOM), a style (CSS), and a logic (JS code) from a data perspective; the program can be divided into a configuration file (manifest. json), a global file (App. js) and a page file (page) from the composition, and the program is packaged to form rpk packaged files, which are Application programs (apps) of fast applications.
In the process of developing the fast application, a set debugging tool can be adopted to debug the fast application. Taking the debugging of the fast application by using Chrome devtols (Chrome developer tool) as an example, Chrome devtols may be installed in a Personal Computer (PC) for debugging, run on the PC, and debug the fast application installed on the terminal device based on the browser front-end interface. The ChromeDevTools is a group of tools embedded in a Chromel browser and used for webpage making and debugging, and the terminal equipment comprises a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include: mobile phones, tablet computers, and the like. The non-mobile terminal may include: PC, etc. When the debugging object is a fast application, the debugging platform is the fast application platform, wherein the fast application platform and the fast application debugging kernel together form a fast application back end.
The fast application back end can be subdivided into a fast application platform and a debugging kernel. Wherein the fast application debugging kernel carries the function of fast application debugging. The running modes of the fast application are divided into a Release mode and a Debug mode. The former is an application program which is formally operated on the terminal equipment and has no debugging function; the latter is usually used as a debugging application program, and a debugging kernel is dynamically loaded when the fast application platform is loaded.
The debugging kernel is located at the position of a bridge in debugging, is arranged between the debugging front end and the fast application platform, mainly comprises functions of CSS, DOM, Debug, Console and the like, and can feed back the running data of the fast application to the debugging front end in real time for interaction with a user. From the perspective of the composition structure of the debugging kernel, the corresponding functions of each composition structure can be divided into: loading control of a debugging module, connection management of a debugging front end, analysis processing of a debugging protocol, a debugging module in a bridging v8(JavaScript engine, JS engine), and the like.
When the debugging object is an applet, the debugging platform is the applet platform, the debugging program operation is completed in the debugging process, and the debugging platform is used as an actual operation platform of the program code in actual use. The running of the applet is executed by the applet platform, and the running result is displayed at the front end of the applet, wherein the front end of the applet can also be used for receiving the applet running instruction. For example, if a front-end-based applet receives a click operation for the applet, the specific process of performing the click operation is performed by the applet platform. Therefore, the process of actually running the applet is mainly implemented based on the applet platform and the network architecture built by the applet front end.
In the debugging process, the debugging object can be normally started and operated, when the program runs to a target breakpoint or receives an instruction of a debugging front end, the current operation is interrupted, the states of functions, variables and data objects contained or generated in the current operation of the debugging object are kept, and then refreshing is carried out according to the instruction of the debugging front end.
The manner of refreshing the page may include restarting the debug object, re-rendering only the page of the debug object (i.e., hot-loading page), and so on. The method comprises the steps that an option of a refreshing mode can be provided at a debugging front end for a developer to select, based on the selected refreshing mode, the debugging front end sends a page refreshing signal to a debugging platform, and the debugging platform refreshes a debugging object based on the refreshing mode determined by the page refreshing signal to obtain a refreshed page.
By the method, different page refreshing modes can be provided for a developer to select according to actual debugging requirements. The debugging object does not need to be restarted every time of refreshing, but the refreshing mode required currently can be determined according to different conditions or requirements, and the method can be suitable for more debugging scenes.
In some embodiments, the determining a page refresh mode according to the refresh signal includes:
when the page refreshing signal is a restarting refreshing signal, determining that the page refreshing mode is that page refreshing is carried out through restarting of the debugging object;
and when the page refreshing signal is a hot loading page signal, determining that the page refreshing mode is to re-render the page of the debugging object.
Since both the debugging platform and the debugging front end are restarted when the debugging object is restarted, the state information of the current window is lost, and different pages may have logical association, data of other pages having logical association with the page needing to be refreshed may be lost when the debugging object is restarted. And the mode of hot loading the page is directly adopted, so that the debugging platform is not required to be restarted, the page is rendered again, all the pages can be kept consistent with the data before refreshing, and the data after refreshing is prevented from being lost. Therefore, when the data of other pages needs to be reserved, the page of the debugging object can be directly re-rendered in a hot loading mode and the like without restarting a debugging platform.
Of course, if the problem of data loss does not need to be considered and the platform needs to be restarted to update data, a restart mode may be selected to rerun the debugging object and restart the debugging platform. The debugging front end can also be restarted, so that the synchronization of the states and data of the debugging front end and the debugging back end is kept.
In some embodiments, when the page refresh manner is a page refresh by restarting the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh manner includes:
according to the page refreshing signal, the debugging object is rerun to a target breakpoint and is suspended;
and refreshing the page of the debugging object displayed by the debugging front end after restarting based on the running result of the debugging object at the target breakpoint.
To facilitate debugging, a developer may set breakpoints at specific locations of a program. The program code of the debugging object is executed to a certain position and stops, and the position is the breakpoint of the program. At this time, the functions, variables and data objects contained or generated by the current operation of the debugging object are kept static and unchanged in the current state, so that a developer can observe the debugging object conveniently and know the operation data and the operation logic conveniently.
In the debugging process, the program code can run to the target breakpoint and be suspended, and at the moment, the page can be refreshed. And after receiving a page refreshing signal, if the mode of restarting the debugging object is adopted, rerunning the code of the debugging object, and running to a target breakpoint for pausing again. At this time, when the debugging object is operated to the target breakpoint, the difference of the data, the state and the logic corresponding to the program when the debugging object is operated to the target breakpoint twice can be compared, so that the debugging of further analysis is facilitated. For example, when there is a difference in the results of two runs, whether the debugging operation is correct can be inferred from the difference. If the refreshed result is the effect which needs to be achieved after debugging, the debugging is successful; on the contrary, if the refreshed result does not reach the expected effect or other undesirable effects are generated, it indicates that the debugging has problems, and the debugging needs to be carried out again, the corresponding parameters are modified, and the next round of refreshing is carried out.
In some embodiments, when the page refresh mode is to re-render the page of the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh mode includes:
after the debugging front end and the debugging platform finish the initialization of the debugging object, the debugging platform re-renders the page of the debugging object and obtains re-rendered page data;
and sending the page data to the debugging object.
The initialization is to assign an initial value or a default value to a data variable of a debugging platform or a debugging front end, to complete corresponding preparation for program running and debugging, and to load a required instruction module. After the initialization is completed, the debugging front end and the debugging platform can perform effective data interaction, so that subsequent debugging work is performed.
Here, by adopting the hot loading page mode, both the debugging front end and the debugging platform can initialize the corresponding debugging object. And after the initialization is completed, the debugging platform re-renders the page to complete the refreshing of the page. And because the back end is not restarted, the refreshed page data needs to be sent to the debugging object, so that the data of the back end and the debugging object are consistent, the actual running condition of the debugging object is reflected at the debugging front end, the debugging operation of the debugging front end is correspondingly provided to the debugging object, and the debugging of the debugging object is completed.
In some embodiments, as shown in fig. 2, the method further comprises:
step S201, interacting the synchronization information initialized by the debugging object with the debugging front end;
step S202, based on the synchronous information, whether the debugging front end and the debugging platform finish the initialization of the debugging object is determined.
If a mode of re-rendering the page is adopted, namely, the page is hot-loaded, at the moment, the debugging platform does not need to be restarted, and the data of each page can be reserved, so that the problem of data loss after refreshing is solved. However, since the debug platform is not restarted when the page is hot loaded, the debug front end may not be synchronized with the initialization of the debug platform. When the two are synchronous, the states of the debugging platform and the connection module at the front end of the debugging are consistent; when the debug platform is restarted, but the debug front end is not restarted, the debug platform may lack some initialization actions for the debug module.
At this time, an instruction receiving module of the debugging platform can be manually triggered to respond to an instruction sent by the debugging front end; when the debugging front end is restarted and the debugging platform is not restarted, the page of the debugging front end is refreshed, but the response of the debugging platform really causes that part of debugging modules are not initialized, so that the instruction synchronization module of the debugging front end can be manually triggered, and the debugged instruction is sent to the debugging platform, so that the debugging platform completes the initialization synchronization.
That is to say, after the hot loading of the page is performed, whether the initialization of the debugging front end and the debugging platform is completed or not can be judged according to the synchronization information of the initialization of the debugging object and the debugging front end, so that the state synchronization of the debugging front end and the debugging platform is ensured after the page is refreshed.
In some embodiments, the interacting with the debug front-end of the synchronization information for the initialization of the debug object includes:
receiving first-class synchronization information sent by the debugging front end after the debugging object is finished; if the debugging platform does not finish the initialization of the debugging object, the debugging platform initializes the debugging object according to the first type of synchronous information;
alternatively, the first and second electrodes may be,
and the debugging platform sends second-class synchronization information to the debugging front end after the debugging object is finished, wherein the second-class synchronization information is used for triggering the debugging object to initialize the debugging object.
Here, when the debugging platform has not completed initialization and the debugging front end completes initialization, the debugging front end may send the initialized synchronization information to the debugging platform, so that the debugging platform further completes initialization; correspondingly, after the debugging platform completes initialization, corresponding second-class synchronization information can be sent to the debugging front end, so that the debugging front end sends a corresponding instruction to the debugging object based on the second-class synchronization information, the initialization of the debugging object is triggered, and the debugging front end and the debugging object are synchronized.
In some embodiments, as shown in fig. 3, the method further comprises:
step S301, sending interruption information to the debugging front end when the debugging object runs to a target breakpoint in the debugging process;
in step S101, the receiving a page refresh signal sent by a debug front end in the debugging process for the debug object includes:
step S302, in the debugging process aiming at the debugging object, receiving a page refreshing signal sent by the debugging front end based on the interrupt information.
In the method of the above embodiment, during debugging, the debugging object may be first run to the target breakpoint and be paused, and at this time, the interrupt information may be sent to the debugging front end. When the debugging front end receives the interrupt information, the current debugging object can be known to run to the interrupt point and be suspended. The debugging front end can obtain the functions, variables, objects and the like of the current program, and is convenient for developers to analyze and debug. When refreshing is needed, refreshing is carried out at the breakpoint, namely, refreshing information of the page is sent to the debugging platform based on the interruption information. The debugging platform can refresh the page according to the refresh information.
In some embodiments, as shown in fig. 4, the method further comprises:
step S401, determining whether the debugging object is started for the first time in the debugging process according to the recorded starting times;
in step S102, the interrupting the running of the debug object according to the page refresh signal includes:
step S402, when the debugging object is not started for the first time in the debugging process, the operation of the debugging object is interrupted according to the page refreshing signal.
For restarting the refresh of the debug object, the operation is substantially the same as starting the debug object for the first time. When a debugging object is started for the first time, data loading of a debugging platform and a debugging front end is required to be completed; and when the system is restarted, the system does not need to be loaded again, and the system is directly operated to the breakpoint to be suspended and then is subjected to subsequent debugging. Therefore, the debugging platform needs to distinguish whether the current boot is the first boot or the restart according to the recorded boot times. When the debugging platform has no started record, namely the starting times are zero, the debugging platform is started for the first time at present and does not need to respond to the refreshing instruction. And when the starting times recorded by the debugging platform are more than or equal to 1, the current starting is the restarting, the response to the refreshing instruction is needed, namely the operation of the debugging object is interrupted according to the page refreshing signal, and the subsequent debugging and refreshing operation is carried out.
In some embodiments, the method further comprises:
step S403, when the debugging object is started for the first time in the debugging process, continuing the operation of the debugging object in the debugging platform.
When the starting times recorded by the debugging platform is zero, namely the debugging platform is started for the first time currently, the debugging object is continuously operated without responding to the page refreshing signal, and the loading of the debugging platform and the debugging front end is finished, so that the data integrity of the debugging front end and the debugging rear end is ensured.
Embodiments of the present disclosure also provide the following examples:
in some embodiments, developer code is directly processed into an H5 (5 th generation html standard specification) file through a compiling tool, rendered by a browser, debugged in an H5 page according to a webpage debugging method, and refreshed at a breakpoint position to reload the page.
The method comprises the following steps:
step S11, converting the fast application app into an H5 page through a compiling tool, and establishing a Web Server (Web Server) locally;
step S12, the debugging front end accesses the H5 page through a URL (Uniform Resource Locator), and the fast application renders through a browser.
Step S13, setting a breakpoint at the front end of the debugging, and pausing the execution of the browser at the back end to the breakpoint position.
And step S14, after the debugging front end is refreshed, immediately interrupting the execution of the page to the residual codes of the current page, and re-executing the current page to the breakpoint position.
In the above method, the fast application is converted into the H5 page for simulation and then debugging, and the refresh flow is shown in fig. 5, but the fast application itself is not debugged substantially. When the page is refreshed, the data of other pages can be lost due to the restart of a JS (JavaScript) engine.
When refreshing a page, the refresh logic is determined by the browser backend and cannot be customized, for example, when refreshing a breakpoint, the result desired by a developer may be: either the fast application is reloaded or the page is reloaded, which the above approach does not provide.
In the embodiment of the disclosure, before starting debugging, a developer may set to select a hot loading page or restart an application during refreshing, and may select different restart modes according to the setting during restarting. When the breakpoint position executes refreshing, if the developer sets the hot loading page, the JS engine can be enabled not to restart, and the page is re-rendered, so that all the logically associated pages are consistent with the data before refreshing.
In the embodiment of the present disclosure, a developer needs to complete the compiling of the fast application program at the PC side, and reset the application or hot load the current page when setting the page refresh. After the debugging of the fast application is started, a breakpoint is set through the debugging front end, and the fast application is executed to the breakpoint. The method comprises the following steps:
and step S21, the fast application back end executes the breakpoint to the designated position and pauses, the breakpoint information is reported to the debugging front end, and the developer can click the refresh button of the debugging front end at the moment.
And step S22, the debugging kernel acquires the refresh command through the protocol processing module and sends the refresh command to the JS engine.
And step S23, the debugging kernel needs to acquire the information of the JS engine, and if the debugging kernel is started for the first time at present, the loading logic for completing the fast application platform is sent to the JS engine.
And step S24, if the current page is not started for the first time, immediately interrupting the residual JS codes of the current page by the debugging kernel, and sending an instruction of application restart or hot loading of the current page to the developer according to the debugging options set by the developer.
And step S25, loading the page after the fast application is restarted, and pausing at the first breakpoint.
Step S26, after refreshing, the debugging kernel synchronously operates the JS engine and the debugging front end to ensure that the JS engine and the debugging front end all complete the initialization of the debugging function
Through the above steps, one breakpoint refresh operation is completed, as shown in the flow chart in fig. 6. In the scheme, two options of breakpoint refreshing are provided for developers, namely restarting programs of fast applications or hot loading current pages. After the page is hot loaded, the JS engine state can be kept inconvenient, so that other page contents with logic association are reserved, and the continuous debugging of a developer is facilitated.
When the breakpoint is refreshed, all JS codes can be executed and restarted, but the time consumption is long, and efficient debugging is not facilitated. Therefore, the execution of the remaining JS code of the current page needs to be interrupted before the restart.
Because the fast application is different from the webpage, the JS engine of the webpage can always keep consistent with the debugging front end, including simultaneously opening, closing, restarting and the like, and the situation of the fast application is different:
when the mode of refreshing the page is to restart the fast application, the JS engine of the fast application and the debugging front end are both restarted, and the state of the JS engine is kept consistent with that of the debugging front end at the moment. The mode of refreshing the page is that when the page is loaded in a hot mode, the JS engine state and the debugging front end are out of synchronization. The following three cases are included:
the first and synchronous states are that the JS engine is consistent with the state of the connection module at the front end of the debugging.
Secondly, the JS engine is restarted, but the debugging front end is not restarted, so that the JS engine lacks part of the initialization action of the debugging module. At this time, Runtime of the JS engine needs to be triggered manually to respond to the JS instruction sent by the debugging front end.
And thirdly, restarting the debugging front end, but not restarting the JS engine, refreshing a page of the debugging front end at the moment, but lacking the correspondence of the JS engine, so that part of debugging modules are not initialized, and at the moment, manually triggering a Runtime module of the debugging front end to realize instruction interaction with the JS engine.
Since the first start and refresh, i.e., restart, behavior of the debug front-end is similar, the debug kernel needs to make a decision on the refresh behavior. If the current refresh instruction is the first refresh, the first loading of the debugging front end is actually performed, and at this time, the fast application does not need to be restarted, but the operation can be continued until the loading of the debugging front end is completed. And when the refresh command is the second refresh or the third refresh, the fast application or the hot-loaded page can be interrupted and restarted at the breakpoint in response to the refresh command.
Fig. 7 is a block diagram illustrating an architecture of a program debugging apparatus 700 according to an example embodiment. Referring to fig. 7, the apparatus 700 is applied to a debugging platform, and the apparatus 700 includes: a receiving module 701, an interrupting module 702, a determining module 703 and a refreshing module 704, wherein:
a receiving module 701, configured to receive a page refresh signal sent by a debug front end in a debugging process for a debug object, where the debug object includes: fast applications and/or applets;
an interruption module 702, configured to interrupt the running of the debug object according to the page refresh signal;
a determining module 703, configured to determine a page refresh mode according to the page refresh signal;
a refreshing module 704, configured to refresh, based on the determined page refresh manner, a page of the debug object displayed at the debug front end after the operation of the debug object is interrupted.
In some embodiments, the determining module comprises:
the first determining submodule is used for determining that the page refreshing mode is that the page refreshing is carried out through the restarting of the debugging object when the page refreshing signal is a restarting refreshing signal;
and the second determining submodule determines that the page refreshing mode is to re-render the page of the debugging object when the page refreshing signal is a hot loading page signal.
In some embodiments, when the page refresh manner is a page refresh by restarting the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh manner includes:
according to the page refreshing signal, the debugging object is rerun to a target breakpoint and is suspended;
and refreshing the page of the debugging object displayed by the debugging front end after restarting based on the running result of the debugging object at the target breakpoint.
In some embodiments, when the page refresh mode is to re-render the page of the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh mode includes:
after the debugging front end and the debugging platform finish the initialization of the debugging object, the debugging platform re-renders the page of the debugging object and obtains re-rendered page data;
and sending the page data to the debugging object.
In some embodiments, the apparatus further comprises:
interacting the synchronous information initialized by the debugging object with the debugging front end;
and determining whether the debugging front end and the debugging platform finish the initialization of the debugging object or not based on the synchronous information.
In some embodiments, the interacting with the debug front-end of the synchronization information for the initialization of the debug object includes:
receiving first-class synchronization information sent by the debugging front end after the debugging object is finished; if the debugging platform does not finish the initialization of the debugging object, the debugging platform initializes the debugging object according to the first type of synchronous information;
alternatively, the first and second electrodes may be,
and the debugging platform sends second-class synchronization information to the debugging front end after the debugging object is finished, wherein the second-class synchronization information is used for triggering the debugging object to initialize the debugging object.
In some embodiments, the apparatus further comprises:
sending interruption information to the debugging front end when the debugging object runs to a target breakpoint in the debugging process;
the receiving a page refresh signal sent by a debugging front end in a debugging process aiming at a debugging object comprises the following steps:
and receiving a page refreshing signal sent by the debugging front end based on the interrupt information in the debugging process aiming at the debugging object.
In some embodiments, the apparatus further comprises:
determining whether the debugging object is started for the first time in the debugging process according to the recorded starting times;
the interrupting the running of the debugging object according to the page refreshing signal comprises:
and when the debugging object is not started for the first time in the debugging process, interrupting the operation of the debugging object according to the page refreshing signal.
In some embodiments, the apparatus further comprises:
and when the debugging object is started for the first time in the debugging process, continuing the operation of the debugging object in the debugging platform.
The above description of the apparatus embodiments, similar to the above description of the method embodiments, has similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus of the present application, reference is made to the description of the embodiments of the method of the present application for understanding.
Fig. 8 is a block diagram illustrating a physical structure of a program debugging apparatus 800 according to an exemplary embodiment. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and so forth.
Referring to fig. 8, the apparatus 800 may include one or more of the following components: a processing component 801, a memory 802, a power component 803, a multimedia component 804, an audio component 805, an input/output (I/O) interface 806, a sensor component 807, and a communication component 808.
The processing component 801 generally operates the apparatus 800 as a whole, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 801 may include one or more processors 810 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 801 may also include one or more modules that facilitate interaction between the processing component 801 and other components. For example, the processing component 801 may include a multimedia module to facilitate interaction between the multimedia component 804 and the processing component 801.
The memory 810 is configured to store various types of data to support operations at the apparatus 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 802 may be implemented by any type or combination of volatile or non-volatile storage devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The power supply component 803 provides power to the various components of the device 800. The power supply component 803 may include: a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 800.
The multimedia component 804 includes a screen that provides an output interface between the device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 804 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and/or rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 805 is configured to output and/or input audio signals. For example, the audio component 805 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 810 or transmitted via the communication component 808. In some embodiments, the audio component 805 also includes a speaker for outputting audio signals.
The I/O interface 806 provides an interface between the processing component 801 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 807 includes one or more sensors for providing various aspects of condition assessment for the apparatus 800. For example, the sensor component 807 may detect the open/closed state of the device 800, the relative positioning of components such as a display and keypad of the device 800, the sensor component 807 may also detect a change in position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, orientation or acceleration/deceleration of the device 800, and a change in temperature of the device 800. Sensor assembly 807 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 807 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 807 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 808 is configured to facilitate communications between the apparatus 800 and other devices in a wired or wireless manner. The apparatus 800 may access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 808 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 808 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, or other technologies.
In an exemplary embodiment, the apparatus 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 802 comprising instructions, executable by the processor 810 of the device 800 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
A non-transitory computer readable storage medium, wherein instructions of the storage medium, when executed by a processor of a mobile terminal, enable the mobile terminal to perform the steps of any one of the program debugging methods provided in the above embodiments.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (20)
1. A program debugging method is applied to a debugging platform and comprises the following steps:
in a debugging process aiming at a debugging object, receiving a page refreshing signal sent by a debugging front end, wherein the debugging object comprises: fast applications and/or applets;
interrupting the operation of the debugging object according to the page refreshing signal;
determining a page refreshing mode according to the page refreshing signal;
and after the operation of the debugging object is interrupted, refreshing the page of the debugging object displayed at the debugging front end based on the determined page refreshing mode.
2. The method of claim 1, wherein determining a page refresh mode according to the refresh signal comprises:
when the page refreshing signal is a restarting refreshing signal, determining that the page refreshing mode is that page refreshing is carried out through restarting of the debugging object;
and when the page refreshing signal is a hot loading page signal, determining that the page refreshing mode is to re-render the page of the debugging object.
3. The method according to claim 2, wherein when the page refresh mode is a page refresh by restarting the debug object, the refreshing the page of the debug object displayed by the debug front end based on the determined page refresh mode includes:
according to the page refreshing signal, the debugging object is rerun to a target breakpoint and is suspended;
and refreshing the page of the debugging object displayed by the debugging front end after restarting based on the running result of the debugging object at the target breakpoint.
4. The method of claim 2, wherein when the page refresh mode is re-rendering the page of the debug object, the refreshing the page of the debug object displayed by the debug front based on the determined page refresh mode comprises:
after the debugging front end and the debugging platform finish the initialization of the debugging object, the debugging platform re-renders the page of the debugging object and obtains re-rendered page data;
and sending the page data to the debugging object.
5. The method of claim 4, further comprising:
interacting the synchronous information initialized by the debugging object with the debugging front end;
and determining whether the debugging front end and the debugging platform finish the initialization of the debugging object or not based on the synchronous information.
6. The method of claim 5, wherein the interacting with the debug front end of the synchronization information for the initialization of the debug object comprises:
receiving first-class synchronization information sent by the debugging front end after the debugging object is finished; if the debugging platform does not finish the initialization of the debugging object, the debugging platform initializes the debugging object according to the first type of synchronous information;
alternatively, the first and second electrodes may be,
and the debugging platform sends second-class synchronization information to the debugging front end after the debugging object is finished, wherein the second-class synchronization information is used for triggering the debugging object to initialize the debugging object.
7. The method of any of claims 1 to 6, further comprising:
sending interruption information to the debugging front end when the debugging object runs to a target breakpoint in the debugging process;
the receiving a page refresh signal sent by a debugging front end in a debugging process aiming at a debugging object comprises the following steps:
and receiving a page refreshing signal sent by the debugging front end based on the interrupt information in the debugging process aiming at the debugging object.
8. The method of any of claims 1 to 6, further comprising:
determining whether the debugging object is started for the first time in the debugging process according to the recorded starting times;
the interrupting the running of the debugging object according to the page refreshing signal comprises:
and when the debugging object is not started for the first time in the debugging process, interrupting the operation of the debugging object according to the page refreshing signal.
9. The method of claim 8, further comprising:
and when the debugging object is started for the first time in the debugging process, continuing the operation of the debugging object in the debugging platform.
10. A program debugging device, applied to a debugging platform, comprising:
a receiving module, configured to receive a page refresh signal sent by a debug front end in a debugging process for a debug object, where the debug object includes: fast applications and/or applets;
the interruption module is used for interrupting the operation of the debugging object according to the page refreshing signal;
the determining module is used for determining a page refreshing mode according to the page refreshing signal;
and the refreshing module is used for refreshing the page of the debugging object displayed at the debugging front end based on the determined page refreshing mode after the operation of the debugging object is interrupted.
11. The apparatus of claim 10, wherein the determining module comprises:
the first determining submodule is used for determining that the page refreshing mode is that the page refreshing is carried out through the restarting of the debugging object when the page refreshing signal is a restarting refreshing signal;
and the second determining submodule determines that the page refreshing mode is to re-render the page of the debugging object when the page refreshing signal is a hot loading page signal.
12. The apparatus of claim 11, wherein when the page refresh mode is a page refresh by a reboot of the debug object, the refreshing the page of the debug object displayed by the debug front based on the determined page refresh mode comprises:
according to the page refreshing signal, the debugging object is rerun to a target breakpoint and is suspended;
and refreshing the page of the debugging object displayed by the debugging front end after restarting based on the running result of the debugging object at the target breakpoint.
13. The apparatus of claim 11, wherein when the page refresh mode is re-rendering the page of the debug object, the refreshing the page of the debug object displayed by the debug front based on the determined page refresh mode comprises:
after the debugging front end and the debugging platform finish the initialization of the debugging object, the debugging platform re-renders the page of the debugging object and obtains re-rendered page data;
and sending the page data to the debugging object.
14. The apparatus of claim 13, further comprising:
interacting the synchronous information initialized by the debugging object with the debugging front end;
and determining whether the debugging front end and the debugging platform finish the initialization of the debugging object or not based on the synchronous information.
15. The apparatus of claim 14, wherein the interacting with the debug front end of the synchronization information for the initialization of the debug object comprises:
receiving first-class synchronization information sent by the debugging front end after the debugging object is finished; if the debugging platform does not finish the initialization of the debugging object, the debugging platform initializes the debugging object according to the first type of synchronous information;
alternatively, the first and second electrodes may be,
and the debugging platform sends second-class synchronization information to the debugging front end after the debugging object is finished, wherein the second-class synchronization information is used for triggering the debugging object to initialize the debugging object.
16. The apparatus of any one of claims 10 to 15, further comprising:
sending interruption information to the debugging front end when the debugging object runs to a target breakpoint in the debugging process;
the receiving a page refresh signal sent by a debugging front end in a debugging process aiming at a debugging object comprises the following steps:
and receiving a page refreshing signal sent by the debugging front end based on the interrupt information in the debugging process aiming at the debugging object.
17. The apparatus of any one of claims 10 to 15, further comprising:
determining whether the debugging object is started for the first time in the debugging process according to the recorded starting times;
the interrupting the running of the debugging object according to the page refreshing signal comprises:
and when the debugging object is not started for the first time in the debugging process, interrupting the operation of the debugging object according to the page refreshing signal.
18. The apparatus of claim 17, further comprising:
and when the debugging object is started for the first time in the debugging process, continuing the operation of the debugging object in the debugging platform.
19. A program debugging apparatus, comprising at least: a processor and a memory for storing executable instructions operable on the processor, wherein:
the processor is configured to execute the executable instructions, and the executable instructions perform the steps of the program debugging method provided in any one of claims 1 to 9.
20. A non-transitory computer-readable storage medium, wherein computer-executable instructions are stored in the computer-readable storage medium, and when executed by a processor, implement the steps in the program debugging method provided in any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910963097.9A CN110781080B (en) | 2019-10-11 | 2019-10-11 | Program debugging method and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910963097.9A CN110781080B (en) | 2019-10-11 | 2019-10-11 | Program debugging method and device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110781080A true CN110781080A (en) | 2020-02-11 |
| CN110781080B CN110781080B (en) | 2023-06-30 |
Family
ID=69385137
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910963097.9A Active CN110781080B (en) | 2019-10-11 | 2019-10-11 | Program debugging method and device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110781080B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111338939A (en) * | 2020-02-21 | 2020-06-26 | 网易传媒科技（北京）有限公司 | Application program debugging method, medium, device and computing equipment |
| CN111338961A (en) * | 2020-02-28 | 2020-06-26 | 北京小米移动软件有限公司 | Application debugging method and device, electronic equipment and storage medium |
| CN114035855A (en) * | 2021-09-30 | 2022-02-11 | 鸣芯信息科技(上海)有限公司 | Firmware debugging method, device, terminal and storage medium |
| EP4027246A4 (en) * | 2020-11-16 | 2022-09-21 | Baidu Online Network Technology (Beijing) Co., Ltd. | Method and apparatus for debugging applet, electronic device and storage medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020085029A1 (en) * | 2000-12-29 | 2002-07-04 | Jamal Ghani | Computer based interactive collaboration system architecture |
| US20080052682A1 (en) * | 2006-08-25 | 2008-02-28 | Satoshi Nagamine | Debug device and debug processing method |
| CN102902618A (en) * | 2011-07-28 | 2013-01-30 | 华为技术有限公司 | Method and device for developing and debugging application programs of mobile equipment |
| CN103064750A (en) * | 2012-12-25 | 2013-04-24 | 北京奇虎科技有限公司 | Interrupt restoring method and device for browser control |
| CN104035945A (en) * | 2013-03-08 | 2014-09-10 | 腾讯科技（深圳）有限公司 | Page refreshing method and page refreshing device of browser |
| CN108280027A (en) * | 2018-02-08 | 2018-07-13 | 金蝶软件（中国）有限公司 | A kind of concurrently debugging rendering intent and device of script |
| CN109032917A (en) * | 2017-06-09 | 2018-12-18 | 北京金山云网络技术有限公司 | Page adjustment method and system, mobile terminal and computer end |
| CN109542463A (en) * | 2018-10-26 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Compiling file packet transmission method, device, computer equipment and storage medium |
| CN109800173A (en) * | 2019-01-28 | 2019-05-24 | 腾讯科技（深圳）有限公司 | Program debugging method, device and storage medium |
| CN110032512A (en) * | 2019-03-28 | 2019-07-19 | 腾讯科技（深圳）有限公司 | A kind of adjustment method of small routine, relevant device and terminal |
-
2019
- 2019-10-11 CN CN201910963097.9A patent/CN110781080B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020085029A1 (en) * | 2000-12-29 | 2002-07-04 | Jamal Ghani | Computer based interactive collaboration system architecture |
| US20080052682A1 (en) * | 2006-08-25 | 2008-02-28 | Satoshi Nagamine | Debug device and debug processing method |
| CN102902618A (en) * | 2011-07-28 | 2013-01-30 | 华为技术有限公司 | Method and device for developing and debugging application programs of mobile equipment |
| CN103064750A (en) * | 2012-12-25 | 2013-04-24 | 北京奇虎科技有限公司 | Interrupt restoring method and device for browser control |
| CN104035945A (en) * | 2013-03-08 | 2014-09-10 | 腾讯科技（深圳）有限公司 | Page refreshing method and page refreshing device of browser |
| CN109032917A (en) * | 2017-06-09 | 2018-12-18 | 北京金山云网络技术有限公司 | Page adjustment method and system, mobile terminal and computer end |
| CN108280027A (en) * | 2018-02-08 | 2018-07-13 | 金蝶软件（中国）有限公司 | A kind of concurrently debugging rendering intent and device of script |
| CN109542463A (en) * | 2018-10-26 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Compiling file packet transmission method, device, computer equipment and storage medium |
| CN109800173A (en) * | 2019-01-28 | 2019-05-24 | 腾讯科技（深圳）有限公司 | Program debugging method, device and storage medium |
| CN110032512A (en) * | 2019-03-28 | 2019-07-19 | 腾讯科技（深圳）有限公司 | A kind of adjustment method of small routine, relevant device and terminal |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111338939A (en) * | 2020-02-21 | 2020-06-26 | 网易传媒科技（北京）有限公司 | Application program debugging method, medium, device and computing equipment |
| CN111338961A (en) * | 2020-02-28 | 2020-06-26 | 北京小米移动软件有限公司 | Application debugging method and device, electronic equipment and storage medium |
| CN111338961B (en) * | 2020-02-28 | 2023-10-20 | 北京小米移动软件有限公司 | Application debugging method and device, electronic equipment and storage medium |
| EP4027246A4 (en) * | 2020-11-16 | 2022-09-21 | Baidu Online Network Technology (Beijing) Co., Ltd. | Method and apparatus for debugging applet, electronic device and storage medium |
| CN114035855A (en) * | 2021-09-30 | 2022-02-11 | 鸣芯信息科技(上海)有限公司 | Firmware debugging method, device, terminal and storage medium |
| CN114035855B (en) * | 2021-09-30 | 2023-10-27 | 鸣芯信息科技(上海)有限公司 | Firmware debugging method, device, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110781080B (en) | 2023-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110781080B (en) | Program debugging method and device and storage medium | |
| CN109032606B (en) | Native application compiling method and device and terminal | |
| CN111221559B (en) | Application updating method, device, storage medium, terminal and server | |
| CN111273899B (en) | Code processing method, device, electronic equipment and storage medium | |
| CN105808305B (en) | Static resource loading method and device | |
| CN109117144B (en) | Page processing method, device, terminal and storage medium | |
| CN111427622B (en) | Execution method and device of script codes in application program | |
| CN110795354A (en) | Information processing method, device and storage medium | |
| CN107562500B (en) | Debugging device, method and equipment | |
| CN107911482B (en) | Target application opening method and device | |
| CN106612149B (en) | Radio frequency circuit testing method, device and system and mobile terminal | |
| CN109901886B (en) | Page language switching method, system, device and computer readable storage medium | |
| CN110851370B (en) | Program testing method and device and storage medium | |
| CN110221813B (en) | Application data connection establishment method and device, storage medium and electronic equipment | |
| CN109976872B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111596980B (en) | Information processing method and device | |
| CN113778687B (en) | Memory allocation information processing method and device, electronic equipment and storage medium | |
| CN113141530B (en) | Remote control interaction based method and device, electronic equipment and storage medium | |
| CN111338961B (en) | Application debugging method and device, electronic equipment and storage medium | |
| CN110569037B (en) | Data writing method and device | |
| CN110908904A (en) | Method and device for debugging fast application and electronic equipment | |
| CN112083981A (en) | Method and device for creating page view component | |
| CN109726129B (en) | Code segment operation method, device, terminal and storage medium | |
| CN114860242A (en) | Compiling method, compiling device and storage medium | |
| CN112181406A (en) | Rendering engine sharing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |