CN111338922A - DLL failure detection method and device - Google Patents
DLL failure detection method and device Download PDFInfo
- Publication number
- CN111338922A CN111338922A CN202010136334.7A CN202010136334A CN111338922A CN 111338922 A CN111338922 A CN 111338922A CN 202010136334 A CN202010136334 A CN 202010136334A CN 111338922 A CN111338922 A CN 111338922A
- Authority
- CN
- China
- Prior art keywords
- dll
- current
- target process
- account information
- account
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000001514 detection method Methods 0.000 title claims description 37
- 238000000034 method Methods 0.000 claims abstract description 194
- 230000006399 behavior Effects 0.000 description 19
- 238000007726 management method Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 238000002347 injection Methods 0.000 description 4
- 239000007924 injection Substances 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011112 process operation Methods 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a method and a device for detecting DLL failure, wherein data information of a target process is acquired and stored through a current DLL, the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, then an account updating signal sent by a timing thread is received, and when the account updating signal is received, the current DLL is judged to be failed, wherein the timing thread is located in the target process and used for acquiring latest account information logged in the target process in the running process, and when the latest account information is inconsistent with the current account information, the account updating signal is sent. According to the method, whether account login is switched or not can be detected in real time aiming at the client process with account login, whether the current DLL is invalid or not is further judged, the fact that the Internet access behavior management equipment receives wrong data is effectively prevented, and accuracy of auditing the Internet access behavior of the client is improved.
Description
Technical Field
The application relates to the technical field of application program monitoring, in particular to a method and a device for detecting DLL failure.
Background
Currently, a DLL injection method is often used by a network access behavior management device to audit the network access behavior of a client. DLL injection is a process of injecting code to a running process in a client, and the injected code exists in the form of a Dynamic Link Library (DLL). Through DLL injection, the internet behavior management device can acquire data information of the client process during operation, and then audit the internet behavior of the client according to the data information.
For a client process with account login, data information acquired after DLL injection generally includes account information and operation information, where the account information is used to identify the identity of a logged-in user, the operation information is a series of data generated in the process operation process, for example, for some chat software, the account information includes an account name, a telephone number, a nickname, and the like, and the operation information includes text messages, picture messages, various files, and the like received and sent in the chat process. When the client process runs, if account login is switched, the account information of the client process is changed, and in this case, the originally injected DLL is failed, and new DLL needs to be injected again to obtain new account information.
However, when the current internet behavior management device monitors the client, it cannot be determined whether the process is running and account login is switched, so that it cannot be detected whether the current DLL is failed. Therefore, when the current account is switched and logged in, the internet behavior management device cannot inject a new DLL in time, and in this case, when the client sends the newly generated running information to the internet behavior management device, the client still sends the original account information together according to the original DLL, so that the internet behavior management device receives wrong data, and the accuracy of auditing the internet behavior of the client is affected.
Disclosure of Invention
In order to solve the problem that whether the current DLL is invalid or not cannot be detected and the accuracy of auditing the internet behavior of the client is affected because whether the account login is switched or not when the process is running cannot be judged when the current internet behavior management device monitors the client, the application discloses a method and a device for detecting DLL invalidation through the following embodiments.
The application discloses in a first aspect a method for detecting DLL failure, comprising:
acquiring and storing data information of a target process according to a current DLL, wherein the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, and the target process is any run process which needs to be monitored and has account logging in a client;
receiving an account updating signal sent by a timing thread, and judging that the current DLL is invalid when the account updating signal is received, wherein the timing thread is located in the target process and is used for acquiring the latest account information logged in the target process in the running process and sending the account updating signal when the latest account information is inconsistent with the current account information.
Optionally, the acquiring and storing data information of the target process according to the current DLL includes:
loading and starting the current DLL to acquire the data information;
and storing the data information into a preset target process memory.
Optionally, the timing thread is configured to obtain, every preset fixed time period, the latest account information logged in the target process during the operation process, and compare the latest account information with the current account information stored in the target process memory, where a set range of the fixed time period is 3 seconds to 5 seconds.
Optionally, while the loading starts the current DLL, the detection method further includes:
and starting the timing thread in the target process.
Optionally, the data information further includes version information of the current DLL.
Optionally, after determining that the current DLL has failed, the detection method further includes:
uninstalling the current DLL from the target process and reinjecting a new DLL, wherein version information of the new DLL is different from that of the current DLL.
Optionally, before the acquiring and storing the data information of the target process according to the current DLL, the detection method further includes:
and detecting whether the target process starts to run or not at regular time, and remotely injecting the DLL into the target process when the target process starts to run.
A second aspect of the present application discloses a DLL failure detection apparatus, which is applied to the DLL failure detection method described in the first aspect of the present application, and the detection apparatus includes:
the information acquisition and storage module is used for acquiring and storing data information of a target process according to a current DLL, wherein the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, and the target process is any one run process which needs to be monitored and has account login in a client;
and the failure determination module is used for receiving an account updating signal sent by a timing thread, determining that the current DLL is failed when the account updating signal is received, wherein the timing thread is positioned in the target process, and the timing thread is used for acquiring the latest account information logged in the target process in the running process and sending the account updating signal when the latest account information is inconsistent with the current account information.
Optionally, the information obtaining and storing module includes:
the acquisition unit is used for loading and starting the current DLL and acquiring the data information;
and the storage unit is used for storing the data information into a preset target process memory.
Optionally, the obtaining unit includes:
and the timed thread starting sub-unit is used for starting the timed thread in the target process while loading and starting the current DLL.
Optionally, the detection apparatus further includes:
and the updating module is used for unloading the current DLL from the target process and reinjecting a new DLL into the target process after judging that the current DLL has failed, wherein the version information of the new DLL is different from that of the current DLL.
Optionally, the detection apparatus further includes:
and the operation monitoring module is used for regularly detecting whether the target process starts to operate or not before the data information of the target process is acquired and stored according to the current DLL, and remotely injecting the DLL into the target process when the target process starts to operate.
A third aspect of the present application discloses a method for detecting DLL failure, including:
a timing thread acquires the latest account information logged in by a target process in the running process and compares the latest account information with the current account information, wherein the timing thread is positioned in the target process, the target process is any running process which needs to be monitored and has account login in a client, and the current account information is the account information logged in the target process when the current DLL is injected;
and when the latest account information is inconsistent with the current account information, the timing thread sends an account updating signal to a detection device for DLL failure, and the detection device is used for judging that the current DLL has failed when receiving the account updating signal.
Optionally, the acquiring, by the timing thread, the latest account information logged in the running process of the target process, and comparing the latest account information with the current account information includes:
and the timing thread acquires the latest account information logged in the running process of the target process every other preset fixed time period, and compares the latest account information with the current account information stored in the memory of the target process, wherein the set range of the fixed time period is 3-5 seconds.
The application discloses a method and a device for detecting DLL failure, wherein data information of a target process is acquired and stored through a current DLL, the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, the target process is any one running process needing monitoring and having account logging in a client side, an account updating signal sent by a timing thread is received, when the account updating signal is received, the current DLL is judged to be failed, the timing thread is located in the target process, the timing thread is used for acquiring the latest account information logged in the target process in the running process, and when the latest account information is inconsistent with the current account information, the account updating signal is sent. According to the method, whether account login is switched or not can be detected in real time aiming at the client process with account login, whether the current DLL is invalid or not is further judged, the fact that the Internet access behavior management equipment receives wrong data is effectively prevented, and accuracy of auditing the Internet access behavior of the client is improved.
Drawings
In order to more clearly explain the technical solution of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic workflow diagram of a DLL failure detection method disclosed in an embodiment of the present application;
fig. 2 is a schematic workflow diagram of another DLL failure detection method disclosed in the embodiment of the present application;
fig. 3 is a schematic structural diagram of a DLL failure detection apparatus disclosed in an embodiment of the present application;
fig. 4 is a schematic structural diagram of another DLL failure detection apparatus disclosed in the embodiments of the present application;
fig. 5 is a schematic workflow diagram of another DLL failure detection method disclosed in an embodiment of the present application.
Detailed Description
In order to solve the problem that whether the current DLL is invalid or not cannot be detected and the accuracy of auditing the internet behavior of the client is affected because whether the account login is switched or not when the process is running cannot be judged when the current internet behavior management device monitors the client, the application discloses a method and a device for detecting DLL invalidation through the following embodiments.
Referring to the workflow diagram shown in fig. 1, a first embodiment of the present application discloses a method for detecting DLL failure, including:
step S101, obtaining and storing data information of a target process according to a current DLL, wherein the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, and the target process is any one run process which needs to be monitored and has account logging in a client.
The account information is related information that can identify the identity of the currently logged-in account, such as an account ID. For chat software such as WeChat, the account information can also be a nickname of an account or a mobile phone number bound to the account.
Step S102, receiving an account updating signal sent by a timing thread, and when receiving the account updating signal, determining that the current DLL is invalid, wherein the timing thread is located in the target process, and the timing thread is used for acquiring the latest account information logged in the target process in the running process and sending the account updating signal when the latest account information is inconsistent with the current account information.
In practical application, the threads belong to practical operation units in a client process, a plurality of threads can be concurrently executed in one process, and each thread executes different tasks in parallel. In the embodiment of the application, a timing thread is started in a target process and used for acquiring the latest account information logged in by the target process in a timing mode in the running process. In one implementation, the thread may be a timer.
The application discloses a DLL failure detection method, which comprises the steps of obtaining and storing data information of a target process through a current DLL, wherein the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, the target process is an operated process which needs to be monitored and has account logging in a client side, an account updating signal sent by a timing thread is received, when the account updating signal is received, the current DLL is judged to be failed, the timing thread is located in the target process, the timing thread is used for obtaining the latest account information logged in the target process in the operation process, and when the latest account information is inconsistent with the current account information, the account updating signal is sent. According to the method, whether account login is switched or not can be detected in real time aiming at the client process with account login, whether the current DLL is invalid or not is further judged, the fact that the Internet access behavior management equipment receives wrong data is effectively prevented, and accuracy of auditing the Internet access behavior of the client is improved.
Further, the acquiring and storing data information of the target process according to the current DLL includes:
and loading and starting the current DLL to acquire the data information.
In the embodiment of the application, the data information is acquired when the current DLL is loaded and started, so that the running efficiency of the target process is ensured.
And storing the data information into a preset target process memory.
Further, the timing thread is configured to obtain the latest account information logged in the running process of the target process every preset fixed time period, and compare the latest account information with the current account information stored in the memory of the target process, where the set range of the fixed time period is 3 seconds to 5 seconds.
Further, while the loading starts the current DLL, the detection method further includes:
and starting the timing thread in the target process.
Further, the data information further includes version information of the current DLL.
Further, after determining that the current DLL has failed, the detection method further includes:
uninstalling the current DLL from the target process and reinjecting a new DLL, wherein version information of the new DLL is different from that of the current DLL.
Further, before the acquiring and storing the data information of the target process according to the current DLL, the detection method further includes:
and detecting whether the target process starts to run or not at regular time, and remotely injecting the DLL into the target process when the target process starts to run.
In one implementation, referring to the workflow diagram shown in fig. 2, the method for detecting DLL failure disclosed in the above embodiment of the present application includes the following steps:
step S201, detecting whether the target process is started to operate or not at regular time, and remotely injecting DLL into the target process when the target process is started to operate;
step S202, loading and starting the current DLL, acquiring the data information, and starting the timing thread in the target process
Step S203, storing the data information into a preset target process memory;
step S204, receiving an account updating signal sent by a timing thread, and judging that the current DLL is invalid when the account updating signal is received;
step S205, after determining that the current DLL has failed, uninstalling the current DLL from the target process, and reinjecting a new DLL.
A second embodiment of the present application discloses a DLL failure detection apparatus, which is applied to the DLL failure detection method described in the first embodiment of the present application, and referring to a schematic structural diagram shown in fig. 3, the detection apparatus includes:
the information obtaining and storing module 10 is configured to obtain and store data information of a target process according to a current DLL, where the data information includes current account information, the current account information is account information logged in the target process when the current DLL is injected, and the target process is any run process in a client that needs to be monitored and has account login.
And the failure determination module 20 is configured to receive an account update signal sent by a timing thread, and determine that the current DLL has failed when the account update signal is received, where the timing thread is located in the target process, and the timing thread is configured to obtain latest account information logged in by the target process in an operation process, and send the account update signal when the latest account information is inconsistent with the current account information.
Further, referring to the schematic structural diagram shown in fig. 4, the information acquisition and storage module 10 includes:
an obtaining unit 1001, configured to load and start the current DLL, and obtain the data information.
The storage unit 1002 is configured to store the data information in a preset target process memory.
Wherein the obtaining unit 1001 includes:
and the timed thread starting sub-unit is used for starting the timed thread in the target process while loading and starting the current DLL.
Further, referring to fig. 4, the detecting device further includes:
an updating module 30, configured to uninstall the current DLL from the target process and reinject a new DLL after determining that the current DLL has failed, wherein the version information of the new DLL is different from the version information of the current DLL.
Further, the detection device further comprises:
and the operation monitoring module is used for regularly detecting whether the target process starts to operate or not before the data information of the target process is acquired and stored according to the current DLL, and remotely injecting the DLL into the target process when the target process starts to operate.
The third embodiment of the present application discloses a method for detecting DLL failure, which refers to a workflow diagram shown in fig. 5, and the method includes:
step S301, a timing thread acquires the latest account information logged in the target process in the running process and compares the latest account information with the current account information, the timing thread is located in the target process, the target process is any running process which needs to be monitored and has account login in a client, and the current account information is the account information logged in the target process when the current DLL is injected.
Step S302, when the latest account information is inconsistent with the current account information, the timing thread sends an account updating signal to a DLL failure detection device, and the detection device is used for judging that the current DLL has failed when receiving the account updating signal.
Further, the step of acquiring the latest account information logged in by the target process in the running process by the timing thread and comparing the latest account information with the current account information by the timing thread includes:
and the timing thread acquires the latest account information logged in the running process of the target process every other preset fixed time period, and compares the latest account information with the current account information stored in the memory of the target process, wherein the set range of the fixed time period is 3-5 seconds.
It should be noted that an execution main body of the DLL failure detection method disclosed in the first embodiment of the present application may be an internet behavior management device or a detection apparatus installed in the internet behavior management device, where the detection apparatus includes each module disclosed in the second embodiment of the present application. The execution subject of the DLL failure detection method disclosed in the third embodiment of the present application is a timing thread, and the timing thread is located in a target process.
The present application has been described in detail with reference to specific embodiments and illustrative examples, but the description is not intended to limit the application. Those skilled in the art will appreciate that various equivalent substitutions, modifications or improvements may be made to the presently disclosed embodiments and implementations thereof without departing from the spirit and scope of the present disclosure, and these fall within the scope of the present disclosure. The protection scope of this application is subject to the appended claims.
Claims (10)
1. A method for detecting DLL failure, comprising:
acquiring and storing data information of a target process according to a current DLL, wherein the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, and the target process is any run process which needs to be monitored and has account logging in a client;
receiving an account updating signal sent by a timing thread, and judging that the current DLL is invalid when the account updating signal is received, wherein the timing thread is located in the target process and is used for acquiring the latest account information logged in the target process in the running process and sending the account updating signal when the latest account information is inconsistent with the current account information.
2. The method for detecting DLL failure according to claim 1, wherein the acquiring and storing the data information of the target process according to the current DLL comprises:
loading and starting the current DLL to acquire the data information;
and storing the data information into a preset target process memory.
3. The DLL failure detection method of claim 2,
the timing thread is used for acquiring the latest account information logged in the running process of the target process every other preset fixed time period, and comparing the latest account information with the current account information stored in the memory of the target process, wherein the set range of the fixed time period is 3-5 seconds.
4. The method of claim 2 or 3, wherein while the loading starts the current DLL, the method further comprises:
and starting the timing thread in the target process.
5. The method of detecting a DLL failure of claim 1, wherein the data information further comprises version information of the current DLL.
6. The method of detecting a DLL failure of claim 5, wherein after determining that the current DLL has failed, the method further comprises:
uninstalling the current DLL from the target process and reinjecting a new DLL, wherein version information of the new DLL is different from that of the current DLL.
7. The method of claim 1, wherein before the acquiring and storing the data information of the target process according to the current DLL, the method further comprises:
and detecting whether the target process starts to run or not at regular time, and remotely injecting the DLL into the target process when the target process starts to run.
8. A DLL failure detection apparatus applied to the DLL failure detection method of any one of claims 1 to 7, the DLL failure detection apparatus comprising:
the information acquisition and storage module is used for acquiring and storing data information of a target process according to a current DLL, wherein the data information comprises current account information, the current account information is account information logged in the target process when the current DLL is injected, and the target process is any one run process which needs to be monitored and has account login in a client;
and the failure determination module is used for receiving an account updating signal sent by a timing thread, determining that the current DLL is failed when the account updating signal is received, wherein the timing thread is positioned in the target process, and the timing thread is used for acquiring the latest account information logged in the target process in the running process and sending the account updating signal when the latest account information is inconsistent with the current account information.
9. A method for detecting DLL failure, comprising:
a timing thread acquires the latest account information logged in by a target process in the running process and compares the latest account information with the current account information, wherein the timing thread is positioned in the target process, the target process is any running process which needs to be monitored and has account login in a client, and the current account information is the account information logged in the target process when the current DLL is injected;
and when the latest account information is inconsistent with the current account information, the timing thread sends an account updating signal to a detection device for DLL failure, and the detection device is used for judging that the current DLL has failed when receiving the account updating signal.
10. The method for detecting the DLL failure according to claim 9, wherein the acquiring, by the timing thread, the latest account information logged in by the target process during running and comparing the latest account information with the current account information includes:
and the timing thread acquires the latest account information logged in the running process of the target process every other preset fixed time period, and compares the latest account information with the current account information stored in the memory of the target process, wherein the set range of the fixed time period is 3-5 seconds.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010136334.7A CN111338922B (en) | 2020-03-02 | 2020-03-02 | DLL failure detection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010136334.7A CN111338922B (en) | 2020-03-02 | 2020-03-02 | DLL failure detection method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111338922A true CN111338922A (en) | 2020-06-26 |
| CN111338922B CN111338922B (en) | 2023-04-11 |
Family
ID=71184634
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010136334.7A Active CN111338922B (en) | 2020-03-02 | 2020-03-02 | DLL failure detection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111338922B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030033521A1 (en) * | 2001-08-13 | 2003-02-13 | Andreas Sahlbach | Method, computer program product and system for providing a switch user functionality in an information technological network |
| CN101034983A (en) * | 2006-12-31 | 2007-09-12 | 深圳市中科新业信息科技发展有限公司 | System and method for realizing on-Internet true name of the network access user |
| US20140047461A1 (en) * | 2011-04-28 | 2014-02-13 | Fasoo.Com Co., Ltd | Computing device having a dll injection function, and dll injection method |
| CN103634311A (en) * | 2013-11-26 | 2014-03-12 | 腾讯科技（深圳）有限公司 | Safety protection method and device, and terminal |
-
2020
- 2020-03-02 CN CN202010136334.7A patent/CN111338922B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030033521A1 (en) * | 2001-08-13 | 2003-02-13 | Andreas Sahlbach | Method, computer program product and system for providing a switch user functionality in an information technological network |
| CN101034983A (en) * | 2006-12-31 | 2007-09-12 | 深圳市中科新业信息科技发展有限公司 | System and method for realizing on-Internet true name of the network access user |
| US20140047461A1 (en) * | 2011-04-28 | 2014-02-13 | Fasoo.Com Co., Ltd | Computing device having a dll injection function, and dll injection method |
| CN103634311A (en) * | 2013-11-26 | 2014-03-12 | 腾讯科技（深圳）有限公司 | Safety protection method and device, and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111338922B (en) | 2023-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108399132B (en) | Scheduling test method, device and storage medium | |
| KR100915564B1 (en) | Method, software and apparatus for application upgrade during execution | |
| CA2974820C (en) | System and method for introducing functionality to an application for use with a network service | |
| CN111324423B (en) | Method and device for monitoring processes in container, storage medium and computer equipment | |
| CN110795128B (en) | Program bug repairing method and device, storage medium and server | |
| CN108108296B (en) | Cloud testing method, server and client | |
| CN111506326A (en) | Method, device and equipment for upgrading terminal equipment and storage medium | |
| CN111813646A (en) | Method and device for injecting application probe in docker container environment | |
| CN110618853B (en) | Detection method, device and equipment for zombie container | |
| CN111752975A (en) | Data loading method and device based on Redis, computer equipment and storage medium | |
| CN111338922B (en) | DLL failure detection method and device | |
| CN109376072B (en) | Application program development method and device based on third-party component library | |
| CN117056115B (en) | Application program repairing method and device, storage medium and electronic equipment | |
| CN113535214A (en) | Algorithm file upgrading method and device, electronic device and storage medium | |
| CN107423087A (en) | A kind of application program updating method that server can monitor | |
| CN104158907A (en) | Method and device of downloading application program file | |
| CN110555017A (en) | block chain data cleaning method and device, computer equipment and storage medium | |
| CN116009984A (en) | Security arrangement and automatic response processing method and device and electronic equipment | |
| CN112685063B (en) | Feature library updating method, device, network equipment and readable storage medium | |
| CN115454860A (en) | Automatic testing method and device, storage medium and electronic equipment | |
| CN109460251B (en) | Component integration framework management method and device | |
| CN113157493A (en) | Backup method, device and system based on ticket checking system and computer equipment | |
| CN112905230B (en) | Application management method, device, terminal equipment and storage medium | |
| CN110569088A (en) | client plug-in management method and device, electronic equipment and storage medium | |
| CN110851328A (en) | Method for detecting abnormal power failure of password card in PKCS #11 application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: Detection method and device for DLL failure Granted publication date: 20230411 Pledgee: Guanggu Branch of Wuhan Rural Commercial Bank Co.,Ltd. Pledgor: WUHAN SIPULING TECHNOLOGY Co.,Ltd. Registration number: Y2024980009435 |