CN112162908A - Program call link monitoring implementation method and device based on bytecode injection technology - Google Patents

Program call link monitoring implementation method and device based on bytecode injection technology Download PDF

Info

Publication number
CN112162908A
CN112162908A CN202011062468.5A CN202011062468A CN112162908A CN 112162908 A CN112162908 A CN 112162908A CN 202011062468 A CN202011062468 A CN 202011062468A CN 112162908 A CN112162908 A CN 112162908A
Authority
CN
China
Prior art keywords
program
information
call link
expected
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.)
Granted
Application number
CN202011062468.5A
Other languages
Chinese (zh)
Other versions
CN112162908B (en
Inventor
陆建艳
张彦祥
黄震人
吴刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202011062468.5A priority Critical patent/CN112162908B/en
Publication of CN112162908A publication Critical patent/CN112162908A/en
Application granted granted Critical
Publication of CN112162908B publication Critical patent/CN112162908B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3051Monitoring 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
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/362Software debugging
    • G06F11/3644Software debugging by instrumenting at runtime

Abstract

The invention provides a program call link monitoring realization method and a device 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 monitoring program calling link into a buried point position; and running the program, acquiring 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. According to the method and the device, a bytecode injection technology is utilized, and codes are injected in a specific position of an operation program to be matched with a front-end visual control interface, so that the problem is quickly and accurately positioned and the program is friendly to show.

Description

Program call link monitoring implementation method and device based on bytecode injection technology
Technical Field
The present application belongs to the field of program monitoring technologies, and in particular, to a method and an apparatus for implementing program call link monitoring based on a bytecode injection technology.
Background
The traditional program testing environment is a pure black box environment for development, when a program BUG submitted by analysis and test is analyzed, analysis can be performed only by means of logs recorded in the program, and problems are difficult to troubleshoot when the logs are missing or not standardized, so that the root cause of the problems cannot be well positioned.
Disclosure of Invention
The application provides a program call link monitoring implementation method and device based on a bytecode injection technology, and aims to at least overcome the defects caused by the problem that the program can only be analyzed and checked by means of logs recorded in the program currently.
According to an aspect of the present application, there is also provided a method for implementing monitoring of a program call link 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 monitoring program calling link into a buried point position;
the method comprises the steps of running a program, collecting actual running information of the program from a buried point position, and judging whether the program is abnormal or not according to the actual running information, wherein the actual running information comprises the following steps: input information, output information, positioning position information and stacking abnormity information.
In one embodiment, determining whether an exception occurs in a program according to actual operation information includes:
comparing the actual operation information with an expected program operation result stored in advance;
and if the actual operation information is inconsistent with the expected program operation result, the program is abnormal.
In an embodiment, the method for implementing program call link monitoring further includes:
and determining an expected program operation result corresponding to the program 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 information acquisition rule according to the type of the program, and acquiring the actual running information of the program by the dynamic bytecode according to the information acquisition rule.
According to another aspect of the present application, there is also provided a device for implementing monitoring of a procedure call link based on a bytecode injection technology, including:
the embedded point determining unit is used for selecting the embedded point position where the dynamic byte codes need to be injected in the program;
the dynamic byte code injection unit is used for injecting the dynamic byte code for the monitoring program calling link into a buried point position;
the data analysis unit is used for running the program, acquiring 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 stacking abnormity information.
In one embodiment, the data analysis unit includes:
the comparison module is used for comparing the actual operation information with an expected program operation result which is stored in advance;
and the abnormality judging module is used for judging that the program is abnormal if the actual running information is inconsistent with the expected program running result.
In an embodiment, the program call link monitoring implementation apparatus further includes:
and the expected generating unit is used for determining an expected program operation result corresponding to the program 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 apparatus further includes:
and the information acquisition rule configuration unit is used for configuring a corresponding information acquisition rule according to the type of the program, and the dynamic byte code acquires the actual operation information of the program according to the information acquisition rule.
According to the method and the device, a bytecode injection technology is utilized, codes are injected at specific positions in a program, and a front-end visual control interface is matched, so that the function of quickly and accurately positioning problems can be realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of a method for implementing monitoring of a procedure call link based on a bytecode injection technology according to the present application.
Fig. 2 is a flowchart illustrating determining whether a program is abnormal according to actual operation information in an embodiment of the present application.
Fig. 3 is a block diagram of a structure of a device for implementing monitoring of a procedure call link based on a bytecode injection technology according to the present application.
Fig. 4 is a block diagram of a data analysis unit in the embodiment of the present application.
Fig. 5 is a system for implementing program call link monitoring provided in this embodiment.
Fig. 6 is a specific implementation of an electronic device in an embodiment of the present application.
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.
At present, analyzing program bug in traditional test environment, under the condition that log is not perfect enough and bottom technology stack is abnormal, the root of problem can not be specifically positioned, in order to solve the problem, the application provides a program call link monitoring implementation method based on bytecode injection technology, as shown in fig. 1, including:
s101: the location of the buried point where the dynamic bytecode needs to be injected is selected in the program.
In one embodiment, dynamic byte codes are inserted into nodes of a program, where the dynamic byte codes are inserted, called buried point locations, and the selected nodes are usually problematic nodes.
S102: and injecting dynamic byte codes for the calling link of the monitoring program into the buried point position.
In one embodiment, the injected dynamic bytecode is based on buried point acquisition program input, output, program exception location, exception stack information, etc., and then structured processing and storing these data by definition.
S103: and running the program, acquiring 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 and stacking abnormity information.
In an embodiment, determining whether an exception occurs in a program according to actual operation information, as shown in fig. 2, includes:
s201: and comparing the actual operation information with the expected program operation result stored in advance.
S202: and if the actual operation information is inconsistent with the expected program operation result, the program is abnormal.
In a specific embodiment, the actual running information collected by the injected dynamic bytecode is filtered, received and structured, and then the actual running information is analyzed, information such as program input parameter data and output result data is explicitly defined according to the previously defined granularity and atomicity requirements, and then the information is matched with an expected program running result, wherein the expected program running information includes a program data request, an expected data return result, an abnormal stack type and the like. If the actual operation information of the program is not matched with the expected program operation result, or the program stack is abnormal, the transaction is overtime and the like, the conclusion of the transaction can be judged and classified, and various potential performance problems of the program can be pre-judged and displayed to technical personnel.
In an embodiment, the method for implementing program call link monitoring further includes:
and determining an expected program operation result corresponding to the program 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 information acquisition rule according to the type of the program, and acquiring the actual running information of the program by the dynamic bytecode according to the information acquisition rule.
Based on the same inventive concept, the embodiment of the present application further provides a device for implementing monitoring of a procedure call link based on a bytecode injection technology, which can be used to implement the method described in the above embodiment, as described in the following embodiment. Because the principle of the device for realizing the monitoring of the program call link based on the bytecode injection technology is similar to the method for realizing the monitoring of the program call link based on the bytecode injection technology, the implementation of the device for realizing the monitoring of the program call link based on the bytecode injection technology can refer to the implementation of the method for realizing the monitoring of the program call link based on the bytecode injection technology, and repeated parts are not described again. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. While the system described in the embodiments below is preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
As shown in fig. 3, the present application provides a device for implementing monitoring of a procedure call link based on a bytecode injection technology, including:
a buried point determining unit 301, configured to select a buried point position where a dynamic bytecode needs to be injected in a program;
a dynamic bytecode injection unit 302, configured to inject a dynamic bytecode for monitoring program call link into a buried point location;
the data analysis unit 303 is configured to run the program, collect actual running information of the program from the buried point position, 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 and stacking abnormity information.
In one embodiment, as shown in fig. 4, the data analysis unit 303 includes:
a comparison module 401, configured to compare actual operation information with an expected program operation result stored in advance;
and an exception judgment module 402, configured to determine that the program is abnormal if the actual running information is inconsistent with the expected program running result.
In an embodiment, the program call link monitoring implementation apparatus further includes:
and the expected generating unit is used for determining an expected program operation result corresponding to the program 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 apparatus further includes:
and the information acquisition rule configuration unit is used for configuring a corresponding information acquisition rule according to the type of the program, and the dynamic byte code acquires the actual operation information of the program according to the information acquisition rule.
In a specific embodiment, the present application provides a set of program call link monitoring implementation system based on bytecode injection technology, and the system includes a parameter setting module 1, an information acquisition module 2, a data analysis module 3, and a result processing module 4, as shown in fig. 5. 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; and the data monitoring center 6 completes information interaction with the program code 5 deployed by the buried point by calling the result processing module 4.
Parameter setting module 1: the system 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 collecting transaction granularity, atomicity and transaction starting and ending time. The program model definition unit is mainly a program definition type, such as serial procedural, multi-thread concurrency, and the like.
The information acquisition module 2: the system mainly comprises an information buried unit, an information acquisition unit, an information receiving unit and an information storage unit. The information embedded point unit mainly makes a virtual request for the operation control so as to acquire information by the acquisition unit, and the information acquisition unit mainly acquires program input and output, program abnormal positioning positions, abnormal stack abnormal information and the like according to embedded points; 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.
The data analysis module 3: the method mainly comprises a model analysis unit, wherein the model analysis unit is used for analyzing basic information required by model definition, parameter definition analysis and problem positioning, specifically defining information such as program input parameter data and output result data according to granularity and atomicity definition requirements, and then matching with the set dimension of the model, and the model comprises a program data request, an expected data return result, an 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 units of programs. And the result information pushing unit returns specific result content according to the user requirement.
According to the method and the device, a bytecode injection technology is utilized, and codes are injected in a specific position of an operation program to be matched with a front-end visual control interface, so that the problem is quickly and accurately positioned and the program is friendly to show. The graphical display and the message pushing are technically realized through dynamic byte code specific position point burying, event acquisition, acquired information storage and analysis and the like. Through key information and request-level data information such as buried point acquisition information, information storage analysis and page processing display which are closely related to the test positioning problem, the problem analysis result data which is more close to the test requirement can be acquired, the problem root cause can be positioned more accurately, problem automatic monitoring display and analysis are achieved, and the analysis mode of the manual machine is eliminated.
As will be appreciated by one skilled in the art, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
An embodiment of the present application further provides a specific implementation manner of an electronic device, which is capable of implementing all steps in the method in the foregoing embodiment, and referring to fig. 6, the electronic device specifically includes the following contents:
a processor (processor)601, a memory 602, a communication Interface 603, a bus 604, and a non-volatile memory 605;
the processor 601, the memory 602, and the communication interface 603 complete mutual communication through the bus 604;
the processor 601 is configured to call the computer programs in the memory 602 and the nonvolatile memory 605, and when the processor executes the computer programs, the processor implements all the steps in the method in the foregoing embodiments, for example, when the processor executes the computer programs, the processor implements the following steps:
s101: the location of the buried point where the dynamic bytecode needs to be injected is selected in the program.
S102: and injecting dynamic byte codes for the calling link of the monitoring program into the buried point position.
S103: and running the program, acquiring 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.
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, where the computer-readable storage medium stores thereon a computer program, and the computer program 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 location of the buried point where the dynamic bytecode needs to be injected is selected in the program.
S102: and injecting dynamic byte codes for the calling link of the monitoring program into the buried point position.
S103: and running the program, acquiring 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 in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment. Although embodiments of the present description provide method steps as described in embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or 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, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded. For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the embodiments of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description 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 so forth) having computer-usable program code embodied therein. The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean 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 an embodiment of the specification.
In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction. The above description is only an example of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure. Various modifications and variations to the embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle 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. A program call link monitoring implementation method based on 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 monitoring program calling link into the buried point position;
running a program, acquiring 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 stacking abnormity information.
2. The method for implementing program call link monitoring according to claim 1, wherein the determining whether the program is abnormal according to the actual operation information includes:
comparing the actual operation information with an expected program operation result stored in advance;
and if the actual operation information is inconsistent with the expected program operation result, the program is abnormal.
3. The method for implementing procedure call link monitoring according to claim 1, further comprising:
and determining an expected program operation result corresponding to the program after the program is operated according to the program, and storing the expected program operation result.
4. The method for implementing procedure call link monitoring according to claim 1, further comprising:
and configuring a corresponding information acquisition rule according to the type of the program, and acquiring the actual running information of the program by the dynamic bytecode according to the information acquisition rule.
5. A program call link monitoring implementation device based on byte code injection technology is characterized by comprising the following components:
the embedded point determining unit is used for selecting the embedded point position where the dynamic byte codes need to be injected in the program;
the dynamic byte code injection unit is used for injecting dynamic byte codes for a monitoring program calling link into the buried point position;
the data analysis unit is used for running a program, acquiring 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 stacking abnormity information.
6. The apparatus of claim 5, wherein the data analysis unit comprises:
the comparison module is used for comparing the actual operation information with an expected program operation result which is stored in advance;
and the abnormal judgment module is used for judging that the program is abnormal if the actual operation information is inconsistent with the expected program operation result.
7. The apparatus for implementing procedure call link monitoring according to claim 5, further comprising:
and the expected generating unit is used for determining an expected program operation result corresponding to the program after the program is operated according to the program and storing the expected program operation result.
8. The apparatus for implementing procedure call link monitoring according to claim 5, further comprising:
and the information acquisition rule configuration unit is used for configuring a corresponding information acquisition rule according to the type of the program, and the dynamic byte code acquires the actual operation information of the program according to the information acquisition rule.
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 for implementing bytecode injection technology-based program call link monitoring as claimed in any one of claims 1 to 4 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the bytecode injection technology-based procedure call link monitoring implementation method of any of claims 1 to 4.
CN202011062468.5A 2020-09-30 2020-09-30 Method and device for realizing program call link monitoring based on byte code injection technology Active CN112162908B (en)

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 true CN112162908A (en) 2021-01-01
CN112162908B 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)

Cited By (2)

* Cited by examiner, † Cited by third party
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
CN114706733A (en) * 2022-05-30 2022-07-05 支付宝(杭州)信息技术有限公司 Section program abnormity monitoring method and device

Citations (5)

* Cited by examiner, † Cited by third party
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
US20180046565A1 (en) * 2016-08-12 2018-02-15 Futurewei Technologies, Inc. Automatically detecting distributed concurrency errors in cloud systems
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

Patent Citations (5)

* Cited by examiner, † Cited by third party
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
US20180046565A1 (en) * 2016-08-12 2018-02-15 Futurewei Technologies, Inc. Automatically detecting distributed concurrency errors in cloud systems
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

Cited By (2)

* Cited by examiner, † Cited by third party
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
CN114706733A (en) * 2022-05-30 2022-07-05 支付宝(杭州)信息技术有限公司 Section program abnormity monitoring method and device

Also Published As

Publication number Publication date
CN112162908B (en) 2024-03-26

Similar Documents

Publication Publication Date Title
CN106844217B (en) Method and device for embedding point of applied control and readable storage medium
US9483390B2 (en) Three-dimensional GUI object stores in automation test tools
CN111756575B (en) Performance analysis method and device of storage server and electronic equipment
CN103150249B (en) A kind of method and system of automatic test
CN110347085B (en) Automated test system, method, vehicle, and computer-readable medium
CN106681701B (en) Task display method and device
CN105446868A (en) System compatibility testing method, test case management method and related devices
CN111488109A (en) Method, device, terminal and storage medium for acquiring control information of user interface
CN103186463B (en) Determine the method and system of the test specification of software
CN112162908A (en) Program call link monitoring implementation method and device based on bytecode injection technology
CN111106965B (en) Intelligent log analysis method, tool, equipment and medium for complex system
CN111190825A (en) Automatic test method, system and robot
CN110554962A (en) Regression testing process covering method, server and computer readable storage medium
CN111144839A (en) Project construction method, continuous integration system and terminal equipment
CN112612697A (en) Software defect testing and positioning method and system based on byte code technology
CN111352668A (en) Device testing method and device based on plug-in and testing system based on plug-in
CN110990177A (en) Fault repairing method, device, system, storage medium and electronic equipment
CN111475394A (en) Application testing method and device
CN113157528A (en) Operation change monitoring method and device based on big data service cloud
CN114003457A (en) Data acquisition method and device, storage medium and electronic equipment
CN114238130A (en) Performance test method, device, equipment and storage medium
CN113326193A (en) Applet testing method and device
CN112346981A (en) Joint debugging test coverage rate detection method and system
CN112363870B (en) Application program development processing method and device, computer equipment and storage medium
CN117632700A (en) Task testing method, device, system, equipment and 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
GR01 Patent grant
GR01 Patent grant