CN112162908B - Method and device for realizing program call link monitoring based on byte code injection technology - Google Patents
Method and device for realizing program call link monitoring based on byte code injection technology Download PDFInfo
- Publication number
- CN112162908B CN112162908B CN202011062468.5A CN202011062468A CN112162908B CN 112162908 B CN112162908 B CN 112162908B CN 202011062468 A CN202011062468 A CN 202011062468A CN 112162908 B CN112162908 B CN 112162908B
- Authority
- CN
- China
- Prior art keywords
- program
- information
- call link
- actual running
- link monitoring
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000012544 monitoring process Methods 0.000 title claims abstract description 37
- 238000002347 injection Methods 0.000 title claims abstract description 27
- 239000007924 injection Substances 0.000 title claims abstract description 27
- 238000005516 engineering process Methods 0.000 title claims abstract description 22
- 230000002159 abnormal effect Effects 0.000 claims abstract description 25
- 238000004590 computer program Methods 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 16
- 230000005856 abnormality Effects 0.000 claims description 14
- 238000007405 data analysis Methods 0.000 claims description 11
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 10
- 238000004458 analytical method Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 239000007795 chemical reaction product Substances 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
Abstract
The invention provides a method and a device for realizing program call link monitoring based on a byte code injection technology, wherein the method comprises the following steps: selecting a buried point position needing to be injected with dynamic byte codes in a program; injecting dynamic byte codes for a monitor call link into the buried point position; and running the program, collecting actual running information of the program from the buried point position, and judging whether the program is abnormal or not according to the actual running information. The method and the device utilize the byte code injection technology, inject codes in specific positions of the running program to be matched with a front-end visualized control interface, and quickly and accurately position the problem and display the problem in a friendly way.
Description
Technical Field
The application belongs to the technical field of program monitoring, and particularly relates to a method and a device for realizing program call link monitoring based on a byte code injection technology.
Background
The traditional program test environment is a pure black box environment for development, when the program BUG submitted by test is analyzed, the analysis can be carried out only by means of the log recorded in the program, and the problem can be difficult to check due to the fact that the log is missing or is not standard, so that the problem root can not be well positioned.
Disclosure of Invention
The application provides a method and a device for realizing program call link monitoring based on a byte code injection technology, which at least solve the defects caused by the problem that the program can only be analyzed and checked by means of a log recorded in the program at present.
According to one aspect of the present application, there is also provided a method for implementing program call link monitoring based on a bytecode injection technology, including:
selecting a buried point position needing to be injected with dynamic byte codes in a program;
injecting dynamic byte codes for a monitor call link into the buried point position;
running the program, collecting actual running information of the program from the buried point position, judging whether the program is abnormal according to the actual running information, wherein the actual running information comprises: input information, output information, positioning position information, stack abnormality information.
In one embodiment, determining whether an abnormality occurs in a program according to actual running information includes:
comparing the actual running information with a prestored expected program running result;
if the actual running information is inconsistent with the expected running result of the program, the program is abnormal.
In an embodiment, the method for implementing program call link monitoring further includes:
and determining a corresponding expected program operation result after the program is operated according to the program, and storing the expected program operation result.
In an embodiment, the method for implementing program call link monitoring further includes:
and configuring a corresponding acquisition information rule according to the type of the program, and acquiring actual running information of the program by the dynamic byte code according to the acquisition information rule.
According to another aspect of the present application, there is also provided a program call link monitoring implementation apparatus based on a bytecode injection technology, including:
the embedded point determining unit is used for selecting the embedded point position needing to be injected with the dynamic byte codes in the program;
the dynamic byte code injection unit is used for injecting the dynamic byte code for the monitoring program call link into the buried point position;
the data analysis unit is used for running the program, collecting actual running information of the program from the buried point position, judging whether the program is abnormal or not according to the actual running information, wherein the actual running information comprises: input information, output information, positioning position information, stack abnormality information.
In an embodiment, the data analysis unit comprises:
the comparison module is used for comparing the actual running information with a prestored expected program running result;
and the abnormality judging module is used for judging that if the actual running information is inconsistent with the expected running result of the program, the program is abnormal.
In an embodiment, the program call link monitoring implementation device further includes:
the expected generation unit is used for determining the corresponding expected program operation result after the program is operated according to the program and storing the expected program operation result.
In an embodiment, the program call link monitoring implementation device further includes:
the information acquisition rule configuration unit is used for configuring corresponding acquisition information rules according to the types of the programs, and the dynamic byte codes acquire actual running information of the programs according to the acquisition information rules.
According to the method and the device, the byte code injection technology is utilized, codes are injected at specific positions in the program, and the function of fast and accurate positioning can be achieved by matching with the front-end visual control interface.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a method for implementing program call link monitoring based on a bytecode injection technology.
Fig. 2 is a flowchart of determining whether an abnormality occurs in a program according to actual running information in an embodiment of the present application.
Fig. 3 is a block diagram of a program calling link monitoring implementation device based on a bytecode injection technology.
Fig. 4 is a block diagram of the structure of the data analysis unit in the embodiment of the present application.
Fig. 5 is a program call link monitoring implementation system provided in an embodiment of the present application.
Fig. 6 is a specific implementation of an electronic device in an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Currently, in order to solve the problem of failure to locate a specific source of a problem under the conditions of incomplete log and abnormal underlying technology stack, the application provides a method for implementing program call link monitoring based on a bytecode injection technology, as shown in fig. 1, comprising:
s101: the embedded point position where the dynamic byte code needs to be injected is selected in the program.
In one embodiment, dynamic bytecodes are inserted at some nodes of a program, where they are inserted, referred to as buried sites, and these selected nodes are typically problem-prone nodes.
S102: dynamic bytecodes for the supervisor call links are injected into the buried site locations.
In one embodiment, the injected dynamic bytecode is used to collect program input, output, program exception location, and exception stack information according to the embedded point, and then the data is structured and stored according to the definition.
S103: and running the program, collecting actual running information of the program from the buried point position, and judging whether the program is abnormal or not according to the actual running information. The actual operation information includes: input information, output information, positioning position information, stack abnormality information.
In one embodiment, determining whether the program is abnormal according to the actual running information, as shown in fig. 2, includes:
s201: and comparing the actual running information with a pre-stored expected program running result.
S202: if the actual running information is inconsistent with the expected running result of the program, the program is abnormal.
In a specific embodiment, the actual running information acquired by the injected dynamic byte codes is filtered, received and structured, and then analyzed, and according to the granularity and atomicity requirements defined previously, the information such as the program input parameter data and the output result data are definitely defined, and then are matched with the expected program running result, wherein the expected program running information comprises a program data request, an expected data return result, an abnormal stack type and the like. If the actual running information of the program is not matched with the expected running result of the program, or the program stack is abnormal, the transaction is overtime, and the like, the conclusion judgment and classification can be carried out on the transaction, and various performance hidden trouble problems of the program are prejudged and displayed to technicians.
In an embodiment, the method for implementing program call link monitoring further includes:
and determining a corresponding expected program operation result after the program is operated according to the program, and storing the expected program operation result.
In an embodiment, the method for implementing program call link monitoring further includes:
and configuring a corresponding acquisition information rule according to the type of the program, and acquiring actual running information of the program by the dynamic byte code according to the acquisition information rule.
Based on the same inventive concept, the embodiments of the present application further provide a device for implementing program call link monitoring based on a bytecode injection technology, which can be used to implement the method described in the above embodiments, as described in the following embodiments. The principle of solving the problem of the program calling link monitoring implementation device based on the byte code injection technology is similar to that of the program calling link monitoring implementation method based on the byte code injection technology, so that the implementation of the program calling link monitoring implementation device based on the byte code injection technology can be referred to the implementation of the program calling link monitoring implementation method based on the byte code injection technology, and the repetition is omitted. As used below, the term "unit" or "module" may be a combination of software and/or hardware that implements the intended function. While the system described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
As shown in fig. 3, the present application provides a device for implementing program call link monitoring based on a bytecode injection technology, including:
a buried point determining unit 301, configured to select a buried point position where a dynamic byte code needs to be injected in a program;
a dynamic byte code injection unit 302, configured to inject a dynamic byte code for a supervisory program call link into a buried point position;
the data analysis unit 303 is configured to run the program, collect actual running information of the program from the buried point, and determine whether the program is abnormal according to the actual running information, where the actual running information includes: input information, output information, positioning position information, stack abnormality information.
In one embodiment, as shown in fig. 4, the data analysis unit 303 includes:
the comparison module 401 is configured to compare the actual running information with a pre-stored expected program running result;
the abnormality determination module 402 is configured to determine that if the actual running information is inconsistent with the expected running result of the program, the program is abnormal.
In an embodiment, the program call link monitoring implementation device further includes:
the expected generation unit is used for determining the corresponding expected program operation result after the program is operated according to the program and storing the expected program operation result.
In an embodiment, the program call link monitoring implementation device further includes:
the information acquisition rule configuration unit is used for configuring corresponding acquisition information rules according to the types of the programs, and the dynamic byte codes acquire actual running information of the programs according to the acquisition information rules.
In a specific embodiment, the application provides a program calling link monitoring implementation system based on a byte code injection technology, which is shown in fig. 5 and comprises a parameter setting module 1, an information acquisition module 2, a data analysis module 3 and a result processing module 4. The information acquisition module 2 is respectively connected with the parameter setting module 1 and the data analysis module 3; the data analysis module 3 is respectively connected with the information acquisition module 2 and the result processing module 4; the data monitoring center 6 completes information interaction with the program codes 5 deployed by the buried points by calling the result processing module 4.
Parameter setting module 1: the method mainly comprises a program model definition unit and a transaction definition rule model unit. The problem definition rule model unit mainly defines the range requirements of acquisition transaction granularity, atomicity, transaction start and end time. The program model definition unit is mainly a program definition type, such as serial procedural, multi-thread concurrency, etc.
Information acquisition module 2: the system mainly comprises an information embedding point unit, an information acquisition unit, an information receiving unit and an information storage unit. The information embedding unit is mainly used for virtually requesting the operation control to acquire information by the acquisition unit, and the information acquisition unit is mainly used for acquiring program input and output, program abnormality positioning positions, abnormal stack abnormality information and the like according to the embedding point; the information receiving unit is responsible for sending the information to the background; the information storage unit carries out structuring processing and storage on the data according to the definition.
Data analysis module 3: the system mainly comprises a model analysis unit which analyzes basic information required by model definition, parameter definition analysis and problem positioning, definitely defines information such as program input parameter data, output result data and the like according to granularity and atomicity definition requirements, and then matches the information with a model setting dimension, wherein the model comprises a program data request, expected data return result, abnormal stack type and the like to obtain an analyzed result.
The result processing module 4: the device mainly comprises a result information storage unit and a result information pushing unit. The result information storage unit stores the result information in a program unit. The result information pushing unit returns specific result content according to the user requirement.
The method and the device utilize the byte code injection technology, inject codes in specific positions of the running program to be matched with a front-end visualized control interface, and quickly and accurately position the problem and display the problem in a friendly way. The graphic display and the message pushing are realized technically through embedding points at specific positions of dynamic byte codes, event acquisition, acquisition information storage, analysis and the like. Through key information and request-level data information of the information, the information storage analysis, the page processing display and the like which are closely related to the test positioning problem, not only can problem analysis result data which are more close to the test be acquired, but also a more accurate positioning problem root can be realized, the problem automatic monitoring display and analysis can be realized, and the analysis mode of manual machinery is eliminated.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The principles and embodiments of the present invention have been described in detail with reference to specific examples, which are provided to facilitate understanding of the method and core ideas of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
The embodiment of the present application further provides a specific implementation manner of an electronic device capable of implementing all the steps in the method in the foregoing embodiment, and referring to fig. 6, the electronic device specifically includes the following:
a processor (processor) 601, memory 602, communication interface (Communications Interface) 603, bus 604, and non-volatile storage 605;
wherein, the processor 601, the memory 602, and the communication interface 603 complete communication with each other through the bus 604;
the processor 601 is configured to invoke the computer program in the memory 602 and the nonvolatile storage 605, where the processor executes the computer program to implement all the steps in the method in the foregoing embodiment, for example, the processor executes the computer program to implement the following steps:
s101: the embedded point position where the dynamic byte code needs to be injected is selected in the program.
S102: dynamic bytecodes for the supervisor call links are injected into the buried site locations.
S103: and running the program, collecting actual running information of the program from the buried point position, and judging whether the program is abnormal or not according to the actual running information.
The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps of the method in the above embodiments, the computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements all the steps of the method in the above embodiments, for example, the processor implements the following steps when executing the computer program:
s101: the embedded point position where the dynamic byte code needs to be injected is selected in the program.
S102: dynamic bytecodes for the supervisor call links are injected into the buried site locations.
S103: and running the program, collecting actual running information of the program from the buried point position, and judging whether the program is abnormal or not according to the actual running information.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a hardware+program class embodiment, the description is relatively simple, as it is substantially similar to the method embodiment, as relevant see the partial description of the method embodiment. Although the present description provides method operational steps as described in the examples or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When implemented in an actual device or end product, the instructions may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even in a distributed data processing environment) as illustrated by the embodiments or by the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, it is not excluded that additional identical or equivalent elements may be present in a process, method, article, or apparatus that comprises a described element. For convenience of description, the above devices are described as being functionally divided into various modules, respectively. Of course, when implementing the embodiments of the present disclosure, the functions of each module may be implemented in the same or multiple pieces of software and/or hardware, or a module that implements the same function may be implemented by multiple sub-modules or a combination of sub-units, or the like. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form. The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be appreciated by those skilled in the art that embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the present specification embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description embodiments may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments. In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the embodiments of the present specification.
In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction. The foregoing is merely an example of an embodiment of the present disclosure and is not intended to limit the embodiment of the present disclosure. Various modifications and variations of the illustrative embodiments will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of the embodiments of the present specification, should be included in the scope of the claims of the embodiments of the present specification.
Claims (10)
1. The method for realizing program call link monitoring based on the byte code injection technology is characterized by comprising the following steps:
selecting a buried point position needing to be injected with dynamic byte codes in a program;
injecting dynamic byte codes for a monitor call link into the buried point position;
and running the program, collecting actual running information of the program from the buried point position, and judging whether the program is abnormal according to the actual running information, wherein the actual running information comprises: input information, output information, positioning position information and stack abnormality information;
the injected dynamic byte code acquires program input information, output information, positioning position and stack abnormal information according to the embedded point, and carries out structural processing and storage on the input information, the output information, the positioning position and the stack abnormal information according to definition.
2. The method for implementing program call link monitoring according to claim 1, wherein said determining whether an abnormality occurs in the program according to the actual running information comprises:
comparing the actual running information with a prestored expected program running result;
if the actual running information is inconsistent with the expected running result of the program, the program is abnormal.
3. The program call link monitoring implementation method according to claim 1, further comprising:
and determining a corresponding expected program operation result after the program is operated according to the program, and storing the expected program operation result.
4. The program call link monitoring implementation method according to claim 1, further comprising:
and configuring a corresponding acquisition information rule according to the type of the program, and acquiring actual running information of the program by the dynamic byte code according to the acquisition information rule.
5. The utility model provides a program call link control implementation device based on byte code injection technique which characterized in that includes:
the embedded point determining unit is used for selecting the embedded point position needing to be injected with the dynamic byte codes in the program;
the dynamic byte code injection unit is used for injecting the dynamic byte code for monitoring the program call link into the buried point position;
the data analysis unit is used for running the program, collecting actual running information of the program from the buried point position, judging whether the program is abnormal or not according to the actual running information, wherein the actual running information comprises: input information, output information, positioning position information and stack abnormality information;
the injected dynamic byte code acquires program input information, output information, positioning position and stack abnormal information according to the embedded point, and carries out structural processing and storage on the input information, the output information, the positioning position and the stack abnormal information according to definition.
6. The program call link monitoring implementation apparatus according to claim 5, wherein the data analysis unit includes:
the comparison module is used for comparing the actual running information with a prestored expected program running result;
and the abnormality judging module is used for judging that if the actual running information is inconsistent with the expected program running result, the program is abnormal.
7. The program call link monitoring implementation apparatus according to claim 5, further comprising:
and the expected generation unit is used for determining the corresponding expected program running result after the program runs according to the program and storing the expected program running result.
8. The program call link monitoring implementation apparatus according to claim 5, further comprising:
the information acquisition rule configuration unit is used for configuring corresponding acquisition information rules according to the types of the programs, and the dynamic byte codes acquire actual running information of the programs according to the acquisition information rules.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of implementing program call link monitoring based on byte code injection techniques of any one of claims 1 to 4 when the program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed by a processor, implements the program call link monitoring implementation method based on the bytecode injection technique as claimed in any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011062468.5A CN112162908B (en) | 2020-09-30 | 2020-09-30 | Method and device for realizing program call link monitoring based on byte code injection technology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011062468.5A CN112162908B (en) | 2020-09-30 | 2020-09-30 | Method and device for realizing program call link monitoring based on byte code injection technology |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112162908A CN112162908A (en) | 2021-01-01 |
| CN112162908B true CN112162908B (en) | 2024-03-26 |
Family
ID=73860899
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011062468.5A Active CN112162908B (en) | 2020-09-30 | 2020-09-30 | Method and device for realizing program call link monitoring based on byte code injection technology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112162908B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114445088A (en) * | 2022-01-13 | 2022-05-06 | 内蒙古蒙商消费金融股份有限公司 | Method and device for judging fraudulent conduct, electronic equipment and storage medium |
| CN114706733B (en) * | 2022-05-30 | 2022-09-20 | 支付宝(杭州)信息技术有限公司 | Section program abnormity monitoring method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102018127317B3 (en) * | 2018-11-01 | 2020-04-09 | Infineon Technologies Ag | METHOD AND DEVICES FOR COMPUTER-IMPLEMENTED GENERATION OF AN EXECUTABLE PROGRAM CODE AND FOR EXECUTING AN EXECUTABLE PROGRAM CODE |
| CN111124906A (en) * | 2019-12-17 | 2020-05-08 | 支付宝(杭州)信息技术有限公司 | Tracking method, compiling method and device based on dynamic embedded points and electronic equipment |
| CN111427738A (en) * | 2019-01-09 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Display method, application monitoring module, bytecode enhancement module and display system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150309813A1 (en) * | 2012-08-31 | 2015-10-29 | iAppSecure Solutions Pvt. Ltd | A System for analyzing applications in order to find security and quality issues |
| US10599551B2 (en) * | 2016-08-12 | 2020-03-24 | The University Of Chicago | Automatically detecting distributed concurrency errors in cloud systems |
-
2020
- 2020-09-30 CN CN202011062468.5A patent/CN112162908B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102018127317B3 (en) * | 2018-11-01 | 2020-04-09 | Infineon Technologies Ag | METHOD AND DEVICES FOR COMPUTER-IMPLEMENTED GENERATION OF AN EXECUTABLE PROGRAM CODE AND FOR EXECUTING AN EXECUTABLE PROGRAM CODE |
| CN111427738A (en) * | 2019-01-09 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Display method, application monitoring module, bytecode enhancement module and display system |
| CN111124906A (en) * | 2019-12-17 | 2020-05-08 | 支付宝(杭州)信息技术有限公司 | Tracking method, compiling method and device based on dynamic embedded points and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112162908A (en) | 2021-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104391795B (en) | Method and system for automatically testing coverage rate in distributed system | |
| CN103150249B (en) | A kind of method and system of automatic test | |
| US20120116561A1 (en) | Program testing apparatus, method of testing a program, and program testing program | |
| Chen et al. | UML activity diagram-based automatic test case generation for Java programs | |
| CN112162908B (en) | Method and device for realizing program call link monitoring based on byte code injection technology | |
| CN104407973A (en) | Automatic unit test realizing method and device | |
| CN102053906A (en) | System and method for collecting program runtime information | |
| CN103019942B (en) | Method and system for automatically testing applications to be tested based on android system | |
| CN105512036A (en) | Test template for automatically generating test case according to preset rules and test method | |
| WO2011060655A1 (en) | Statistical method and system for software business functional coverage | |
| CN104820640A (en) | Webpage testing method and device | |
| CN106991046B (en) | Application testing method and device | |
| CN103186463B (en) | Determine the method and system of the test specification of software | |
| KR20200007133A (en) | Method and apparatus for dinamically injecting fault for vehicle ecu software test | |
| CN102495802A (en) | Method and device for testing software system, and computer system | |
| US7895580B1 (en) | Application tracing service employing different levels of precision for modifying bytecode | |
| CN105279092A (en) | Software testing method and apparatus | |
| CN112054822A (en) | Bluetooth test method and device, electronic equipment and storage medium | |
| Ubayashi et al. | Context-dependent product line practice for constructing reliable embedded systems | |
| CN113220597B (en) | Test method, test device, electronic equipment and storage medium | |
| CN112612697A (en) | Software defect testing and positioning method and system based on byte code technology | |
| CN111142469B (en) | Debugging method and debugging system for PLC configuration program | |
| CN109491882B (en) | Case data processing method and system, equipment case and readable storage medium | |
| CN111352668A (en) | Device testing method and device based on plug-in and testing system based on plug-in | |
| CN101582050A (en) | Bug prompt method in software test and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |