CN110795354A - Information processing method, device and storage medium - Google Patents
Information processing method, device and storage medium Download PDFInfo
- Publication number
- CN110795354A CN110795354A CN201911042752.3A CN201911042752A CN110795354A CN 110795354 A CN110795354 A CN 110795354A CN 201911042752 A CN201911042752 A CN 201911042752A CN 110795354 A CN110795354 A CN 110795354A
- Authority
- CN
- China
- Prior art keywords
- debugging
- information
- target
- runtime data
- breakpoint
- 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.)
- Pending
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
-
- 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/3664—Environments for testing or debugging software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The present disclosure relates to an information processing method, an information processing apparatus, and a storage medium, where the method is applied to a debug object platform, and includes: the method comprises the steps of running a debugging object and obtaining the running data of the debugging object, wherein the debugging object comprises: fast applications and/or applets; receiving debugging information; executing debugging operation corresponding to the debugging information based on the debugging information; and obtaining a debugging result based on the debugging operation and the runtime data. In the present disclosure, the network architecture related to the debugging environment is the same as the network architecture in actual operation; the data interaction process involved in debugging is the same as that of the actual running fast application. The obtained debugging data is highly similar to the data of the actual operation of the debugging object, so that the difference between the debugging data and the data obtained by the actual operation of the fast application can be reduced, and the efficiency of the fast application and the accuracy of the debugging result are improved.
Description
Technical Field
The present disclosure relates to the field of computer communications, and in particular, to an information processing method, an information processing apparatus, 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 running effect of the fast application and check the correctness of the page, the style, the logic and the like of the fast application, and the specific mode is that in the process of packaging the fast application according to a set flow and installing and checking the running effect of a program, when the effect is inconsistent with the expectation, the fast application needs to be modified, and then the packaging, the installation and the checking of the running effect of the program are carried out again, so that the debugging efficiency is low.
Disclosure of Invention
The present disclosure provides an information processing method, apparatus, and storage medium.
According to a first aspect of the embodiments of the present disclosure, there is provided an information processing method, which is applied to a debug object platform, and includes:
the method comprises the steps of running a debugging object and obtaining the running data of the debugging object, wherein the debugging object comprises: fast applications and/or applets;
receiving debugging information;
executing debugging operation corresponding to the debugging information based on the debugging information;
and obtaining a debugging result based on the debugging operation and the runtime data.
Optionally, the obtaining a debugging result based on the debugging operation and the runtime data includes:
when the debugging object runs to a target breakpoint based on the debugging operation, acquiring target runtime data acquired when the debugging object runs to the target breakpoint;
and obtaining a debugging result based on the target runtime data.
Optionally, obtaining a debugging result based on the target runtime data includes:
when the target runtime data is acquired, storing the target runtime data into a message processing queue;
and sequentially processing the target runtime data in the message processing queue to obtain the debugging result.
Optionally, the method further includes:
detecting whether target runtime data to be processed exist in the message processing queue;
and if the target runtime data to be processed does not exist in the message processing queue, continuing to receive the debugging information until a quit debugging signal is received.
Optionally, the executing, based on the debugging information, a debugging operation corresponding to the debugging information includes:
acquiring the position and the running instruction of the target breakpoint from the debugging information;
and executing corresponding debugging operation based on the running instruction, and indicating the debugging object to run to the target breakpoint.
According to a second aspect of the embodiments of the present disclosure, there is provided an information processing apparatus including:
a first obtaining module configured to run a debug object and obtain runtime data of the debug object, wherein the debug object includes: fast applications and/or applets;
a first receiving module configured to receive debugging information;
the execution module is configured to execute debugging operation corresponding to the debugging information based on the debugging information;
and the second acquisition module is configured to obtain a debugging result based on the debugging operation and the runtime data.
Optionally, the second obtaining module includes:
the first obtaining sub-module is configured to obtain target runtime data obtained when the debugging object runs to a target breakpoint based on the debugging operation when the debugging object runs to the target breakpoint;
and the second obtaining submodule is configured to obtain a debugging result based on the target runtime data.
Optionally, the second obtaining sub-module is further configured to:
when the target runtime data is acquired, storing the target runtime data into a message processing queue;
and sequentially processing the target runtime data in the message processing queue to obtain the debugging result.
Optionally, the apparatus further comprises:
a detection module configured to detect whether there is target runtime data to be processed in the message processing queue;
and the second receiving module is configured to continue to receive the debugging information until receiving the quit debugging signal if the target runtime data to be processed does not exist in the message processing queue.
Optionally, the execution module includes:
the third obtaining submodule is configured to obtain the position and the running instruction of the target breakpoint from the debugging information;
and the control submodule is configured to execute corresponding debugging operation based on the running instruction and indicate the debugging object to run to the target breakpoint.
According to a third aspect of the embodiments of the present disclosure, there is provided an information processing apparatus including:
a processor;
a memory configured to store processor-executable instructions;
wherein the processor is configured to: the steps in the information processing method of the first aspect described above are implemented when executed.
According to a fourth aspect of embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium having instructions therein, which when executed by a processor of an information processing apparatus, enable the apparatus to perform the information processing method of the first aspect described above.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
according to the technical scheme, the debugging object is debugged based on the debugging object platform by adding the debugging function to the debugging object platform, so that the debugging object does not need to be debugged after being converted into a webpage with a set format, the debugging of the fast application or the small program is realized directly through data interaction between the debugging object platform and the debugging front end, and the network architecture related to the whole debugging environment is the same as the network architecture of the actual running fast application; the process of data interaction involved in debugging is also the same as that of data interaction in the actual running of fast applications. Therefore, the obtained debugging data is highly similar to the data of the actual operation of the debugging object, the difference between the debugging data and the data obtained by the actual operation of the fast application can be reduced, and the efficiency of the fast application and the accuracy of the debugging result are 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 present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a first flowchart illustrating an information processing method according to an example embodiment.
FIG. 2 is a flow chart diagram two illustrating an information processing method according to an exemplary embodiment.
Fig. 3 is a flowchart three illustrating an information processing method according to an exemplary embodiment.
Fig. 4 is a flow chart diagram four illustrating an information processing method according to an example embodiment.
Fig. 5 is a block diagram illustrating an information processing apparatus according to an example embodiment.
Fig. 6 is a block diagram showing a hardware configuration of an information processing 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 implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating an information processing method according to an exemplary embodiment, where the method is applied to a debug object platform, as shown in fig. 1, and includes the following steps:
in step 101, the debug object platform runs a debug object and obtains run-time data of the debug object, where the debug object includes: fast applications and/or applets;
in step 102, the debugging object platform receives debugging information;
in step 103, the debug object platform executes a debug operation corresponding to the debug information based on the debug information;
in step 104, the debug object platform obtains a debug result based on the debug operation and the runtime data.
Here, before the debug object is run, a debug function for the debug object may be started based on the debug object platform, and a start signal may be sent to the debug front end, and after the debug front end receives the start signal, debug information may be sent to the debug object platform based on the start signal. Wherein the debug object may be: and the program object is operated by the cloud, displays the operation result on the terminal and receives the control instruction from the terminal. The program object may include: fast applications and/or applets.
Here, the fast application is a new application form based on a mobile phone hardware platform, and a user does not need to download and install the fast application, namely, the fast 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 object platform is the fast application platform, wherein the fast application platform and the fast application debugging kernel can jointly form a fast application back end. Taking the terminal device as a mobile phone as an example, the fast application back end can be run on the hardware of the mobile phone and communicate with other terminal devices through a data transmission protocol.
Here, the fast application backend may 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.
And when the debugging object is the applet, the debugging object platform is the applet platform, wherein the operation of the applet is executed by the applet platform, and the operation 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 operation 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 embodiment of the present disclosure, a debugging function for a debugging object may be started based on a debugging object platform, and a start signal may be sent to a debugging front end. Taking the case that the debugging object is a fast application, the debugging function for the fast application installed on the terminal device can be started based on the fast application platform, and a start signal is sent to the debugging front end running on the PC, so that the debugging front end can determine corresponding debugging information based on the start signal and send the debugging information to the fast application platform. The debugging front end can be a browser front end.
After the fast application platform starts the debugging function for the fast application, the fast application can be run based on the fast application platform, and the run-time data of the fast application can be acquired. Wherein the runtime data can be generated based on an operation input by a user via a display interface of the fast application.
For example, if the function of a setting control displayed on the display interface of the fast application needs to be debugged, the user may click the control on the display interface, and the related data generated based on clicking the control may be used as the runtime data of the fast application. The relevant data may include: based on the parameters of the operating system called by clicking the control and the data directly obtained by clicking the setting control, for example, if the setting control is a login control for logging in, the data related to logging in may be used as runtime data.
In the embodiment of the present disclosure, after the runtime data of the debug object is obtained, the debug object platform may execute the debug operation corresponding to the debug information based on the debug information received from the debug front end, and obtain the debug result based on the debug operation and the runtime data. The debugging object is debugged based on the debugging object platform by adding a debugging function on the debugging object platform, so that the debugging object does not need to be debugged after being converted into a webpage with a set format, the debugging of the fast application or the small program is realized directly through data interaction between the debugging object platform and a debugging front end, and a network architecture related to the whole debugging environment is the same as that of the actual running fast application; the process of data interaction involved in debugging is also the same as that of data interaction in the actual running of fast applications. Therefore, the obtained debugging data is highly similar to the data of the actual operation of the debugging object, the difference between the debugging data and the data obtained by the actual operation of the fast application can be reduced, and the efficiency of the fast application and the accuracy of the debugging result are improved.
In other optional embodiments, the debug information includes at least breakpoint processing information;
based on the debug information, performing a debug operation corresponding to the debug information, including at least one of:
setting a target breakpoint based on the breakpoint processing information;
exiting the target breakpoint based on the breakpoint processing information;
running the debugging object to a target breakpoint based on the breakpoint processing information;
and canceling the target breakpoint based on the breakpoint processing information.
Here, a breakpoint is one of functions of a debugger, and a breakpoint is a signal for notifying the debugger to temporarily suspend program execution at a certain point. A mode when execution is suspended at some breakpoint is referred to as a program being in interrupt mode.
Wherein, based on breakpoint processing information, setting a target breakpoint, includes: acquiring a breakpoint position from the breakpoint processing information, and setting a target breakpoint at the breakpoint position;
based on the breakpoint processing information, exiting the target breakpoint includes: acquiring an exit breakpoint instruction from the breakpoint processing information, and exiting the target breakpoint based on the exit breakpoint instruction;
based on the breakpoint processing information, running the debugging object to the target breakpoint includes: acquiring the position and the running instruction of the target breakpoint from the breakpoint processing information, and indicating the debugging object to run to the target breakpoint of the position based on the running instruction;
canceling the target breakpoint based on the breakpoint processing information, including: and acquiring a breakpoint canceling instruction from the breakpoint processing information, and canceling the target breakpoint based on the breakpoint canceling instruction.
In the embodiment of the disclosure, breakpoint processing information can be received from the debugging front end, and corresponding breakpoint operations are executed on the debugging object platform based on different breakpoint processing information, compared with executing the debugging operations on the debugging back end, the breakpoint processing method and the debugging object platform directly execute different breakpoint operations based on the interaction between the debugging object platform and the debugging front end, so that not only is the network architecture simple, but also the network architecture related to the debugging environment is the same as the actually-running network architecture; the process of data interaction involved in debugging is also the same as that of data interaction in the actual running of fast applications. Therefore, the obtained debugging data is highly similar to the data of the actual operation of the debugging object, the difference between the debugging data and the data obtained by the actual operation of the fast application can be reduced, and the efficiency of the fast application and the accuracy of the debugging result are improved.
In other optional embodiments, obtaining a debugging result of the debugging object based on the debugging operation and the runtime data includes:
when the debugging object runs to the target breakpoint based on the debugging operation, acquiring target running-time data acquired when the debugging object runs to the target breakpoint;
and obtaining a debugging result based on the target runtime data.
Here, also taking the case that the debugging object is a fast application as an example, based on that a target breakpoint has been set at a set position, when the fast application runs to the target breakpoint, the fast application running program can be temporarily suspended at the set position, at this time, the running data when the fast application is suspended, that is, the target running data, can be acquired, and then the debugging result can be obtained based on the target running data.
In the embodiment of the disclosure, when the application is run to the target breakpoint, the target runtime data is directly obtained, and at this time, the target runtime data is real data when the fast application is actually run to the target breakpoint, so that the difference between the debugging data and the data obtained by actually running the fast application can be reduced, and the efficiency of debugging the fast application and the accuracy of the debugging result can be improved.
In other optional embodiments, obtaining a debugging result based on the target runtime data includes:
when the target runtime data is acquired, storing the target runtime data into a message processing queue;
and sequentially processing target runtime data in the message processing queue to obtain a debugging result.
Here, since congestion of a transmission channel may be caused if target runtime data is directly acquired and debugged during debugging, in the embodiment of the present disclosure, by setting a message processing queue, storing the target runtime data in the message processing queue in a stacked manner, and then sequentially processing the target runtime data in the message processing queue, efficiency and convenience in processing the target runtime data can be improved.
In other optional embodiments, the method further comprises:
detecting whether target runtime data to be processed exist in a message processing queue;
and if the target runtime data to be processed does not exist in the message processing queue, continuing to receive the debugging information until a quit debugging signal is received.
Here, when receiving the debug quit signal sent by the debug target platform, the processing of the runtime data may be ended based on the debug quit signal. Here, the fast application program may be written based on the JS code, and taking transmission of the runtime data based on the JS thread as an example, if a message of exiting the JS thread is received, that is, when a control signal for the terminal to process the runtime data is received, the interrupt interface of the JS engine needs to be executed, and the JS code that is not executed is abandoned, so that the JS thread can be quickly closed.
In other optional embodiments, based on the debug information, performing a debug operation corresponding to the debug information includes:
acquiring the position and the running instruction of a target breakpoint from debugging information;
and executing corresponding debugging operation based on the running instruction, and indicating the debugging object to run to the target breakpoint.
Here, the position and the execution instruction of the target breakpoint can be acquired based on the debugging information received from the debugging front end, and the corresponding debugging operation is executed based on the execution instruction, so that the debugging object is instructed to run to the target breakpoint, and the direct interaction between the debugging object platform and the debugging front end can be realized. Therefore, debugging is not needed after the debugging object is converted into a webpage with a set format, but the debugging of the fast application or the small program is realized directly through data interaction between the debugging object platform and the debugging front end, and the network architecture related to the whole debugging environment is the same as the network architecture of the fast application which is actually operated; the process of data interaction involved in debugging is also the same as that of data interaction in the actual running of fast applications.
Fig. 2 is a flowchart of a second information processing method according to an exemplary embodiment, as shown in fig. 2, the method mainly includes the following steps:
in step 201, the fast application is converted into a generation 5 html standard specification (H5) page at the fast application back end.
Here, the fast application needs to be converted into an H5 page at the fast application backend, and the H5 page is sent to the browser backend. For example, a fast application is converted to an H5 page based on a compilation tool and a user is given access to the page through a Uniform Resource Locator (URL).
In step 202, the browser backend retrieves the H5 page content.
In step 203, the front end of the browser displays the debugging information and sends a breakpoint signal to the back end of the browser.
Wherein the debug information includes a debug page status.
In step 204, the browser backend receives a breakpoint signal.
In step 205, the browser backend executes the fast application to the breakpoint position according to the breakpoint signal, and starts breakpoint debugging.
In step 206, the browser backend performs a breakpoint debugging process.
Here, the browser backend may receive the debugging instruction of the browser front end, and sequentially process the received debugging instruction, and continue to wait for the breakpoint signal after processing.
In step 207, if the browser backend receives a signal to exit the breakpoint, the breakpoint debugging process is ended.
Fig. 3 is a flowchart three illustrating an information processing method according to an exemplary embodiment, as shown in fig. 3, the method mainly includes the following steps:
in step 301, the fast application platform initiates fast application debugging.
In step 302, the browser front-end displays the debugging information and sends a breakpoint signal to the fast application platform.
In step 303, the fast application platform receives a breakpoint signal.
In step 304, the fast application platform executes the fast application to the breakpoint position according to the breakpoint signal, and starts breakpoint debugging.
In step 305, the fast application platform performs a breakpoint debugging process.
In step 306, if the fast application platform receives a signal to exit the breakpoint, the breakpoint debugging process ends.
Fig. 4 is a fourth flowchart illustrating an information processing method according to an exemplary embodiment, as shown in fig. 4, the method mainly includes the following steps:
in step 401, the fast application backend starts the fast application debugging and loads the JS engine.
Here, before the fast application backend starts the fast application debugging and loads the JS engine, the method includes: and compiling the fast application App at the PC terminal. The JS engine is built in the rear end of the fast application platform.
In step 402, the debug front end exposes debug information and sends breakpoint information to the fast application platform.
Wherein the breakpoint information includes at least one of: setting a breakpoint, exiting the breakpoint, running to the breakpoint, executing to the next step, canceling the breakpoint, checking stacks, checking variables and other information. The debugging front end is the browser front end.
In step 403, the fast application backend controls the JS engine to set breakpoint information.
In step 404, when the JS engine runs to the breakpoint, the JS engine stops running and calls the fast application platform interface.
Here, the JS engine calls the fast application platform interface, and may give control over debugging to the fast application platform, that is, switch the fast application from the running thread to the debugging thread, and perform debugging-related operations based on the fast application platform.
In step 405, the fast application back-end feeds back the breakpoint processing result.
In step 406, if the fast application back end receives a signal to exit the breakpoint, the breakpoint debugging process ends.
In the embodiment of the present disclosure, the end condition for ending the breakpoint debugging process is: a message to exit the breakpoint is received. In other alternative embodiments, the end condition for ending the breakpoint debugging process may also be set as: and detecting whether the connection between the fast application back end and the debugging front end is abnormal or disconnected, and ending the breakpoint debugging process when the connection between the fast application back end and the debugging front end is abnormal or disconnected.
According to the technical scheme, the debugging function is added to the fast application rear end, and the fast application is debugged based on the fast application rear end, so that the data obtained in the debugging process during operation is from the data of the actual operation of the fast application, namely the data during operation during debugging is consistent with the data during actual operation of the fast application, the difference between the debugging data and the real situation can be reduced, and the accuracy of the debugging result is improved.
Fig. 5 is a block diagram illustrating an information processing apparatus according to an example embodiment. As shown in fig. 5, the information processing apparatus 500 mainly includes:
a first obtaining module 501, configured to run a debug object and obtain runtime data of the debug object, where the debug object includes: fast applications and/or applets;
a first receiving module 502 configured to receive debugging information;
an executing module 503 configured to execute a debugging operation corresponding to the debugging information based on the debugging information;
a second obtaining module 504 configured to obtain a debugging result based on the debugging operation and the runtime data.
In other optional embodiments, the second obtaining module includes:
the first obtaining sub-module is configured to obtain target runtime data of the debugging object running to a target breakpoint when the debugging object runs to the target breakpoint;
and the second obtaining submodule is configured to obtain a debugging result based on the target runtime data.
In other optional embodiments, the second obtaining sub-module is further configured to:
when the target runtime data is acquired, storing the target runtime data into a message processing queue;
and sequentially processing the target runtime data in the message processing queue to obtain the debugging result.
In other optional embodiments, the apparatus further comprises:
a detection module configured to detect whether there is target runtime data to be processed in the message processing queue;
and the second receiving module is configured to continue to receive the debugging information until receiving the quit debugging signal if the target runtime data to be processed does not exist in the message processing queue.
In other optional embodiments, the execution module includes:
the third obtaining submodule is configured to obtain the position and the running instruction of the target breakpoint from the debugging information;
and the control submodule is configured to execute corresponding debugging operation based on the running instruction and indicate the debugging object to run to the target breakpoint.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 6 is a block diagram illustrating a hardware configuration of an information processing apparatus 600 according to an exemplary embodiment. For example, the apparatus 600 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 the like.
Referring to fig. 6, apparatus 600 may include one or more of the following components: a processing component 602, a memory 604, a power component 606, a multimedia component 608, an audio component 610, an interface to input/output (I/O) 612, a sensor component 614, and a communication component 616.
The processing component 602 generally controls overall operation of the device 600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 can include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.
The memory 604 is configured to store various types of data to support operations at the apparatus 600. Examples of such data include instructions for any application or method operating on device 600, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 604 may be implemented by any type or combination of volatile or non-volatile memory 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 multimedia component 608 includes a screen that provides an output interface between the device 600 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 608 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 600 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 610 is configured to output and/or input audio signals. For example, audio component 610 includes a Microphone (MIC) configured to receive external audio signals when apparatus 600 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 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.
The I/O interface 612 provides an interface between the processing component 602 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 component 614 includes one or more sensors for providing status assessment of various aspects of the apparatus 600. For example, the sensor component 614 may detect an open/closed state of the device 600, the relative positioning of components, such as a display and keypad of the device 600, the sensor component 614 may also detect a change in position of the device 600 or a component of the device 600, the presence or absence of user contact with the device 600, orientation or acceleration/deceleration of the device 600, and a change in temperature of the device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 614 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 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 616 is configured to facilitate communications between the apparatus 600 and other devices in a wired or wireless manner. The apparatus 600 may access a wireless network based on a communication standard, such as WiFi, 2G or 6G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 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, and other technologies.
In an exemplary embodiment, the apparatus 600 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 604 comprising instructions, executable by the processor 620 of the apparatus 600 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 in which instructions, when executed by a processor of an electronic device, enable the electronic device to perform an information processing method, the method comprising:
the method comprises the steps of running a debugging object and obtaining the running data of the debugging object, wherein the debugging object comprises: fast applications and/or applets;
receiving debugging information;
executing debugging operation corresponding to the debugging information based on the debugging information;
and obtaining a debugging result based on the debugging operation and the runtime data.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure 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 present disclosure is limited only by the appended claims.
Claims (12)
1. An information processing method, applied to a debugging object platform, includes:
the method comprises the steps of running a debugging object and obtaining the running data of the debugging object, wherein the debugging object comprises: fast applications and/or applets;
receiving debugging information;
executing debugging operation corresponding to the debugging information based on the debugging information;
and obtaining a debugging result based on the debugging operation and the runtime data.
2. The method of claim 1, wherein obtaining a debug result based on the debug operation and the runtime data comprises:
when the debugging object runs to a target breakpoint based on the debugging operation, acquiring target runtime data acquired when the debugging object runs to the target breakpoint;
and obtaining a debugging result based on the target runtime data.
3. The method of claim 2, wherein obtaining the debugging result based on the target runtime data comprises:
when the target runtime data is acquired, storing the target runtime data into a message processing queue;
and sequentially processing the target runtime data in the message processing queue to obtain the debugging result.
4. The method of claim 3, further comprising:
detecting whether target runtime data to be processed exist in the message processing queue;
and if the target runtime data to be processed does not exist in the message processing queue, continuing to receive the debugging information until a quit debugging signal is received.
5. The method of claim 2, wherein performing, based on the debug information, a debug operation corresponding to the debug information comprises:
acquiring the position and the running instruction of the target breakpoint from the debugging information;
and executing corresponding debugging operation based on the running instruction, and indicating the debugging object to run to the target breakpoint.
6. An information processing apparatus characterized by comprising:
a first obtaining module configured to run a debug object and obtain runtime data of the debug object, wherein the debug object includes: fast applications and/or applets;
a first receiving module configured to receive debugging information;
the execution module is configured to execute debugging operation corresponding to the debugging information based on the debugging information;
and the second acquisition module is configured to obtain a debugging result based on the debugging operation and the runtime data.
7. The apparatus of claim 6, wherein the second obtaining module comprises:
the first obtaining sub-module is configured to obtain target runtime data obtained when the debugging object runs to a target breakpoint based on the debugging operation when the debugging object runs to the target breakpoint;
and the second obtaining submodule is configured to obtain a debugging result based on the target runtime data.
8. The apparatus of claim 7, wherein the second acquisition submodule is further configured to:
when the target runtime data is acquired, storing the target runtime data into a message processing queue;
and sequentially processing the target runtime data in the message processing queue to obtain the debugging result.
9. The apparatus of claim 8, further comprising:
a detection module configured to detect whether there is target runtime data to be processed in the message processing queue;
and the second receiving module is configured to continue to receive the debugging information until receiving the quit debugging signal if the target runtime data to be processed does not exist in the message processing queue.
10. The apparatus of claim 7, wherein the execution module comprises:
the third obtaining submodule is configured to obtain the position and the running instruction of the target breakpoint from the debugging information;
and the control submodule is configured to execute corresponding debugging operation based on the running instruction and indicate the debugging object to run to the target breakpoint.
11. An information processing apparatus characterized by comprising:
a processor;
a memory configured to store processor-executable instructions;
wherein the processor is configured to: when executed, implement the steps in any of the information processing methods of claims 1 to 5 above.
12. A non-transitory computer-readable storage medium in which instructions, when executed by a processor of an information processing apparatus, enable the apparatus to perform the information processing method of any one of claims 1 to 5 above.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911042752.3A CN110795354A (en) | 2019-10-30 | 2019-10-30 | Information processing method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911042752.3A CN110795354A (en) | 2019-10-30 | 2019-10-30 | Information processing method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110795354A true CN110795354A (en) | 2020-02-14 |
Family
ID=69441959
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911042752.3A Pending CN110795354A (en) | 2019-10-30 | 2019-10-30 | Information processing method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110795354A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112269708A (en) * | 2020-12-22 | 2021-01-26 | 湖北芯擎科技有限公司 | Debugging information acquisition method and device, electronic equipment and storage medium |
| CN113626321A (en) * | 2021-07-29 | 2021-11-09 | 北京达佳互联信息技术有限公司 | Bridging test method, device, system and storage medium |
| WO2022100033A1 (en) * | 2020-11-16 | 2022-05-19 | 百度在线网络技术（北京）有限公司 | Method and apparatus for debugging applet, electronic device and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101719093A (en) * | 2009-12-09 | 2010-06-02 | 上海普元信息技术有限责任公司 | System and method for realizing cross-browser Javascript debugging in enterprise Web application system |
| CN102902618A (en) * | 2011-07-28 | 2013-01-30 | 华为技术有限公司 | Method and device for developing and debugging application programs of mobile equipment |
| CN109542463A (en) * | 2018-10-26 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Compiling file packet transmission method, device, computer equipment and storage medium |
| CN109739770A (en) * | 2019-01-04 | 2019-05-10 | 百度在线网络技术（北京）有限公司 | The adjustment method and device of small routine |
| CN109800159A (en) * | 2018-12-27 | 2019-05-24 | 百富计算机技术（深圳）有限公司 | Program debugging method, program debugging device, terminal 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-30 CN CN201911042752.3A patent/CN110795354A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101719093A (en) * | 2009-12-09 | 2010-06-02 | 上海普元信息技术有限责任公司 | System and method for realizing cross-browser Javascript debugging in enterprise Web application system |
| CN102902618A (en) * | 2011-07-28 | 2013-01-30 | 华为技术有限公司 | Method and device for developing and debugging application programs of mobile equipment |
| CN109542463A (en) * | 2018-10-26 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Compiling file packet transmission method, device, computer equipment and storage medium |
| CN109800159A (en) * | 2018-12-27 | 2019-05-24 | 百富计算机技术（深圳）有限公司 | Program debugging method, program debugging device, terminal device and storage medium |
| CN109739770A (en) * | 2019-01-04 | 2019-05-10 | 百度在线网络技术（北京）有限公司 | The adjustment method and device of small routine |
| CN110032512A (en) * | 2019-03-28 | 2019-07-19 | 腾讯科技（深圳）有限公司 | A kind of adjustment method of small routine, relevant device and terminal |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022100033A1 (en) * | 2020-11-16 | 2022-05-19 | 百度在线网络技术（北京）有限公司 | Method and apparatus for debugging applet, electronic device and storage medium |
| CN112269708A (en) * | 2020-12-22 | 2021-01-26 | 湖北芯擎科技有限公司 | Debugging information acquisition method and device, electronic equipment and storage medium |
| CN113626321A (en) * | 2021-07-29 | 2021-11-09 | 北京达佳互联信息技术有限公司 | Bridging test method, device, system and storage medium |
| CN113626321B (en) * | 2021-07-29 | 2024-03-19 | 北京达佳互联信息技术有限公司 | Bridging test method, device, system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032606B (en) | Native application compiling method and device and terminal | |
| US20180365004A1 (en) | Method and device for calling software development kit | |
| EP2998899A1 (en) | Method and apparatus for running application program | |
| CN110781080B (en) | Program debugging method and device and storage medium | |
| CN111221559B (en) | Application updating method, device, storage medium, terminal and server | |
| CN110795354A (en) | Information processing method, device and storage medium | |
| CN105808305B (en) | Static resource loading method and device | |
| CN107423218B (en) | Application testing method, device and terminal | |
| CN110928543A (en) | Page processing method and device and storage medium | |
| CN104881304B (en) | Resource downloading method and device | |
| CN109117144B (en) | Page processing method, device, terminal and storage medium | |
| CN109344051B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN107562500B (en) | Debugging device, method and equipment | |
| CN109684112B (en) | Program file operation method, device, terminal and storage medium | |
| CN106612149B (en) | Radio frequency circuit testing method, device and system and mobile terminal | |
| CN108984417B (en) | Software testing method, device, terminal and storage medium | |
| CN111338961B (en) | Application debugging method and device, electronic equipment and storage medium | |
| CN113377370A (en) | File processing method and device, electronic equipment and storage medium | |
| CN110851370B (en) | Program testing method and device and storage medium | |
| CN110908904A (en) | Method and device for debugging fast application and electronic equipment | |
| CN110221813B (en) | Application data connection establishment method and device, storage medium and electronic equipment | |
| CN111596980A (en) | Information processing method and device | |
| CN113407879B (en) | Data reporting method, device and readable medium | |
| CN114780334A (en) | Power consumption monitoring method, power consumption monitoring device and storage medium | |
| CN111290944B (en) | Script generation method, script generation device and storage medium |
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 |