CN115878086A - Application program operation processing method, device, equipment and storage medium - Google Patents

Application program operation processing method, device, equipment and storage medium Download PDF

Info

Publication number
CN115878086A
CN115878086A CN202211361042.9A CN202211361042A CN115878086A CN 115878086 A CN115878086 A CN 115878086A CN 202211361042 A CN202211361042 A CN 202211361042A CN 115878086 A CN115878086 A CN 115878086A
Authority
CN
China
Prior art keywords
identifier
exchanged
determining
execution
processing request
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
CN202211361042.9A
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.)
Agricultural Bank of China
Original Assignee
Agricultural Bank of China
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 Agricultural Bank of China filed Critical Agricultural Bank of China
Priority to CN202211361042.9A priority Critical patent/CN115878086A/en
Publication of CN115878086A publication Critical patent/CN115878086A/en
Pending legal-status Critical Current

Links

Images

Abstract

The invention discloses an application program running processing method, device, equipment and storage medium. The method comprises the following steps: in response to a detected processing request, determining a request calling method identifier associated with the processing request; and executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier. By replacing the execution process of the calling method in the processing request with the execution process of the safety method when the processing request is executed, the crash protection of the program operation can be realized without performing the crash protection processing in the program compiling stage, so that the crash protection processing of the program is more convenient.

Description

Application program operation processing method, device, equipment and storage medium
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing an application program.
Background
At present, most mainstream iOS applications are developed by using an objective-c language, and due to the dynamic characteristics, the type of an object is not checked during the compiling period, for example, a dictionary object can be assigned to a string object, but the dictionary object does not have the function of a string, so that after the iOS applications are online, if the type check is not done in advance, the iOS is often thrown out or even crashes.
One of the main anti-crash technologies of the iOS application at present is to perform defensive programming on a crash situation which may occur in a coding stage, wherein common crash reasons include that a parameter is abnormal, an array is out of bounds, a method is not implemented, and the like, and in the coding stage, verification is performed to avoid the crash. The other method is realized in a safe interface mode, specifically, a safe method for fully judging the type is packaged for a method which can generate crash, and the appointment of calling the method is carried out through the development process. For example, a layer of safe _ addObject is encapsulated for the addObject method of the nsmusablearray type, in the method, the type, the length and the like of a calling object are fully checked, and in the development process, the safe _ addObject method is appointed to be called uniformly instead of the addObject method, so that the problem that a program throws an exception due to the fact that the object is too long, the object is empty and the like in the calling process is avoided.
In the process of implementing the invention, at least the following technical problems are found in the prior art: the safety interface scheme carries out compensation type packaging on known and few crash types, needs to investigate the existing project, replaces and transfers all 'unsafe' interfaces, needs to carry out greater invasive modification on the project, cannot ensure the safety of unknown or to be developed and new calls, needs to establish unified specifications for project developers, and is difficult to realize the uniformity in large-scale projects.
Disclosure of Invention
The invention provides an application program operation processing method, device, equipment and storage medium, and aims to solve the technical problem that application collapse prevention processing is difficult to realize in a compiling stage.
According to an aspect of the present invention, there is provided an application program execution processing method, including:
in response to a detected processing request, determining a request calling method identifier associated with the processing request;
and executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier.
Optionally, on the basis of the above scheme, before responding to the detected processing request, the method further includes:
when an application program is started, determining at least one method to be exchanged;
and determining a safety method identifier corresponding to the method identifier to be exchanged based on a preset method exchange relationship, and replacing the execution process of the method identifier to be exchanged with the execution process of the safety method identifier through method exchange.
Optionally, on the basis of the foregoing scheme, the determining at least one method to be exchanged includes:
and determining the method to be exchanged based on a preset exchange method library.
Optionally, on the basis of the above scheme, the setting of the exchange method library includes:
acquiring historical program operating data, and determining the identifier of the method to be exchanged based on the historical program operating data;
and determining a safety method identifier corresponding to the method identifier to be exchanged and an execution process of the safety method identifier, and storing to construct the exchange method library.
Optionally, on the basis of the above scheme, the determining, based on the historical program operating data, the identifier of the method to be exchanged includes:
and determining operation crash information in the historical program operation data, and determining the method identifier to be exchanged based on the calling method associated with the operation crash information.
Optionally, on the basis of the above scheme, the determining a security method identifier corresponding to the to-be-exchanged method identifier and the executing process of the security method identifier include:
constructing the safety method identification based on the method identification to be exchanged;
determining the execution condition of the method identifier to be exchanged based on the method execution characteristics of the method identifier to be exchanged, and determining a verification condition based on the execution condition;
and determining the execution process of the safety method identifier based on the verification condition and the operation mode of the method to be exchanged.
Optionally, on the basis of the above scheme, the constructing the security method identifier based on the to-be-exchanged method identifier includes:
determining method keywords based on the method identifier to be exchanged;
and constructing an identifier meeting a set length as the safety method identifier based on the method keyword.
According to another aspect of the present invention, there is provided an application execution processing apparatus including:
the calling method identification determining module is used for responding to the detected processing request and determining a request calling method identification related to the processing request;
and the processing request execution module is used for executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the application program running processing method according to any embodiment of the present invention.
According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement a method for processing an application program according to any one of the embodiments of the present invention when the computer instructions are executed.
According to the technical scheme of the embodiment of the invention, the request calling method identification associated with the processing request is determined by responding to the detected processing request; and executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier. By replacing the execution process of the calling method in the processing request with the execution process of the safety method when the processing request is executed, the crash protection of the program operation can be realized without performing the crash protection processing in the program compiling stage, so that the crash protection processing of the program is more convenient.
It should be understood that the statements in this section are not intended to identify key or critical features of the embodiments of the present invention, nor are they intended to limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of an application running processing method according to an embodiment of the present invention;
fig. 2 is a flowchart of an application running processing method according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of an application running processing apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solutions of the present invention, 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.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Moreover, 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.
Example one
Fig. 1 is a flowchart of an application execution processing method according to an embodiment of the present invention, where this embodiment is applicable to a situation when an application is executed, especially to a situation when an application is executed in an iOS system, and the method may be executed by an application execution processing apparatus, which may be implemented in hardware and/or software, and may be configured in a computer device. As shown in fig. 1, the method includes:
s110, responding to the detected processing request, and determining a request calling method identification associated with the processing request.
In this embodiment, the processing request may be any processing request supported in the application program. For example, the processing request may be a counting processing request, a value processing request, and the like, which is not limited herein.
It is understood that the running processing device of the application program may determine, according to the processing request, a method to be called for executing the processing request, and use the method to be called for executing the processing request as a request calling method, and use an identifier of the method as a request calling method identifier. Generally, the object usually called in the processing request is a method name, and based on this, the request calling method identifier associated with the processing request can be the method name of the request calling method.
And S120, executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier.
In this embodiment, it is not necessary to perform processing for preventing the program from crashing in the development/compilation stage, but only to replace the execution process of the original method with the execution process of the security method corresponding to the original method in advance in the program running stage, and execute the processing request through the execution process of the security method when executing the processing request. By replacing the execution process of the method at the program running stage, the anti-crash processing of the application program can be realized without carrying out invasive change on the application program.
In the above process, the security method identifier corresponding to the request-to-call method identifier may be predetermined. The method can be set manually or automatically based on the request calling method identification.
It should be noted that not all the request calling methods need to be replaced by the execution process, but only the method with the risk of crash during running needs to be replaced by the execution process. Therefore, not all execution processes for processing the request need to be determined by the security method identifier corresponding to the request calling method identifier.
In one embodiment of the present invention, before responding to the detected processing request, the method further comprises:
when an application program is started, determining at least one method to be exchanged;
and determining a safety method identifier corresponding to the method identifier to be exchanged based on a preset method exchange relationship, and replacing the execution process of the method identifier to be exchanged with the execution process of the safety method identifier through method exchange.
Optionally, when detecting that the application program is started, determining a method to be exchanged, and replacing an execution process of the method to be exchanged with a safe execution process. Generally, an application program of the iOS system is developed through an object-C language, a method to be exchanged which may possibly generate a crash can be exchanged by utilizing the characteristic that the method can be exchanged when the object-C language runs, the method to be exchanged is replaced by using the implementation of a safety method, and the crash is avoided when a processing request is executed.
Wherein Objective-C is a general purpose, high-level, object-oriented programming language. It extends the standard ANSI C programming language, adding a Smalltalk-like message passing mechanism to ANSI C. It is the OSX and iOS operating systems of apple, and the main programming languages for its associated APIs, cocoa and Cocoa Touch. The Method exchange can be realized by means of Method switzling, which mainly has the function of replacing the realization of one Method with the realization of another Method in runtime, each class in Objective-C maintains a Method list, namely, method list, the Method list has different methods, namely, method, each Method includes the name (SEL) and specific realization (IMP) of the Method, the Method exchange is to disconnect the original correspondence between SEL and IMP, and generate the correspondence between SEL and new IMP.
It should be noted that the method provided by the present embodiment can be applied not only to the application developed by Objective-C, but also to all the applications developed by languages that can implement method exchange.
Optionally, the determining at least one method to be exchanged includes:
and determining the method to be exchanged based on a preset exchange method library.
Optionally, a method exchange library may be preset, and when the application program is started, all or part of the methods in the method exchange library are used as the methods to be exchanged. Illustratively, the method to be exchanged can be selected from the exchange method library according to the starting type of the application program. Generally, the running functions corresponding to different starting types are different, the functions to be executed after starting can be determined according to the starting types, and the method corresponding to the functions to be executed in the exchange method library is taken as the method to be exchanged.
Wherein, the exchange method library can be set according to historical operation data.
In one implementation, the setting of the exchange method library includes:
acquiring historical program operating data, and determining the identifier of the method to be exchanged based on the historical program operating data;
and determining a safety method identifier corresponding to the method identifier to be exchanged and an execution process of the safety method identifier, and storing to construct the exchange method library.
It can be understood that the historical program operation data includes normal operation data and operation crash data, a method with operation crash risk can be selected as a method to be exchanged according to the normal operation data and the operation crash data, a security method corresponding to the method to be exchanged and an execution process of the security method are determined, and the method to be exchanged and the security method are stored in an exchange method library in an associated manner.
It should be noted that the historical program operation data is not limited to the operation data of the current application program, and may further include operation data of other application programs. Considering that although the application programs are different, different application programs may all need to call the same method, therefore, historical operating data of other application programs can be used as the historical program operating program as a reference of the method of the current application program with the risk of operating crash.
In one implementation, the determining the identifier of the method to be exchanged based on the historical program operation data includes:
and determining operation crash information in the historical program operation data, and determining the method identifier to be exchanged based on the calling method associated with the operation crash information.
In order to completely avoid the risk of operation crash, all calling methods contained in the operation crash information can be directly used as the method to be exchanged, and the corresponding method identifier to be exchanged is determined.
In some embodiments, the determining a security method identifier corresponding to the to-be-exchanged method identifier and the executing process of the security method identifier include:
constructing the safety method identification based on the method identification to be exchanged;
determining the execution condition of the method identifier to be exchanged based on the method execution characteristics of the method identifier to be exchanged, and determining a verification condition based on the execution condition;
and determining the execution process of the safety method identifier based on the verification condition and the operation mode of the method to be exchanged.
Firstly, in order to enable the security methods corresponding to the method to be exchanged to maintain consistency on the identifiers, the security method identifiers may be constructed based on the method to be exchanged identifiers. Then, the execution process of the security method is determined based on the execution characteristics and the execution mode of the method to be exchanged.
For example, assuming that the method to be exchanged is identified as a, the corresponding security method may be constructed with the identification Aa. In addition, the execution characteristics of the method to be exchanged may be determined according to the execution object of the method to be exchanged. If the method to be exchanged is a counting method, it can be known that if the execution object of the counting method is an integer type value, the execution condition is the integer type value, otherwise the operation is crashed, it can be determined that the check condition is to determine whether the execution object is the integer type value, and the execution process of the security method is set as: judging whether the execution object is an integer class value, if so, executing calculation operation; if not, outputting the set prompt information for prompting. So that the operation crash can not be caused even if the operation cannot be carried out based on the safety method.
On the basis of the above scheme, the constructing the security method identifier based on the to-be-exchanged method identifier includes:
determining method keywords based on the method identifier to be exchanged;
and constructing an identifier meeting a set length as the safety method identifier based on the method keyword.
In consideration of the fact that the execution process of the method to be exchanged is replaced by the execution process of the security method when the method to be exchanged is exchanged, the execution process of the security method is also replaced by the execution process of the method to be exchanged, the set length of the security method identifier can be set to avoid miscalling of the security method, the security method identifier is set to be a longer identifier, and the identifier repetition of other method identifiers and the security method identifier is avoided. Meanwhile, in order to make the method identifier to be exchanged and the security method identifier consistent, method keywords in the method identifier to be exchanged need to be determined, and the security method identifier is constructed based on the method keywords and the set length. The set length can be set according to actual requirements, and is not limited herein.
For example, assuming that the to-be-exchanged method identifier is a count, the count may be directly used as a method key, and assuming that the length is set to be 10, an identifier with a length not less than 10 may be randomly generated based on the count as a security method identifier.
In the technical scheme of the embodiment, a request calling method identifier associated with a processing request is determined by responding to the detected processing request; and executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier. By replacing the execution process of the calling method in the processing request with the execution process of the safety method when the processing request is executed, the crash protection of the program operation can be realized without performing crash protection processing in the program compiling stage, and the crash protection processing of the program is more convenient.
Example two
Fig. 2 is a flowchart of an application running processing method according to a second embodiment of the present invention, and this embodiment provides a preferred embodiment based on the foregoing embodiment. As shown in fig. 2, the method includes:
and the server side issues the abnormal data, so that the abnormal calling method is determined based on the abnormal data, and the safety method corresponding to the abnormal calling method is determined. Optionally, a corresponding crash protector may be configured for each abnormal calling method, and when the application program is started, the crash protector replaces the execution process of the abnormal calling method (a method name) with the implementation process of the corresponding security method (a security method name), so that the execution process based on the security method is executed when the request is executed, and the program operation crash is avoided.
It can be understood that corresponding crash protectors can be set for different abnormal calling methods, so that the same type of crash can be solved at one time, and the online crash rate is greatly reduced.
According to the technical scheme of the embodiment, type judgment is not needed to be carried out on calling of the method every time in the development stage, and anti-collapse low intrusion is realized; and for the service logic to be developed in the future, the developer still does not need to carry out type judgment or parameter verification on the calling of the method A, so that the safety can be ensured, and the unification of different services can be realized.
EXAMPLE III
Fig. 3 is a schematic structural diagram of an application execution processing apparatus according to a third embodiment of the present invention. As shown in fig. 3, the apparatus includes: a calling method identification determination module 310 and a processing request execution module 320, wherein:
a calling method identification determining module 310, configured to determine, in response to a detected processing request, a request calling method identification associated with the processing request;
and a processing request executing module 320, configured to execute the processing request, generate an execution result, and display the execution result, where an execution process of the processing request is determined based on the security method identifier corresponding to the request calling method identifier.
According to the technical scheme of the embodiment, a request calling method identifier associated with a processing request is determined by responding to the detected processing request; and executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier. By replacing the execution process of the calling method in the processing request with the execution process of the safety method when the processing request is executed, the crash protection of the program operation can be realized without performing the crash protection processing in the program compiling stage, so that the crash protection processing of the program is more convenient.
On the basis of the foregoing embodiment, optionally, the apparatus further includes an execution procedure replacement module, configured to:
determining at least one method to be exchanged when an application starts up before responding to the detected processing request;
and determining a safety method identifier corresponding to the method identifier to be exchanged based on a preset method exchange relationship, and replacing the execution process of the method identifier to be exchanged with the execution process of the safety method identifier.
On the basis of the above embodiment, optionally, the execution process replacement module is specifically configured to:
and determining the method to be exchanged based on a preset exchange method library.
On the basis of the foregoing embodiment, optionally, the apparatus further includes an exchange method library setting module, configured to:
obtaining historical program operating data, and determining the method identifier to be exchanged based on the historical program operating data;
and determining a safety method identifier corresponding to the method identifier to be exchanged and an execution process of the safety method identifier, and storing to construct the exchange method library.
On the basis of the foregoing embodiment, optionally, the exchange method library setting module is specifically configured to:
and determining operation crash information in the historical program operation data, and determining the method identifier to be exchanged based on the calling method associated with the operation crash information.
On the basis of the foregoing embodiment, optionally, the exchange method library setting module is specifically configured to:
constructing the safety method identification based on the method identification to be exchanged;
determining the execution condition of the method identifier to be exchanged based on the method execution characteristic of the method identifier to be exchanged, and determining a verification condition based on the execution condition;
and determining the execution process of the safety method identification based on the checking condition and the operation mode of the method to be exchanged.
On the basis of the foregoing embodiment, optionally, the exchange method library setting module is specifically configured to:
determining method keywords based on the method identifier to be exchanged;
and constructing an identifier meeting a set length as the safety method identifier based on the method keyword.
The running processing device of the application program provided by the embodiment of the invention can execute the running processing method of the application program provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Example four
Fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, 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. 4, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various suitable 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 necessary for the operation of the electronic apparatus 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 the bus 14.
A number of 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, or the like; 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 dedicated Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The processor 11 executes the respective methods and processes described above, such as the execution processing method of the application program.
In some embodiments, the execution processing method of the application program may be implemented as a computer program that is tangibly embodied in a computer-readable storage medium, such as the 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 the RAM 13 and executed by the processor 11, one or more steps of the execution processing method of the application program described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the execution processing method of the application program by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a 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 that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
The computer program for implementing the execution processing method of the application program of the present invention can 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 performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
EXAMPLE five
An embodiment of the present invention further provides a computer-readable storage medium, where a computer instruction is stored, where the computer instruction is used to enable a processor to execute a method for processing an application program, where the method includes:
in response to a detected processing request, determining a request calling method identifier associated with the processing request;
and executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier.
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. A 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 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) by 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 can 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, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end 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 back-end, 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. A client and server are generally 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 host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. An application program operation processing method is characterized by comprising the following steps:
in response to a detected processing request, determining a request calling method identifier associated with the processing request;
and executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier.
2. The method of claim 1, prior to responding to the detected processing request, further comprising:
when an application program is started, determining at least one method to be exchanged;
and determining a safety method identifier corresponding to the method identifier to be exchanged based on a preset method exchange relationship, and replacing the execution process of the method identifier to be exchanged with the execution process of the safety method identifier through method exchange.
3. The method of claim 2, wherein determining at least one method to be exchanged comprises:
and determining the method to be exchanged based on a preset exchange method library.
4. The method of claim 3, wherein the setting of the library of switching methods comprises:
acquiring historical program operating data, and determining the identifier of the method to be exchanged based on the historical program operating data;
and determining a safety method identifier corresponding to the method identifier to be exchanged and an execution process of the safety method identifier, and storing to construct the exchange method library.
5. The method of claim 4, wherein determining the method identification to be exchanged based on the historical program execution data comprises:
and determining operation crash information in the historical program operation data, and determining the method identifier to be exchanged based on the calling method associated with the operation crash information.
6. The method according to claim 4, wherein the determining of the security method identifier corresponding to the to-be-exchanged method identifier and the execution process of the security method identifier include:
constructing the safety method identification based on the method identification to be exchanged;
determining the execution condition of the method identifier to be exchanged based on the method execution characteristics of the method identifier to be exchanged, and determining a verification condition based on the execution condition;
and determining the execution process of the safety method identification based on the checking condition and the operation mode of the method to be exchanged.
7. The method of claim 6, wherein the constructing the secure method identifier based on the to-be-exchanged method identifier comprises:
determining method keywords based on the method identifier to be exchanged;
and constructing an identifier meeting a set length as the safety method identifier based on the method keyword.
8. An application program execution processing apparatus, comprising:
the calling method identification determining module is used for responding to the detected processing request and determining a request calling method identification related to the processing request;
and the processing request execution module is used for executing the processing request, generating an execution result and displaying the execution result, wherein the execution process of the processing request is determined based on the safety method identifier corresponding to the request calling method identifier.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,
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 enable the at least one processor to perform a method of processing an execution of an application program according to any one of claims 1 to 7.
10. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions for causing a processor to implement a method for processing execution of an application program according to any one of claims 1 to 7.
CN202211361042.9A 2022-11-02 2022-11-02 Application program operation processing method, device, equipment and storage medium Pending CN115878086A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211361042.9A CN115878086A (en) 2022-11-02 2022-11-02 Application program operation processing method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211361042.9A CN115878086A (en) 2022-11-02 2022-11-02 Application program operation processing method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN115878086A true CN115878086A (en) 2023-03-31

Family

ID=85759336

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211361042.9A Pending CN115878086A (en) 2022-11-02 2022-11-02 Application program operation processing method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115878086A (en)

Similar Documents

Publication Publication Date Title
CN113468021B (en) Method, device, equipment and storage medium for monitoring performance data
CN113641544A (en) Method, apparatus, device, medium and product for detecting application status
CN116545905A (en) Service health detection method and device, electronic equipment and storage medium
CN115878086A (en) Application program operation processing method, device, equipment and storage medium
CN115600261A (en) Data security protection method, device, equipment and medium
CN115310096A (en) Security vulnerability processing method, device, equipment and medium
CN115580522A (en) Method and device for monitoring running state of container cloud platform
CN115309730A (en) Data auditing method and device, electronic equipment and storage medium
CN113778849A (en) Method, apparatus, device and storage medium for testing code
CN112968876A (en) Content sharing method and device, electronic equipment and storage medium
CN115080205B (en) Task execution method, device, electronic equipment and readable storage medium
CN113220554B (en) Method and apparatus for detecting performance of program code
CN116719621B (en) Data write-back method, device, equipment and medium for mass tasks
CN117234471A (en) Project development method and device, electronic equipment and storage medium
CN115374010A (en) Function testing method, device, equipment and storage medium
CN115794255A (en) Data processing method and device, electronic equipment and storage medium
CN113901451A (en) Link detection method and device, electronic equipment and storage medium
CN115408195A (en) Batch task management method, equipment and storage medium for heterogeneous platform
CN116431578A (en) File cleaning method and device, electronic equipment and storage medium
CN116302796A (en) Process monitoring method and device, electronic equipment and storage medium
CN115344212A (en) Data desensitization method, device and system, electronic equipment and storage medium
CN115309717A (en) Database loading method, device, equipment, medium and computer program product
CN114691404A (en) Service process monitoring method and device, electronic equipment, storage medium and product
CN115048159A (en) Exception handling method, device, equipment and storage medium
CN115801357A (en) Global exception handling method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination