CN111092780A - Method and system for dynamically debugging android system - Google Patents
Method and system for dynamically debugging android system Download PDFInfo
- Publication number
- CN111092780A CN111092780A CN201811236307.6A CN201811236307A CN111092780A CN 111092780 A CN111092780 A CN 111092780A CN 201811236307 A CN201811236307 A CN 201811236307A CN 111092780 A CN111092780 A CN 111092780A
- Authority
- CN
- China
- Prior art keywords
- debugging
- terminal
- protocol
- debugged
- command
- 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
- 238000000034 method Methods 0.000 title claims abstract description 25
- 230000005540 biological transmission Effects 0.000 claims description 13
- 230000003213 activating effect Effects 0.000 claims description 10
- 238000012546 transfer Methods 0.000 claims description 10
- 230000011218 segmentation Effects 0.000 claims description 2
- 230000004913 activation Effects 0.000 abstract description 2
- 238000010276 construction Methods 0.000 abstract 1
- 230000006870 function Effects 0.000 description 10
- 230000018109 developmental process Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/18—Protocol analysers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a system for dynamically debugging an android system, wherein the method comprises the following steps: the debugging device comprises an equipment identifier generation module, a debugging protocol construction module, a debugging terminal starting module, a debugged terminal activation module, a debugging result feedback module and a debugged terminal pushing module, the debugging function is opened through a password at the debugged terminal, then the registered terminal is checked through a built-in checking and debugging command at the debugging end, then a debugger of the debugging end is used, the debugger and the debugged terminal are connected, the connection mode mainly comprises the debugging command, the debugging command is sent to the debugged terminal through the debugger for debugging, the remote debugging function only depending on a network is realized, the specified android software can be sent to the debugged terminal at any time without space limitation, the debugging function is easy to expand, and the debugged terminal is supported to carry out a file pushing function to the debugger.
Description
Technical Field
The invention relates to the technical field of computer software, in particular to a method and a system for dynamically debugging an android system.
Background
In the process of android mobile terminal development, due to the diversity of customized versions of the android system, the running condition and the positioning troubleshooting problem of the mobile phone software are often needed to be known in real time in the running process of the mobile phone software, but due to the particularity of the mobile terminal, remote program debugging cannot be carried out in a remote cooperation mode similar to a PC terminal, and therefore, a set of convenient debugging system of the android terminal is very necessary to be provided.
Disclosure of Invention
Technical problem to be solved
Aiming at the defects of the prior art, the invention provides a method and a system for dynamically debugging an android system, which realize that a debugged terminal and a debugging end can access the Internet to debug android mobile phone software without other external conditions, and solve the problem of expanding debugging commands.
(II) technical scheme
In order to achieve the purpose, the invention is realized by the following technical scheme: a system for android system dynamic debugging, comprising:
the equipment identifier generating module is used for generating unique equipment identifiers matched with each other between the debugging terminal and the debugged terminal;
the debugging protocol building module is used for building and generating a debugging protocol for mutual matching and data exchange among the debugging terminal, the debugged terminal and the debugging server, and comprises a first heartbeat protocol, a second heartbeat protocol and a debugging terminal request list protocol;
the debugging terminal starting module is used for registering the debugging terminal to the debugging server end through a first heartbeat protocol, registering a group of debugging commands and starting debugging of the debugging terminal;
the debugged terminal activating module is used for activating a debugging interface of the debugged terminal and registering the debugged terminal to the debugging server end through a second heartbeat protocol so as to receive a debugging command of the debugging terminal;
the debugging module is used for checking and acquiring the equipment identifier by the debugging terminal through a debugging terminal request list protocol, connecting the debugged terminal through the equipment identifier, caching the acquired equipment identifier, and calling the debugging command for debugging so as to enable all the calling commands of the debugging terminal to be routed to the debugging terminal through the debugging server;
and the debugged terminal supports the extension of the debugging command through the registered debugging command interface and returns the debugging result to the debugging terminal through the debugging command interface.
Preferably, the system further includes a debugged terminal pushing module, the reserved file of the debugged terminal is pushed to the debugging server through the file transfer protocol, the debugging server informs the debugger through the device identifier in the file transfer protocol, and the debugger requests the corresponding file in the debugging server through receiving the transmission protocol and informs the debugger of ending the task.
Preferably, the debugging protocol building module includes: setting special character string marks of segmentation data at the initial position and the end position of a debugging protocol respectively, wherein the special character string marks are used for segmenting different protocol data, and setting a first heartbeat protocol unit, a request user list protocol unit and a request file protocol unit at a debugging terminal; setting a request response identifier, a second heartbeat protocol unit which is the same as the debugging terminal and a data forwarding unit at a debugging server end; and setting a protocol unit for executing a specific debugging command and a file transmission protocol unit corresponding to the request file protocol unit of the debugging terminal at the debugged terminal.
Preferably, the contents of the debug command interface include: specific debugging commands, debugging command description and JAVA language interface.
Preferably, the extension of the debug system is extended through an interface provided by the SDK of the debuggee terminal.
A method for dynamically debugging an android system comprises the following steps:
generating an equipment identifier, and matching a debugger of the debugging terminal with the debugged terminal through the equipment identifier;
constructing a debugging protocol, and setting a first heartbeat protocol unit, a request user list protocol unit and a request file protocol unit at a debugging terminal; setting a request response identifier, a second heartbeat protocol unit which is the same as the debugging terminal and a data forwarding unit at a debugging server end; setting a protocol unit for executing a specific debugging command and a file transmission protocol unit corresponding to a request file protocol unit of a debugging terminal at the debugged terminal, wherein the protocol unit is used for matching and exchanging data among the debugging terminal, a debugging server and the debugged terminal;
starting a debugging terminal, registering the debugging terminal with a debugging server terminal through a first heartbeat protocol, and registering a group of debugging commands to start debugging of the debugging terminal;
activating the debugged terminal, activating a debugging interface of the debugged terminal, and registering the debugged terminal to a debugging server end through a second heartbeat protocol to receive a debugging command of the debugging terminal;
debugging, wherein a debugging terminal checks and acquires an equipment identifier through a debugging terminal request list protocol, is connected with the debugged terminal through the equipment identifier, caches the acquired equipment identifier, and calls a debugging command for debugging so that all the calling commands of the debugging terminal are routed to the debugging terminal through a debugging server;
and feeding back a debugging result, supporting the extension of the debugging command by the debugged terminal through the registered debugging command interface, and returning the debugging result to the debugging terminal by the debugging command interface.
Preferably, the method further includes pushing the reserved file, the debugged terminal is pushed to the debugging server through a file transfer protocol, the debugging server informs the debugger through a device identifier in the file transfer protocol, and the debugger requests the corresponding file in the debugging server through receiving the transmission protocol and informs the debugger of ending the task.
Preferably, before the debugging protocol is constructed, special character string marks for segmenting data are respectively set at the starting position and the ending position of the debugging protocol so as to segment different protocol data.
Preferably, the debug command interface content includes: specific debugging commands, debugging command description and JAVA language interface.
Preferably, the extension of the debug system is extended through an interface provided by the SDK of the debuggee terminal.
(III) advantageous effects
The invention has the following beneficial effects:
1. the matching of the debugger and the debugged terminal is realized through a network and a debugging protocol algorithm, the debugging channel which is communicated with the debugging end and the debugged terminal is connected, and the whole debugging process of sending, receiving, executing and returning a remote debugging command is realized;
2. supporting file transmission between a debugger and a debugged terminal in the debugging process;
3. and a debugging interface which is easy to expand is reserved in the debugged terminal SDK, so that the debugging command can be expanded conveniently.
Drawings
FIG. 1 is a system flow diagram of dynamic debugging of an android system;
FIG. 2 is a flowchart of a method for dynamically debugging an android system;
fig. 3 is a flowchart of pushing log files.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
And (3) SDK: a Software Development Kit, a full Software Development Kit, provides a programming interface for implementing specific functions.
A debugger: and the tool is used for checking the running state of the software and troubleshooting the software problems.
JSON: JSON (JavaScript Object Notation) is a lightweight data exchange format, and data description is performed by using "key" and "value".
APK: the Android package (apk) is an abbreviation of Android package, and is an application installation package generated by development and compilation of an Android platform.
And an Android terminal: also referred to as a debuggee terminal in the present invention.
A PC terminal: also referred to as the debug port in the present invention.
ftpTransfer: file transfer protocol.
ftpGetFile: a file protocol is received.
regiostercmd: and registering the function.
In the first embodiment of the present invention, referring to fig. 1 and 3, a system for dynamically debugging an android system is generally divided into three parts, where a debugger located at a debugging end in the first part mainly implements functions of pairing the debugger and a debugged terminal, initiating a debugging command after pairing, and performing analysis display on a result returned by the debugged terminal; the second part is a debugging server positioned in a public network, and the main realized functions are the registration of a debugging terminal, the receiving and routing of debugging commands of the debugging terminal, the receiving and pushing of debugging files, the activity state check of the debugging terminal and the like; the third part is a debugging SDK positioned at the debugged terminal, and the main function is to register a debugging command, receive the debugging command sent by the debugger, route the debugging command to a command executor, and then return the result of the command execution to the debugger.
The equipment identifier generating module is used for generating unique equipment identifiers matched with each other between the debugging terminal and the debugged terminal;
the debugging protocol building module is used for building and generating a debugging protocol for mutual matching and data exchange among the debugging terminal, the debugged terminal and the debugging server, and comprises a first heartbeat protocol, a second heartbeat protocol and a debugging terminal request list protocol;
the debugging terminal starting module is used for registering the debugging terminal to the debugging server end through a first heartbeat protocol, registering a group of debugging commands and starting debugging of the debugging terminal;
the debugged terminal activating module is used for activating a debugging interface of the debugged terminal and registering the debugged terminal to the debugging server end through a second heartbeat protocol so as to receive a debugging command of the debugging terminal;
the debugging module is used for checking and acquiring the equipment identifier by the debugging terminal through a debugging terminal request list protocol, connecting the debugged terminal through the equipment identifier, caching the acquired equipment identifier, and calling the debugging command for debugging so as to enable all the calling commands of the debugging terminal to be routed to the debugging terminal through the debugging server;
and the debugged terminal supports the extension of the debugging command through the registered debugging command interface and returns the debugging result to the debugging terminal through the debugging command interface.
The system also comprises a debugged terminal pushing module, wherein the reserved file of the debugged terminal is pushed to the debugging server through a file transmission protocol, the debugging server informs the debugger through a device identifier in the file transmission protocol, and the debugger requests the corresponding file in the debugging server through receiving the transmission protocol and informs the debugger of finishing the task.
In the second embodiment of the present invention, referring to fig. 2 and fig. 3, a method for dynamically debugging an android system is provided.
The method comprises the steps of generating equipment identifications, generating an equipment identification for a debugging terminal of each terminal including a debugger and the debugged terminal for uniquely identifying one terminal, pairing all debuggers in the following method, routing a debugging command, pushing and forwarding a log file based on the equipment identification, randomly generating the equipment identifications for the first time and caching the equipment identifications to the local, and directly using the equipment identifications cached for the first time to ensure that the equipment identifications of all equipment are different and the equipment identifications of the same equipment after the equipment is restarted are kept unchanged.
The method comprises the steps of constructing a debugging protocol, designing a group of debugging protocols for pairing and data exchange among a debugger, a debugging server and a debugged terminal, describing the protocol by adopting a text-type Json character string on the basis of the principle of easy expansion and easy maintenance, marking the starting position and the ending position of the protocol by using a fixed special character string and dividing different protocol data, namely processing sub-packets and sticky packets which are often called by people, wherein a dataType field, a unique field and an id field are public fields and respectively represent the protocol type, the equipment identification and the id of the protocol and are mainly used for corresponding to a return packet. If the server side has the response, the format of the response packet is as follows:
the dataType field is the protocol identification, where the fixed reply flag is a reply packet.
id: and the id in the corresponding request packet is used for corresponding the request packet and the response packet.
stat: request status, 0 identifies success, and others fail.
content: and the returned request receipt content is specified.
The heartbeat protocol of the terminal and the server is mainly used for registering and checking the states of the debugging terminal:
{
"dataType":"heartbeat_c2s",
"unique": terminal identification ",
"id":111,
"clientDesc": device description ",
"ip" means "internal ip",
"Port": internal Port "
And a clientDesc field, wherein the device description field is mainly used for describing the terminal device in a text mode.
ip: and debugging the ip address of the terminal.
port is port number of the debugging terminal.
The terminal request user list protocol is mainly used for the debugging end to obtain the list of the current debugged terminal:
{
"dataType":"getUserList",
"serial":111,
"unique": terminal identification ",
time sending time "
}
Data forwarded by the debugging server:
src field: identification of the device initiating the request
dst field: equipment identification of target debugging terminal
content: data content to be forwarded
Requiring the debugged terminal to execute a specific debugging command protocol:
{
"dataType":"runcmd_c2c",
"unique": terminal identification ",
time-sending time,
"cmd": Command identification "
}
cmd field: commands to be executed, of course, this data needs to be routed to the debugged terminal through the transdata, transmission data instruction. Most debug commands are routed through this protocol to the debug terminal. Then, a set of file transfer protocols is used for the debuggee terminal to push files to the debugger:
{
"dataType":"ftpTransfer",
"id":112233,
"fileUnique": file identification ",
"src" means "file sender",
"dst": file receiver ",
"desc": file description ",
"fileSize":112233,
"fileName"
}
And the fileUnique is that a random character string generated by the debugged terminal is used for uniquely identifying a file on a server, and the file is downloaded by the identifier when the debugger downloads the file.
src: the device identification of the file sender.
dst: the device identification of the file recipient.
desc: descriptive text information about the file.
fileSize-representing the file size of the file in bytes.
filiename: the file name of the file.
The debugging terminal requests the file pushed by the debugged terminal to the debugging server:
{
"dataType":"ftpGetFile",
"id":1122323,
"ftpUnique":"abcdef"
}
ftpUnique: the file identification to be requested, usually initiated by the debugger terminal, requests the file from the debug server.
The debugging terminal is started, the debugger is located at the pc end, after the debugging terminal is started, the debugging terminal registers itself with the debugging server through a heartbeat protocol, then a group of built-in debugging commands are registered for starting debugging, and the group of initial debugging commands mainly comprises debugging command lists for checking debugging, debugging command lists for checking support, debugging command lists for connecting debugged terminals and the like.
The debugged terminal is activated, before debugging, the debugged terminal needs to activate a debugging function firstly, a debugging interface of the debugged terminal is activated at an android end in a secret code mode, after activation, the debugged terminal registers the debugged terminal with a debugging server firstly, and after registration, a debugging command of a debugger can be received.
When the debugger needs debugging, firstly, a debugging terminal list function is checked to check which debugged terminals exist locally, then the equipment identifiers of the debugged terminals are obtained, then the debugged terminals are connected through the equipment identifiers, the equipment identifiers of the connected debugged terminals are cached locally after connection is successful, and then all debugging commands are routed to the debugging terminals through a debugging server.
The debugging result is fed back, the debugged terminal supports the extension of the debugging command by providing an interface for registering the debugging command, the first parameter of the interface is a specific debugging command, the second parameter is about the description of the command, the third parameter is a Java interface, the interface is debugged after the debugged terminal receives the command declared by the first parameter, the first parameter of the interface is that the debugging command corresponds to the first parameter of the register cmd function, the second parameter is a command parameter input by a debugging end, and the internal implementation of the interface is the specific logic of the debugging command. The return value of the interface is a debugging result returned by the debugging command to the debugger, and is shown in text, wherein each element is a line of data.
The method comprises the steps that a log file pushing process is carried out, a debugged terminal reserves a file pushing interface, if the debugged terminal needs to transmit a file to a debugger, the debugged terminal pushes the file to a debugging server through an ftpTransfer protocol, then the debugging server informs the corresponding debugger server of a new file through a target device identifier in the ftpTransfer, the debugger actively requests the corresponding file to the server through an ftpGetFile protocol after receiving the notification, the request is finished, and the debugger requests are informed of being finished, so that the file is routed to the debugger from an android end to be debugged.
Therefore, the whole debugging process of the command interactive debugger based on the network is finished, and the specific debugging function can be continuously expanded through the interface provided by the SDK at the android end without being repeated.
Embodiments of the invention: if a certain mobile phone needs to be remotely debugged, firstly, a debugging function is opened at an android end through a secret code defined in advance, then, a built-in debugging terminal checking command is used for checking which terminals are registered at the debugging end, then, a debugger at a pc end is used for connecting the debugger with the debugged terminal through a connection debugging terminal command, and then, the debugging command can be sent to the debugged terminal through the debugger to be debugged.
Claims (10)
1. A system for android system dynamic debugging, comprising:
the equipment identifier generating module is used for generating unique equipment identifiers matched with each other between the debugging terminal and the debugged terminal;
the debugging protocol building module is used for building and generating a debugging protocol for mutual matching and data exchange among the debugging terminal, the debugged terminal and the debugging server, and comprises a first heartbeat protocol, a second heartbeat protocol and a debugging terminal request list protocol;
the debugging terminal starting module is used for registering the debugging terminal to the debugging server end through a first heartbeat protocol, registering a group of debugging commands and starting debugging of the debugging terminal;
the debugged terminal activating module is used for activating a debugging interface of the debugged terminal and registering the debugged terminal to the debugging server end through a second heartbeat protocol so as to receive a debugging command of the debugging terminal;
the debugging module is used for checking and acquiring the equipment identifier by the debugging terminal through a debugging terminal request list protocol, connecting the debugged terminal through the equipment identifier, caching the acquired equipment identifier, and calling the debugging command for debugging so as to enable all the calling commands of the debugging terminal to be routed to the debugging terminal through the debugging server;
and the debugged terminal supports the extension of the debugging command through the registered debugging command interface and returns the debugging result to the debugging terminal through the debugging command interface.
2. The system according to claim 1, wherein the system further includes a debugged terminal push module, the reserved file of the debugged terminal is pushed to the debugging server through a file transfer protocol, the debugging server informs the debugger through a device identifier in the file transfer protocol, and the debugger requests the corresponding file in the debugging server through receiving the transmission protocol and notifies the debugger of ending the task.
3. The system according to claim 1, wherein the debugging protocol building module includes: setting special character string marks of segmentation data at the initial position and the end position of a debugging protocol respectively, wherein the special character string marks are used for segmenting different protocol data, and setting a first heartbeat protocol unit, a request user list protocol unit and a request file protocol unit at a debugging terminal; setting a request response identifier, a second heartbeat protocol unit which is the same as the debugging terminal and a data forwarding unit at a debugging server end; and setting a protocol unit for executing a specific debugging command and a file transmission protocol unit corresponding to the request file protocol unit of the debugging terminal at the debugged terminal.
4. The system according to claim 1, wherein the contents of the debug command interface include: specific debugging commands, debugging command description and JAVA language interface.
5. The system according to claim 1, wherein the extension of the debugging system is extended through an interface provided by an SDK of the debuggee terminal.
6. A method for dynamically debugging an android system is characterized by comprising the following steps:
generating an equipment identifier, and matching a debugger of the debugging terminal with the debugged terminal through the equipment identifier; constructing a debugging protocol, and setting a first heartbeat protocol unit, a request user list protocol unit and a request file protocol unit at a debugging terminal; setting a request response identifier, a second heartbeat protocol unit which is the same as the debugging terminal and a data forwarding unit at a debugging server end; setting a protocol unit for executing a specific debugging command and a file transmission protocol unit corresponding to a request file protocol unit of a debugging terminal at the debugged terminal, wherein the protocol unit is used for matching and exchanging data among the debugging terminal, a debugging server and the debugged terminal;
starting a debugging terminal, registering the debugging terminal with a debugging server terminal through a first heartbeat protocol, and registering a group of debugging commands to start debugging of the debugging terminal;
activating the debugged terminal, activating a debugging interface of the debugged terminal, and registering the debugged terminal to a debugging server end through a second heartbeat protocol to receive a debugging command of the debugging terminal;
debugging, wherein a debugging terminal checks and acquires an equipment identifier through a debugging terminal request list protocol, is connected with the debugged terminal through the equipment identifier, caches the acquired equipment identifier, and calls a debugging command for debugging so that all the calling commands of the debugging terminal are routed to the debugging terminal through a debugging server;
and feeding back a debugging result, supporting the extension of the debugging command by the debugged terminal through the registered debugging command interface, and returning the debugging result to the debugging terminal by the debugging command interface.
7. The method according to claim 6, further comprising pushing the reserved file, wherein the debugged terminal is pushed to the debugging server through a file transfer protocol, the debugging server informs the debugger through a device identifier in the file transfer protocol, and the debugger requests the corresponding file in the debugging server through receiving the transmission protocol and notifies the debugger of ending the task.
8. The method according to claim 6, wherein before the debugging protocol is constructed, special character string markers for segmenting data are respectively set at a start position and an end position of the debugging protocol to segment different protocol data.
9. The method for dynamically debugging an android system of claim 6, wherein the debugging command interface content comprises: specific debugging commands, debugging command description and JAVA language interface.
10. The method according to claim 6, wherein the extension of the debugging system is extended through an interface provided by an SDK of the debuggee terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811236307.6A CN111092780A (en) | 2018-10-23 | 2018-10-23 | Method and system for dynamically debugging android system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811236307.6A CN111092780A (en) | 2018-10-23 | 2018-10-23 | Method and system for dynamically debugging android system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111092780A true CN111092780A (en) | 2020-05-01 |
Family
ID=70391843
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811236307.6A Pending CN111092780A (en) | 2018-10-23 | 2018-10-23 | Method and system for dynamically debugging android system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111092780A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111711969A (en) * | 2020-06-12 | 2020-09-25 | 荆门汇易佳信息科技有限公司 | Power saving method for health mobile monitoring platform focusing on android mobile phone end |
| CN112486813A (en) * | 2020-11-25 | 2021-03-12 | 广州品唯软件有限公司 | Debugging method, debugging device and computer readable storage medium |
| CN114691486A (en) * | 2020-12-30 | 2022-07-01 | 腾讯科技（深圳）有限公司 | Program debugging method and device and computer equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120102460A1 (en) * | 2010-10-21 | 2012-04-26 | International Business Machines Corporation | Collaborative Software Debugging In A Distributed System With Client-Specific Dynamic Breakpoints |
| CN103902358A (en) * | 2014-03-18 | 2014-07-02 | 北京领通科技有限公司 | Mobile terminal remote debugging method and system and mobile terminal |
| CN105338110A (en) * | 2015-11-23 | 2016-02-17 | 小米科技有限责任公司 | Remote debugging method, platform and server |
| CN106182005A (en) * | 2016-08-08 | 2016-12-07 | 江阴市雷奥机器人技术有限公司 | A kind of robot remote adjustment method |
| CN107026764A (en) * | 2016-02-02 | 2017-08-08 | 腾讯科技（深圳）有限公司 | A kind of remote debugging method, equipment, server and system |
| CN108011883A (en) * | 2017-12-05 | 2018-05-08 | 深圳市创维软件有限公司 | A kind of remote debugging method, terminal device and server |
-
2018
- 2018-10-23 CN CN201811236307.6A patent/CN111092780A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120102460A1 (en) * | 2010-10-21 | 2012-04-26 | International Business Machines Corporation | Collaborative Software Debugging In A Distributed System With Client-Specific Dynamic Breakpoints |
| CN103902358A (en) * | 2014-03-18 | 2014-07-02 | 北京领通科技有限公司 | Mobile terminal remote debugging method and system and mobile terminal |
| CN105338110A (en) * | 2015-11-23 | 2016-02-17 | 小米科技有限责任公司 | Remote debugging method, platform and server |
| CN107026764A (en) * | 2016-02-02 | 2017-08-08 | 腾讯科技（深圳）有限公司 | A kind of remote debugging method, equipment, server and system |
| CN106182005A (en) * | 2016-08-08 | 2016-12-07 | 江阴市雷奥机器人技术有限公司 | A kind of robot remote adjustment method |
| CN108011883A (en) * | 2017-12-05 | 2018-05-08 | 深圳市创维软件有限公司 | A kind of remote debugging method, terminal device and server |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111711969A (en) * | 2020-06-12 | 2020-09-25 | 荆门汇易佳信息科技有限公司 | Power saving method for health mobile monitoring platform focusing on android mobile phone end |
| CN112486813A (en) * | 2020-11-25 | 2021-03-12 | 广州品唯软件有限公司 | Debugging method, debugging device and computer readable storage medium |
| CN114691486A (en) * | 2020-12-30 | 2022-07-01 | 腾讯科技（深圳）有限公司 | Program debugging method and device and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111092780A (en) | Method and system for dynamically debugging android system | |
| CN102904959B (en) | Network accelerating method and gateway | |
| CN110290015B (en) | Remote deployment method, device and storage medium | |
| CN105430711B (en) | Transmission method, device and the equipment of information | |
| CN108306844B (en) | Method for API communication between server and client | |
| CN111159019B (en) | Application program testing method, testing control terminal and testing terminal | |
| CN110413329A (en) | IOT equipment remote debugging method, apparatus and system | |
| CN108600377B (en) | Method, device, terminal and storage medium for suspending file downloading | |
| CN109150977B (en) | Method for automatically generating global serial number based on transaction link | |
| CN107888434B (en) | Network equipment configuration synchronization method and device | |
| CN104040538A (en) | Internet application interaction method, device and system | |
| US7095718B1 (en) | Client/server scan software architecture | |
| JP5610654B2 (en) | Apparatus for providing terminal management package and method for receiving terminal management package | |
| CN106708717B (en) | A kind of exploitation adjustment method and device | |
| CN108600378B (en) | File downloading method, device, terminal and storage medium | |
| CN112468611B (en) | Application program starting method, terminal equipment and computer storage medium | |
| JP2012159924A (en) | Installation system | |
| CN101499031A (en) | Software bug feedback system and method | |
| US10643039B2 (en) | Location based situation awareness system and method thereof | |
| CN106331051A (en) | File transmission method and system, file receiving device and file transmission device | |
| CN110557509A (en) | mobile phone control method and device, electronic equipment and readable storage medium | |
| JP2006113754A (en) | Software update device and method | |
| WO2022121492A1 (en) | File transmission method and apparatus, computer device, and storage medium | |
| US20150067854A1 (en) | Apparatus and method for multi-checking for mobile malware | |
| CN115599669A (en) | Debugging method and device of microservice, electronic equipment and readable 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200501 |