CN117632217A - Crash information processing method, device, terminal, server and storage medium - Google Patents

Crash information processing method, device, terminal, server and storage medium Download PDF

Info

Publication number
CN117632217A
CN117632217A CN202210952163.4A CN202210952163A CN117632217A CN 117632217 A CN117632217 A CN 117632217A CN 202210952163 A CN202210952163 A CN 202210952163A CN 117632217 A CN117632217 A CN 117632217A
Authority
CN
China
Prior art keywords
information
crash
program
software development
development kit
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
Application number
CN202210952163.4A
Other languages
Chinese (zh)
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.)
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
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 Beijing Jingdong Century Trading Co Ltd, Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN202210952163.4A priority Critical patent/CN117632217A/en
Publication of CN117632217A publication Critical patent/CN117632217A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the invention discloses a crash information processing method, a device, a terminal, a server and a storage medium. The method is applied to the client and comprises the following steps: responding to a crash information acquisition instruction, and acquiring crash information of a host program in the running process; adding the obtained target information into the crash information, and updating the crash information, wherein the target information comprises first version information of the SDK, program version information of a host program and identification information; and reporting the crash information to a package server corresponding to the SDK, so that the package server sends the repair information to a program server corresponding to a host program with identification information in the crash information, wherein the repair information comprises first version information and program version information determined from the crash information and second version information of the repaired SDK obtained after the SDK is repaired according to the crash information. The technical scheme of the embodiment of the invention can enable the host program to better apply the repair result.

Description

Crash information processing method, device, terminal, server and storage medium
Technical Field
The embodiment of the invention relates to the technical field of computer application, in particular to a crash information processing method, a device, a terminal, a server and a storage medium.
Background
Through the development and precipitation of the internet for years, the industry is huge and profound, and various industries are powered on, and a large part of the internet is provided for external Application programs (APP) in the form of software development kits (Software Development Kit, SDKs). In practical applications, an APP having an SDK attached thereto may be referred to as a host program of the SDK.
In order to ensure the application performance of the SDK, the SDK can internally capture the crash information of a host program in the running process, and then report the crash information to a server of the SDK, so that the server can check the crash points in the SDK according to the received crash information, and a developer can repair the checked crash points.
In the process of realizing the invention, the inventor finds that the following technical problems exist in the prior art: the repair result cannot be well applied by the host program.
Disclosure of Invention
The embodiment of the invention provides a crash information processing method, a device, a terminal, a server and a storage medium, which solve the problem that a repair result cannot be well applied by a host program.
According to an aspect of the present invention, there is provided a crash information processing method applied to a client corresponding to a software development kit, the method including:
responding to a crash information acquisition instruction, and acquiring crash information of a host program in the running process, wherein the host program is an application program accessed with a software development kit;
obtaining target information, adding the target information into the crash information, and updating the crash information according to an adding result, wherein the target information comprises first version information of a software development kit, program version information of a host program and identification information;
and reporting the crash information to a package server corresponding to the software development kit, so that the package server sends the repair information to a program server corresponding to a host program with identification information in the crash information, wherein the repair information comprises first version information and program version information determined from the crash information and second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information.
According to another aspect of the present invention, there is provided a crash information processing method applied to a package service end corresponding to a software development kit, the method may include:
Receiving crash information reported by a client corresponding to a software development kit, wherein the crash information comprises information of a host program accessed with the software development kit and added with target information in the running process, and the target information comprises first version information of the software development kit, program version information and identification information of the host program;
acquiring second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information, and taking the first version information and the program version information determined from the crash information and the second version information as repair information;
and sending the repair information to a program server corresponding to the host program with the identification information in the crash information.
According to another aspect of the present invention, there is provided a crash information processing apparatus configured at a client corresponding to a software development kit, the apparatus may include:
the crash information acquisition module is used for responding to a crash information acquisition instruction and acquiring crash information of a host program in the running process, wherein the host program is an application program accessed with a software development kit;
The system comprises a target information adding module, a crash information updating module and a program information updating module, wherein the target information adding module is used for obtaining target information, adding the target information into the crash information and updating the crash information according to an adding result, and the target information comprises first version information of a software development kit, program version information of a host program and identification information;
the system comprises a crash information reporting module, a software development kit and a software development kit, wherein the crash information reporting module is used for reporting the crash information to a package server corresponding to the software development kit so that the package server can send repair information to a program server corresponding to a host program with identification information in the crash information, and the repair information comprises first version information and program version information determined from the crash information and second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information.
According to another aspect of the present invention, there is provided a crash information processing apparatus configured at a package service end corresponding to a software development kit, the apparatus comprising:
the system comprises a crash information receiving module, a program execution module and a program execution module, wherein the crash information receiving module is used for receiving crash information reported by a client corresponding to a software development kit, wherein the crash information comprises information which is added with target information and appears in the running process of a host program accessed with the software development kit, and the target information comprises first version information of the software development kit, program version information and identification information of the host program;
The repair information obtaining module is used for obtaining second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information, and taking the first version information and the program version information determined from the crash information and the second version information as repair information;
and the repair information sending module is used for sending the repair information to a program server corresponding to the host program with the identification information in the crash information.
According to another aspect of the present invention, there is provided a terminal, which may include:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to implement, when executed, a crash information processing method provided by any embodiment of the present invention as applied to a client corresponding to a software development kit.
According to another aspect of the present invention, there is provided a package server, which may include:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
The memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to implement, when executed, a crash information processing method provided by any embodiment of the present invention and applied to a package server corresponding to a software development kit.
According to another aspect of the present invention, there is provided a computer readable storage medium having stored thereon computer instructions for causing a processor to implement the crash information processing method provided by any embodiment of the present invention when executed.
According to the technical scheme, the crash information of the host program accessed with the SDK in the running process is obtained by responding to the crash information obtaining instruction; because the obtained crash information can only show the crash cause, but cannot show the crash object, namely what host program is what version of the host program is crashed, what version of the SDK is imported into the host program, in order to enable the host program to better apply the repaired SDK, adding the obtained target information (namely the first version information of the SDK, the program version information and the identification information of the host program) which can show the crash object into the crash information, and updating the crash information according to the adding result; then, the crash information is reported to the packet server where the SDK is located, so that the packet server can determine a specific host program according to the identification information obtained from the crash information, and then send corresponding repair information (namely, the first version information and the program version information determined from the crash information and the second version information of the repaired SDK) obtained after repairing the SDK according to the crash information to the determined program server where the host program is located, so that the host program can better apply the repaired SDK according to the repair information received by the program server. By the technical scheme, the effect that the repaired SDK can be well applied by a host program is achieved.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention, nor is it intended to be used to limit the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a crash information processing method provided in accordance with an embodiment of the present invention;
FIG. 2 is a first schematic diagram of an alternative example of a crash information processing method according to an embodiment of the present invention;
FIG. 3 is a flow chart of another crash information processing method provided in accordance with an embodiment of the invention;
FIG. 4 is a second schematic diagram of an alternative example of another crash information processing method provided in accordance with an embodiment of the invention;
FIG. 5 is a third schematic diagram of an alternative example of another crash information processing method provided in accordance with an embodiment of the invention;
FIG. 6 is a flow chart of another crash information processing method provided in accordance with an embodiment of the invention;
FIG. 7 is a block diagram of a crash information processing apparatus provided in accordance with an embodiment of the present invention;
FIG. 8 is a block diagram of another crash information processing apparatus provided in accordance with an embodiment of the invention;
fig. 9 is a schematic structural diagram of a terminal or a packet server implementing the crash information processing method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. The cases of "target", "original", etc. are similar and will not be described in detail herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
FIG. 1 is a flow chart of a crash information processing method according to an embodiment of the present invention. The present embodiment is applicable to a case where a repair result for an SDK corresponding to crash information acquired inside the SDK is applied by a host program. The method can be performed by the crash information processing device provided by the embodiment of the invention, the device can be realized by software and/or hardware, and the device can be integrated on a terminal deployed with a client corresponding to the SDK.
Referring to fig. 1, the method of the embodiment of the present invention specifically includes the following steps:
s110, responding to a crash information acquisition instruction, and acquiring crash information of a host program in the running process, wherein the host program is an application program accessed with a software development kit.
The crash information obtaining instruction may include an instruction for obtaining crash information of a host program in a running process, where the host program may be an APP having an SDK, and the SDK may be understood as a set of development tools used by a software engineer to build application software for a specific software package, a software framework, a hardware platform, an operating system, and the like; the crash information may be information that the host program has occurred when it crashed (i.e., suddenly exited) during execution, and in actual use, may optionally include information about the flow performed before the crash and information about the actions performed at the time of the crash.
And responding to the crash information acquisition instruction, and acquiring the crash information inside the SDK. In practical applications, the crash information may be obtained from a crash stack. By way of example, assume that 20 books are placed in a list of books, and the book is found in the list of books by calling the function findbook. When the 1 st book is searched, the problem of out-of-range array occurs, the host program throws out the crash information outwards and stores the crash information in a crash stack, and the crash information at this time can comprise information related to the searching flow of the previous 20 books and information related to out-of-range findbook array when the 21 st book is searched. Then the SDK may obtain crash information from the crash stack.
It should be noted that, the crash information acquired by the SDK is the crash information of the whole host program, and the crash of the host program may be caused by the crash of the host program itself or may be caused by the crash of the SDK that is accessed into the host program, so the crash information acquired by the SDK may belong to the host program or may belong to the SDK, which is related to the actual situation, and is not specifically limited herein. On the basis, optionally, after the SDK acquires the crash information, whether the SDK belongs to the SDK can be determined, if so, the following steps are carried out, otherwise, the SDK jumps out; of course, the following steps may be performed no matter whether the crash information belongs to the SDK itself, and then the packet server where the SDK is located determines whether the received crash information belongs to the SDK, if so, the crash point in the SDK is checked, otherwise, the checking operation is not required to be performed.
S120, obtaining target information, adding the target information into the crash information, and updating the crash information according to an adding result, wherein the target information comprises first version information of a software development kit, program version information of a host program and identification information.
The target information may include first version information of the SDK currently accessed into the host program, and program version information and identification information of the host program, where the identification information may be information for uniquely identifying the host program, and in practical application, may optionally be represented by a package name, because the package name of each host program is unique in the android system or the apple system.
It should be noted that, the crash information obtained by the SDK can only show the crash cause, but cannot show the crash object, that is, who has crashed, specifically what host program is what version of the crashed host program (at least two versions may exist in one host program, and one SDK may be accessed into a different host program), what version of the SDK is accessed therein (at least two versions may exist in one SDK), so the object information may be added to the crash information, so that who the crash object is can be determined according to the added crash information, which is matched with the subsequent steps, and is helpful for applying the repairing result provided by the package service end to the crashed host program.
S130, reporting the crash information to a package server corresponding to the software development kit, so that the package server sends the repair information to a program server corresponding to a host program with identification information in the crash information, wherein the repair information comprises first version information and program version information determined from the crash information, and second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information.
And reporting the crash information (here, the crash information added with the target information) to the package server, and when the crash information received by the package server belongs to the SDK, checking out a crash point in the SDK according to the crash information, and repairing the crash point by a developer, thereby obtaining a repairing result and repairing information. The repair result may be understood as a repaired SDK obtained after repairing the SDK according to the crash information, and the repair information may include first version information and program version information determined from the crash information, and second version information of the repaired SDK. Further, since the host program with the crash can be uniquely determined according to the identification information in the crash information, the package server can send the repair information to the program server corresponding to the host program, so that the host program can better apply the repair result.
The program server side can determine what version of the host program is accessed to what version of the SDK has crashed according to the received repair information or the repair information displayed by the developer of the host program according to the repair information displayed by the program server side, so as to determine what version of the SDK has been accessed in the latest version of the host program, where the latest version of the host program may be the host program with crashed or may be the host program after the crashed host program has been upgraded. Further, if the SDK before repair (i.e., corresponding to the first version information) is accessed in the host program of the latest version, the host program of the latest version is upgraded to access the SDK after repair (i.e., corresponding to the second version information); otherwise, the host program of the latest version is not required to be updated. In other words, in either case, the host program (precisely, the latest version of the host program) can be applied to the repaired SDK.
In order to better understand the above technical solution, an exemplary description thereof is provided below in connection with specific examples. For example, referring to fig. 2, when it is obtained from the crash stack that the crash information belongs to the SDK, the first version information (e.g., V1.0.0) of the SDK currently accessed may be obtained, and the package name (e.g., com.aa.app.mall) of the host program accessing the SDK and the program version information (e.g., V5.9.0) may be obtained. Assuming that the obtained crash information is mysdk_aa, after adding the target information thereto, mysdk_ V1.0.0_com.aa.app.mall_ V5.9.0_aa can be obtained, here divided by three short underlines, labeled: mysdk: SDK alias, V1.0.0: first version information, com.aa.app.mall: package name, V5.9.0: second version information. And then, reporting the added crash information.
According to the technical scheme, the crash information of the host program accessed with the SDK in the running process is obtained by responding to the crash information obtaining instruction; because the obtained crash information can only show the crash cause, but cannot show the crash object, namely what host program is what version of the host program is crashed, what version of the SDK is imported into the host program, in order to enable the host program to better apply the repaired SDK, adding the obtained target information (namely the first version information of the SDK, the program version information and the identification information of the host program) which can show the crash object into the crash information, and updating the crash information according to the adding result; then, the crash information is reported to the packet server where the SDK is located, so that the packet server can determine a specific host program according to the identification information obtained from the crash information, and then send corresponding repair information (namely, the first version information and the program version information determined from the crash information and the second version information of the repaired SDK) obtained after repairing the SDK according to the crash information to the determined program server where the host program is located, so that the host program can better apply the repaired SDK according to the repair information received by the program server. By the technical scheme, the effect that the repaired SDK can be well applied by a host program is achieved.
On the basis, an optional technical scheme for acquiring the target information can comprise the following steps: acquiring first version information; acquiring environment variable information transmitted by a host program, and determining program version information and identification information according to the environment variable information; the first version information, the program version information, and the identification information are taken as target information. The SDK may directly obtain the own first version information. The host program may be understood as a software environment in which the SDK is located, and thus program version information and identification information of the host program may be determined by environment variable information transferred from the host program. In practical applications, the environment variable information may optionally include variable information that is transferred to the SDK before the host program uses the relevant functions of the SDK to inform the software environment in which it is located. Then, the first version information, the program version information and the identification information are used as target information, so that the effect of quickly acquiring the target information is achieved.
Another alternative solution, obtaining crash information that occurs in the running process of the host program may include: intercepting crash information of a host program in the running process to obtain the crash information; after obtaining the crash information, the crash information processing method may further include: the crash information is passed back to the host program. When the host program crashes in the running process, crash information can be thrown outwards. The SDK can intercept the crash information thrown by the host program, thereby acquiring the crash information. In practical application, optionally, in order to implement the above-mentioned interception process of crash information, the following operations may be performed in advance: for the SDK integrated in the host program, since the host program is externally exposed with an interface, the host program can transmit the environment variable information to the SDK through the interface, so that the SDK is initialized according to the received environment variable information, and an interceptor is registered after the initialization is finished, so that crash information thrown outwards by the host program is intercepted based on the interceptor. It should be noted that, the crash information intercepted by the SDK may belong to the SDK or may belong to the host program itself, and after the crash information is intercepted, a collector in the host program that needs to collect the crash information cannot collect the crash information. On the basis, in order to ensure the application performance of the host program, the program server side also needs to check the crash points in the host program, so that the SDK can transmit the intercepted crash information back to the host program, and the host program can report the received crash information to the program server side for crash point analysis. According to the technical scheme, the SDK can intercept the crash information and cannot influence the collection work of the host program on the crash information.
FIG. 3 is a flowchart of another crash information processing method according to an embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, acquiring the target information may include: if the crash information is information generated by the software development kit, the target information is obtained. Wherein, the explanation of the same or corresponding terms as the above embodiments is not repeated herein.
Referring to fig. 3, the method of this embodiment may specifically include the following steps:
s210, responding to a crash information acquisition instruction, and acquiring crash information of a host program in the running process, wherein the host program is an application program accessed with a software development kit.
S220, if the crash information is information generated by the software development kit, acquiring target information.
The crash information may be information that occurs during the running process of the host program, and may be information generated by the host program itself (i.e., information generated due to the crash of the host program itself), or may be information generated by the SDK that is accessed in the host program (i.e., information generated due to the crash of the SDK). On the basis, in order to improve the checking efficiency of the packet server for the crash point, the SDK can firstly determine whether the internally acquired crash information is the information generated by the SDK, and if so, the following steps are executed by acquiring the target information so that the crash information reported to the packet server is the information related to the SDK.
On the basis, optionally, whether the collapse information captured by the SDK is information generated by the SDK can be determined in various ways, for example, whether the function with the collapse is the function in the SDK is determined by determining the function name in the collapse information, so that whether the collapse information belongs to the SDK is determined, and the function can be understood as a function, a class, a variable and the like capable of realizing certain functions; determining whether the crash information belongs to the SDK or not by determining whether a target identifier related to the SDK exists in the crash information; etc., and are not particularly limited herein.
And S230, adding the target information into the crash information, and updating the crash information according to the adding result, wherein the target information comprises the first version information of the software development kit, and the program version information and the identification information of the host program.
S240, reporting the crash information to a package server corresponding to the software development kit, so that the package server sends the repair information to a program server corresponding to a host program with identification information in the crash information, wherein the repair information comprises first version information and program version information determined from the crash information, and second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information.
According to the technical scheme provided by the embodiment of the invention, whether the collapse information is generated by the SDK is determined, if so, the following steps are executed by acquiring the target information, so that the collapse information reported to the packet server is the information related to the SDK, and interference of the collapse information unrelated to the SDK on the process of checking the collapse point of the packet server can be avoided, and the efficiency of checking the collapse point by the packet server is ensured.
In order to better understand the above technical solutions as a whole, an exemplary description thereof is given below in connection with specific examples. For example, referring to fig. 4, before using the related function of the SDK, the host program transfers the environment variable information to the SDK through an interface exposed to the outside of the SDK, so that the SDK is initialized according to the received environment variable information, and after the initialization is finished, an interceptor is registered to intercept crash information thrown outward by the host program based on the interceptor. After intercepting the crash information, the SDK can firstly determine whether the crash information is the crash information generated by the SDK, if so, the obtained target information is added into the crash information, the added crash information is reported to a packet server for crash point analysis, and the crash information before being added is transmitted back to a host program; otherwise, the intercepted crash information is directly transmitted back to the host program. According to the technical scheme, the crash information belonging to the SDK can be reported to the package server for analysis of the crash point, and the collection work of the host program on the crash information is not affected.
On the basis, an optional technical scheme, the crash information processing method, may further include: and determining whether a target identifier exists in the collapse information, and if so, taking the collapse information as information generated by a software development kit, wherein the target identifier comprises an identifier which is confused into source code when the source code of the software development kit is confused. The crash information may be information that occurs when the host program crashes during the running process, and specifically may be information that is thrown outwards when a problem occurs in a line of code running in the host program, that is, the crash information may represent a problem code that occurs in the problem, as described above. In addition, for the source code of the written SDK, code obfuscation (e.g., converting the source code into a nonsensical combination of letters and symbols) may be performed, and the code obfuscation result may be compiled and then packaged, so that the packaged result is integrated into the host program to enable the host program to use the relevant functions of the SDK. On the basis, in order to enable the SDK to quickly and accurately determine whether the acquired crash information belongs to the SDK or not, when the source code of the SDK is subjected to code confusion, the target identification can be confused into the source code. In this way, if the crash information which can represent the problem code belongs to the SDK, the object identifier is naturally included in the crash information, so that whether the crash information belongs to the SDK can be determined by determining whether the object identifier exists in the acquired crash information, and the effect of quickly and accurately determining the attribution of the crash information is achieved.
For a better understanding of the present technical solution, an exemplary description thereof is given below in connection with specific examples. Illustratively, as shown in fig. 5, the source code of the SDK is code-obfuscated based on a custom code obfuscating rule, for example, the code obfuscating rule defines that the function name of the function findbook is converted into aa, and the target identifier mysdk_ is added thereto, so that the obfuscated code obtained after the code obfuscating of the function findbook may be mysdk_aa, which means that when a problem occurs in invoking the function findbook, mysdk_aa may be included in crash information generated thereby. Decompiling and packaging the code confusion result, and integrating the obtained packaging result into a host program. Therefore, after the SDK acquires the crash information, whether the crash information contains mysdk_ or not can be inquired in the crash stack storing the crash information, if so, the crash information is generated by the SDK, otherwise, the crash information is not generated by the SDK, and the effect of quickly and accurately determining whether the crash information acquired by the SDK is generated by self-crash is achieved.
FIG. 6 is a flowchart of another crash information processing method according to an embodiment of the present invention. The present embodiment is applicable to a case where a repair result for an SDK corresponding to crash information acquired inside the SDK is applied by a host program. The method can be executed by the crash information processing device provided by the embodiment of the invention, the device can be realized by software and/or hardware, and the device can be integrated on a package server deployed with a package service end corresponding to the SDK.
Referring to fig. 6, the method of the embodiment of the present invention specifically includes the following steps:
s310, receiving crash information reported by a client corresponding to a software development kit, wherein the crash information comprises information which is added with target information and occurs in the running process of a host program accessed with the software development kit, and the target information comprises first version information of the software development kit, program version information and identification information of the host program.
The package server receives the crash information reported by the client, and the target information in the crash information can show who the crash object is, namely what host program is what version the crash host program is, and what version the SDK is in, which is crucial to enable the repaired SDK to be better applied by the crash host program.
S320, obtaining second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information, and taking the first version information and the program version information determined from the crash information and the second version information as repair information.
The first version information and the program version information obtained from the crash information and the second version information of the repaired SDK are used as repair information, and the repair information can enable a program server side or a developer where the host program is located to quickly and accurately determine whether the host program of the latest version has accessed the repaired SDK, and further judge whether the host program of the latest version needs to be upgraded according to a determination result, so that the host program can be better applied to the repaired SDK.
S330, the repair information is sent to a program server corresponding to the host program with the identification information in the crash information.
The host program is the host program with the crash, so that the repair information can be sent to the program server where the host program is located, so that the host program can be better applied to the repaired SDK.
According to the technical scheme, the crash information reported by the client corresponding to the SDK is received, the crash information comprises information which is accessed to a host program with the SDK and added with target information in the running process, the target information comprises first version information of the SDK, program version information and identification information of the host program, and the target information in the received crash information can represent a crash object, namely what host program of what version the crashed host program is, and what version of the SDK which is accessed into the host program is; further, for the repaired SDK obtained after repairing the SDK according to the crash information, the second version information of the SDK can be obtained, and the first version information and the program version information determined from the crash information and the second version information are used as repair information; and then, determining a specific host program according to the identification information obtained from the crash information, and sending the repair information to a program server where the determined host program is located, so that the host program can better apply the repaired SDK according to the repair information received by the program server. By the technical scheme, the effect that the repaired SDK can be well applied by a host program is achieved.
On the basis, an optional technical scheme, the crash information processing method, may further include: analyzing the collapse information and checking out the collapse points in the software development kit; determining whether the crash point has been repaired according to the first version information; if yes, the software development kit corresponding to the repaired crash point is used as the repaired software development kit. The crash information is generated when the SDK crashes, so that after the received crash information is analyzed, the crash point in the SDK can be checked out. In practical applications, as described above, the crash information may represent the problem code in the SDK, so the crash point that is checked out after the crash information is analyzed may be the problem code. Since a certain version of SDK can be accessed into at least two hosts, when any one of the hosts crashes due to the same crash point, the packet server can receive the crash information for representing the crash point. However, the time points when the host programs crash may be different, which results in that the crash point reflected by the crash information currently received by the packet server may be a crash point that has been repaired, and such a crash point does not need to be repaired repeatedly. Thus, after a crash point is checked, it may be determined from the first version information in the crash information whether the crash point has been repaired, such as determining whether there is a higher version of the SDK that repaired the crash point based on the repair record. If so, the SDK with the repaired breakdown point can be directly used as the repaired SDK, so that the effect of accurately determining whether the checked breakdown point is repaired or not is achieved, and the situation of manpower waste caused by repeated repair of the same breakdown point is avoided.
In another alternative solution, analyzing the crash information to find crash points in the software development kit may include: obtaining a confusion file, wherein the confusion file is a file generated when the source codes of the software development kit are subjected to code confusion, the confusion file stores the mapping relation between the source codes and the confusion codes, and the confusion codes are source codes after the codes are mixed; analyzing the collapse information to obtain a first code with problems in the confusion code; and determining a second code corresponding to the first code in the source code according to the mapping relation in the confusion file, and checking out a crash point in the software development kit based on the second code. Because the mapping relationship between the active code and the confusion code is stored in the confusion file, for example, the function findbook before code confusion corresponds to the function aa after code confusion, when the first code with problems in the confusion code is obtained after the collapse information is analyzed, a second code corresponding to the first code in the source code can be determined based on the mapping relationship in the confusion file, and then the collapse point in the SDK is checked according to the second code, for example, the second code is directly used as the collapse point, and classes, functions and/or variables appearing in the second code are used as the collapse point, so that the effect of accurately checking the collapse point is achieved.
Fig. 7 is a block diagram of a crash information processing apparatus according to an embodiment of the present invention, which may be used to execute the crash information processing method according to any of the above embodiments. The device and the crash information processing method of each embodiment belong to the same invention conception, and the details of the embodiment of the crash information processing device, which are not described in detail, can be referred to the embodiment of the crash information processing method. Referring to fig. 7, the device is configured at a client corresponding to a software development kit, and specifically may include: a crash information acquisition module 410, a target information addition module 420, and a crash information reporting module 430.
The crash information obtaining module 410 is configured to obtain crash information that occurs in an operation process of a host program in response to a crash information obtaining instruction, where the host program is an application program that is accessed with a software development kit;
the target information adding module 420 is configured to obtain target information, add the target information to the crash information, and update the crash information according to an addition result, where the target information includes first version information of the software development kit, and program version information and identification information of the host program;
The crash information reporting module 430 is configured to report the crash information to a package server corresponding to the software development kit, so that the package server sends repair information to a program server corresponding to a host program with identification information in the crash information, where the repair information includes first version information and program version information determined from the crash information, and second version information of the repaired software development kit obtained after repairing the software development kit according to the crash information.
Optionally, the target information adding module 420 may include:
a first version information acquisition unit configured to acquire first version information;
the identification information determining unit is used for acquiring environment variable information transmitted by the host program and determining program version information and identification information according to the environment variable information;
the target information first acquisition unit is used for taking the first version information, the program version information and the identification information as target information.
Optionally, the target information adding module 420 may include:
and the second target information acquisition unit is used for acquiring the target information if the crash information is information generated by the software development kit.
On this basis, optionally, the crash information processing apparatus may further include:
the crash information attribution determining module is used for determining whether a target identifier exists in the crash information, and if so, the crash information is used as information generated by the software development kit, wherein the target identifier comprises an identifier which is confused into a source code when the source code of the software development kit is confused.
Optionally, the crash information obtaining module 410 may include:
the crash information obtaining unit is used for intercepting crash information occurring in the running process of the host program to obtain the crash information;
the crash information processing apparatus may further include:
and the crash information returning module is used for returning the crash information to the host program after the crash information is obtained.
According to the crash information processing device provided by the embodiment of the invention, the crash information acquisition module responds to the crash information acquisition instruction to acquire the crash information of the host program accessed with the SDK in the running process; the obtained crash information can only show the crash cause, but cannot show the crash object, namely what host program is in what version of the crashed host program, and what version of the SDK is in the host program, so that in order to enable the host program to better apply the repaired SDK, the obtained target information (namely the first version information of the SDK, the program version information and the identification information of the host program) which can show the crash object is added into the crash information through the target information adding module, and the crash information is updated according to the adding result; then, the crash information is reported to the package server where the SDK is located through the crash information reporting module, so that the package server can determine a specific host program according to the identification information obtained from the crash information, and then the corresponding repair information (namely the first version information and the program version information determined from the crash information and the second version information of the repaired SDK) obtained after repairing the SDK according to the crash information is sent to the determined program server where the host program is located, so that the host program can better apply the repaired SDK according to the repair information received by the program server. The device achieves the effect that the repaired SDK can be well applied by a host program.
The crash information processing device provided by the embodiment of the invention can execute the crash information processing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
It should be noted that, in the embodiment of the crash information processing apparatus, each unit and module included are only divided according to the functional logic, but not limited to the above-mentioned division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
FIG. 8 is a block diagram of another crash information processing apparatus according to an embodiment of the present invention, which is configured to execute the crash information processing method according to any of the above embodiments. The device and the crash information processing method of each embodiment belong to the same invention conception, and the details of the embodiment of the crash information processing device, which are not described in detail, can be referred to the embodiment of the crash information processing method. Referring to fig. 8, the device is configured at a package service end corresponding to a software development kit, and may specifically include: a crash information receiving module 510, a repair information obtaining module 520, and a repair information transmitting module 530.
The crash information receiving module 510 is configured to receive crash information reported by a client corresponding to a software development kit, where the crash information includes information, which appears in an operation process of a host program accessed with the software development kit and is added with target information, and the target information includes first version information of the software development kit, program version information and identification information of the host program;
the repair information obtaining module 520 is configured to obtain second version information of a repaired software development kit obtained after repairing the software development kit according to the crash information, and use the first version information and the program version information determined from the crash information, and the second version information as repair information;
the repair information sending module 530 is configured to send the repair information to a program server corresponding to the host program with the identification information in the crash information.
Optionally, the crash information processing apparatus may further include:
the crash point checking module is used for analyzing the crash information and checking out crash points in the software development kit;
the crash point determining module is used for determining whether the crash point is repaired according to the first version information;
And the software development kit obtaining module is used for taking the software development kit corresponding to the repaired crash point as the repaired software development kit if the software development kit is the repaired crash point.
On this basis, optionally, the crash point checking module may include:
the system comprises an confusion file acquisition unit, a code confusion unit and a code confusion unit, wherein the confusion file is a file generated when the source codes of the software development tool kit are subjected to code confusion, the confusion file stores the mapping relation between the source codes and the confusion codes, and the confusion codes are source codes after the codes are mixed;
the first code obtaining unit is used for analyzing the collapse information to obtain a first code with problems in the confusion code;
and the crash point checking unit is used for determining a second code corresponding to the first code in the source code according to the mapping relation in the confusion file and checking the crash point in the software development kit based on the second code.
According to the crash information processing device provided by the embodiment of the invention, the crash information receiving module receives the crash information reported by the client corresponding to the SDK, wherein the crash information comprises information which is added with target information and appears in the running process of the host program accessed with the SDK, the target information can comprise first version information of the SDK, program version information and identification information of the host program, and the target information in the received crash information can represent a crash object, namely what host program is in what version of the host program where the crash occurs, and what version of the SDK is in the host program which is accessed; furthermore, the second version information of the SDK obtained after the SDK is repaired according to the crash information can be obtained through the repair information obtaining module, and the first version information, the program version information and the second version information which are determined from the crash information are used as repair information; and then, determining a specific host program according to the identification information obtained from the crash information through a repair information sending module, and sending the repair information to a program server where the determined host program is located, so that the host program can better apply the repaired SDK according to the repair information received by the program server. The device achieves the effect that the repaired SDK can be well applied by a host program.
The crash information processing device provided by the embodiment of the invention can execute the crash information processing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
It should be noted that, in the embodiment of the crash information processing apparatus, each unit and module included are only divided according to the functional logic, but not limited to the above-mentioned division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
Fig. 9 shows a schematic diagram of a terminal or package server (hereinafter collectively referred to as an electronic device) 10 that may be used to implement an embodiment of the present invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 9, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as the crash information processing method.
In some embodiments, the crash information processing method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the crash information processing method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the crash information processing method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims (13)

1. A crash information processing method, applied to a client corresponding to a software development kit, the method comprising:
responding to a crash information acquisition instruction, and acquiring crash information of a host program in the running process, wherein the host program is an application program accessed with the software development kit;
obtaining target information, adding the target information into the crash information, and updating the crash information according to an adding result, wherein the target information comprises first version information of the software development kit, program version information and identification information of the host program;
And reporting the crash information to a package server corresponding to the software development kit, so that the package server sends repair information to a program server corresponding to the host program with the identification information in the crash information, wherein the repair information comprises the first version information and the program version information determined from the crash information, and the repaired second version information of the software development kit obtained after the software development kit is repaired according to the crash information.
2. The method of claim 1, wherein the obtaining the target information comprises:
acquiring the first version information;
acquiring environment variable information transmitted by the host program, and determining the program version information and the identification information according to the environment variable information;
and taking the first version information, the program version information and the identification information as target information.
3. The method of claim 1, wherein the obtaining the target information comprises:
and if the crash information is information generated by the software development kit, acquiring target information.
4. A method according to claim 3, further comprising:
and determining whether a target identifier exists in the collapse information, and if so, taking the collapse information as information generated by the software development kit, wherein the target identifier comprises an identifier which is confused into a source code of the software development kit when the source code is confused.
5. The method of claim 1, wherein the obtaining crash information of the host program during the running process comprises:
intercepting crash information of a host program in the running process to obtain the crash information;
after the crash information is obtained, the method further comprises:
and returning the crash information to the host program.
6. A crash information processing method, which is applied to a package server corresponding to a software development kit, the method comprising:
receiving crash information reported by a client corresponding to the software development kit, wherein the crash information comprises information added with target information, which appears in the running process of a host program accessed with the software development kit, and the target information comprises first version information of the software development kit, program version information and identification information of the host program;
Acquiring second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information, and taking the first version information, the program version information and the second version information which are determined from the crash information as repair information;
and sending the repair information to a program server corresponding to the host program with the identification information in the crash information.
7. The method as recited in claim 6, further comprising:
analyzing the collapse information to find out the collapse points in the software development kit;
determining whether the crash point has been repaired according to the first version information;
and if so, taking the software development kit corresponding to the repaired crash point as the repaired software development kit.
8. The method of claim 7, wherein analyzing the crash information to locate crash points in the software development kit comprises:
obtaining an confusion file, wherein the confusion file is a file generated when the source codes of the software development tool kit are subjected to code confusion, the confusion file stores a mapping relation between the source codes and the confusion codes, and the confusion codes are the source codes after the codes are mixed;
Analyzing the collapse information to obtain a first code with problems in the confusion code;
and determining a second code corresponding to the first code in the source code according to the mapping relation in the confusion file, and checking out a crash point in the software development kit based on the second code.
9. A crash information processing apparatus, which is disposed at a client corresponding to a software development kit, the apparatus comprising:
the crash information acquisition module is used for responding to a crash information acquisition instruction and acquiring crash information of a host program in the running process, wherein the host program is an application program accessed with the software development kit;
the target information adding module is used for obtaining target information, adding the target information into the crash information and updating the crash information according to an adding result, wherein the target information comprises first version information of the software development kit, program version information and identification information of the host program;
and the crash information reporting module is used for reporting the crash information to a package server corresponding to the software development kit, so that the package server sends repair information to a program server corresponding to the host program with the identification information in the crash information, wherein the repair information comprises the first version information and the program version information determined from the crash information, and the repaired second version information of the software development kit obtained after the software development kit is repaired according to the crash information.
10. A crash information processing apparatus, which is disposed at a package server corresponding to a software development kit, the apparatus comprising:
the system comprises a crash information receiving module, a program execution module and a program execution module, wherein the crash information receiving module is used for receiving crash information reported by a client corresponding to the software development kit, wherein the crash information comprises information which is added with target information and appears in the running process of a host program accessed with the software development kit, and the target information comprises first version information of the software development kit, program version information and identification information of the host program;
the repair information obtaining module is used for obtaining second version information of the repaired software development kit obtained after the software development kit is repaired according to the crash information, and taking the first version information, the program version information and the second version information which are determined from the crash information as repair information;
and the repair information sending module is used for sending the repair information to a program server corresponding to the host program with the identification information in the crash information.
11. A terminal, comprising:
At least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to cause the at least one processor to perform the crash information processing method as recited in any one of claims 1-5.
12. A package server, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to cause the at least one processor to perform the crash information processing method as recited in any one of claims 6-8.
13. A computer readable storage medium storing computer instructions for causing a processor to implement the crash information processing method according to any one of claims 1-8 when executed.
CN202210952163.4A 2022-08-09 2022-08-09 Crash information processing method, device, terminal, server and storage medium Pending CN117632217A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210952163.4A CN117632217A (en) 2022-08-09 2022-08-09 Crash information processing method, device, terminal, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210952163.4A CN117632217A (en) 2022-08-09 2022-08-09 Crash information processing method, device, terminal, server and storage medium

Publications (1)

Publication Number Publication Date
CN117632217A true CN117632217A (en) 2024-03-01

Family

ID=90015030

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210952163.4A Pending CN117632217A (en) 2022-08-09 2022-08-09 Crash information processing method, device, terminal, server and storage medium

Country Status (1)

Country Link
CN (1) CN117632217A (en)

Similar Documents

Publication Publication Date Title
CN111752843B (en) Method, apparatus, electronic device and readable storage medium for determining influence surface
CN111858296B (en) Interface testing method, device, equipment and storage medium
CN110858172A (en) Automatic test code generation method and device
CN110688305B (en) Test environment synchronization method, device, medium and electronic equipment
CN109683997B (en) Method for accessing application program interface through sandbox, sandbox and sandbox equipment
CN107621963B (en) Software deployment method, software deployment system and electronic equipment
CN112035344A (en) Multi-scenario test method, device, equipment and computer readable storage medium
CN109408309B (en) Multi-terminal testing method and device
CN114205274A (en) Network equipment testing method and device
CN112131092A (en) Page debugging method and device
CN104809063A (en) Test method and device of distributed system
CN112269706A (en) Interface parameter checking method and device, electronic equipment and computer readable medium
CN107908565B (en) Test method and test equipment
CN116401113B (en) Environment verification method, device and medium for heterogeneous many-core architecture acceleration card
CN117520195A (en) Method, apparatus, device, storage medium and program product for testing interface
CN108304321A (en) A kind of method, system and device creating front and back end exploitation joint debugging environment
CN112115041A (en) Dynamic point burying method and device for application program, storage medium and computer equipment
CN117632217A (en) Crash information processing method, device, terminal, server and storage medium
CN115495195A (en) Data processing method and device and related equipment
CN114021133A (en) Code processing method and device, electronic equipment and storage medium
CN114416895A (en) Map data processing method and device, electronic equipment and storage medium
CN109286978B (en) Networking method and device of positioning network, terminal equipment and storage medium
CN118152250A (en) Application programming interface test method, apparatus, device, medium and program product
CN117195236A (en) Vulnerability detection method and device for target service, electronic equipment and storage medium
CN115309717A (en) Database loading method, device, equipment, medium and computer program product

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