CN113220495B - Method and device for processing process abnormal event, electronic equipment and storage medium - Google Patents

Method and device for processing process abnormal event, electronic equipment and storage medium Download PDF

Info

Publication number
CN113220495B
CN113220495B CN202110564156.2A CN202110564156A CN113220495B CN 113220495 B CN113220495 B CN 113220495B CN 202110564156 A CN202110564156 A CN 202110564156A CN 113220495 B CN113220495 B CN 113220495B
Authority
CN
China
Prior art keywords
file
indication signal
threads
core dump
thread
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110564156.2A
Other languages
Chinese (zh)
Other versions
CN113220495A (en
Inventor
滕开恩
杨世增
林森
周健
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang Dahua Technology Co Ltd
Original Assignee
Zhejiang Dahua 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 Zhejiang Dahua Technology Co Ltd filed Critical Zhejiang Dahua Technology Co Ltd
Priority to CN202110564156.2A priority Critical patent/CN113220495B/en
Publication of CN113220495A publication Critical patent/CN113220495A/en
Application granted granted Critical
Publication of CN113220495B publication Critical patent/CN113220495B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793Remedial or corrective actions

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the application provides a method, a device, electronic equipment and a storage medium for processing a process abnormal event, which are used for improving the resource utilization rate when a large-scale process abnormal event occurs in system operation. The method comprises the following steps: when a first thread receives a first indication signal, determining whether a core dump file needs to be generated according to the first indication signal, wherein the first indication signal is used for indicating that an abnormality occurs in a process, the core dump file is used for storing information required for performing abnormality analysis, and the first thread belongs to the process; if the core dump file is determined to be required to be generated, closing a file handle opened by the process; and generating the core dump file.

Description

Method and device for processing process abnormal event, electronic equipment and storage medium
Technical Field
The present invention relates to the field of data storage and operating systems, and in particular, to a method, an apparatus, an electronic device, and a storage medium for processing a process exception event.
Background
In a Linux operating system, a user program runs in a system in a process mode, data and codes of the process are stored in a memory, when serious exception occurs in the process running process, a Linux kernel sends a signal to enable the program to exit, and part of the signal (for example, SIGQUIT, SIGILL, SIGTRAP, SIGABRT, SIGFPE, SIGSEGV, SIGBUS, SIGSYS, SIGXCPU, SIGXFSZ) triggers the process to generate a core dump (coredump) file before exiting so as to write all or part of memory data and call stack information in the process running process into the core file (dump), so that technicians can analyze the reason of the abnormal exit of the process based on the coredump file.
However, the coreump file is usually stored in a solid state disk or a mechanical hard disk, and when an abnormality occurs in a process with complex service and high memory occupation, the generated Coredump file is usually a large file, so that it takes a long time to generate, compress and store the Coredump file, and in the Coredump generation process, the process still occupies resources such as system memory, file handles and the like.
Thus, the abnormal process occupies the hard disk resource for a long time, so that the situation of low resource utilization rate is easy to occur. And if a large-scale process abnormal event occurs in the running process of the system, the service cluster is easy to fail, and the service reliability is easy to be reduced.
Disclosure of Invention
The embodiment of the application provides a method, a device, electronic equipment and a storage medium for processing a process abnormal event, which are used for improving the resource utilization rate when a large-scale process abnormal event occurs in system operation.
In a first aspect, a method for processing a process exception event is provided, where the method includes:
when a first thread receives a first indication signal, determining whether a core dump file needs to be generated according to the first indication signal, wherein the first indication signal is used for indicating that an abnormality occurs in a process, the core dump file is used for storing information required for performing abnormality analysis, and the first thread belongs to the process;
if the core dump file is determined to be required to be generated, closing a file handle opened by the process;
and generating the core dump file.
Optionally, the method further comprises:
and sending a second indication signal to other threads, wherein the second indication signal is used for indicating the other threads to disassociate files and exit from a running state, and the other threads are other threads except the first thread in the process.
Optionally, closing the file handle opened by the process includes:
acquiring a file handle list corresponding to the process;
determining all file handles opened by the process according to the file handle list;
and closing all file handles opened by the process.
Optionally, after closing the file handle opened by the process, the storage resources occupied by the process are released.
In a second aspect, there is provided a process exception event handling apparatus, the apparatus comprising:
the communication module is used for receiving the first indication signal;
the processing module is used for determining whether a core dump file needs to be generated according to a first indication signal when the communication module receives the first indication signal, wherein the first indication signal is used for indicating that an abnormality occurs in a process, the core dump file is used for storing information required for performing abnormality analysis, and the first thread belongs to the process;
the processing module is further configured to close a file handle opened by the process when it is determined that the core dump file needs to be generated;
the processing module is further configured to generate the core dump file.
Optionally, the communication module is further configured to:
and sending a second indication signal to other threads, wherein the second indication signal is used for indicating the other threads to disassociate files and exit from a running state, and the other threads are other threads except the first thread in the process.
Optionally, the processing module is specifically configured to:
acquiring a file handle list corresponding to the process;
determining all file handles opened by the process according to the file handle list;
and closing all file handles opened by the process.
Optionally, after closing the file handle opened by the process, the storage resources occupied by the process are released.
In a third aspect, an electronic device is provided, the electronic device comprising:
a memory for storing program instructions;
and a processor, configured to call the program instructions stored in the memory, and execute the steps included in the method according to any one of the first aspect according to the obtained program instructions.
In a fourth aspect, there is provided a computer readable storage medium storing computer executable instructions for causing a computer to perform the steps comprised by the method of any one of the first aspects.
In a fifth aspect, a computer program product is provided comprising instructions which, when run on a computer, cause the computer to perform the method of processing a process exception event described in the various possible implementations described above.
In the embodiment of the application, when a first instruction signal sent by a system kernel and used for indicating that an abnormality occurs in a process is received by a first thread in the process, whether a core dump file needs to be generated or not is judged according to the first instruction signal, the first thread is used for storing information required by a technician for analyzing reasons of the abnormality of the program, if the fact that the core dump file needs to be generated is determined, a file handle opened by the process is closed, and the core dump file is generated. That is, when a process is abnormal, a core dump file needs to be generated for a technician to analyze the cause of the abnormality, a first thread in the process closes all file handles opened by the process before generating the core dump file. Therefore, storage resources such as file handles occupied by the abnormal process are released in time before the core dump file is generated, so that the abnormal process can release the occupation of the storage resources in advance, other processes can use the storage resources in advance, and the resource utilization rate can be effectively improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application.
FIG. 1 is a flowchart of a method for processing a process exception event according to an embodiment of the present application;
FIG. 2 is a block diagram of a device for processing a process exception event according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure. Embodiments and features of embodiments in this application may be combined with each other arbitrarily without conflict. Also, while a logical order is depicted in the flowchart, in some cases, the steps depicted or described may be performed in a different order than presented herein.
The terms first and second in the description and claims of the present application and in the above-described figures are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the term "include" and any variations thereof is intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The term "plurality" in the present application may mean at least two, for example, two, three or more, and embodiments of the present application are not limited.
In addition, the term "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. The character "/" herein generally indicates that the associated object is an "or" relationship unless otherwise specified.
For easy understanding, the technical background of the embodiments of the present invention will be described first.
As described above, when an exception occurs in a process, it takes a long time to generate a core dump file, and the exception process always occupies resources such as a file handle and a file memory in the process of generating the core dump file, which causes waste of storage resources, so that the resource utilization rate is low. Moreover, if a large number of processes in the system are abnormal at the same time, a large number of storage resources are occupied by the abnormal processes, so that a service cluster is failed, and the reliability of the service is reduced.
At present, in order to solve the problems that the resource utilization rate is low and the service reliability is reduced due to the fact that a service cluster is easy to fail, one scheme is that when a server receives request information for generating an abnormal file, the server determines whether the abnormal file is allowed to be generated according to a white list and/or the operation times of allowing generation of the abnormal file in a delay period, if the abnormal file is allowed to be generated, a client is instructed to generate the abnormal file, and if the abnormal file is forbidden to be generated, the client does not generate the abnormal file. That is, the conventional scheme solves the above-mentioned technical problem by reducing the number of generated abnormal files. However, the client side for allowing to generate the abnormal file still occupies the storage resource for a long time due to the fact that the file handle cannot be released, the file system is unloaded and the disk array (raid) is stopped in the process of generating the abnormal file. Aiming at the client which is not allowed to generate the abnormal file, the abnormal file record is not available after the abnormal process exits, so that the technical staff is not beneficial to analyzing the reason of the abnormal process exits.
In view of this, the embodiment of the application provides a process exception event processing method, which closes a file handle opened by a process before a core dump file is generated, and at this time, storage resources occupied by the exception process are released, so that the exception process will not continue to occupy the storage resources in the process of generating the core dump file, and the utilization rate of the storage resources is effectively improved.
The following describes a method for processing a process abnormal event according to an embodiment of the present application with reference to the accompanying drawings. Referring to fig. 1, the flow of the process exception event handling method in the embodiment of the present application is described as follows:
step 101: a first indication signal is received.
In the Linux operating system, a user program runs in the form of a process in the system. When detecting that the process is abnormal in the running process, the Linux kernel sends a first indication signal to the process for indicating that the process is abnormal and needs to be exited. Wherein the process includes at least one thread.
In a process, a thread, for example, a first thread, is specifically configured to receive the first indication signal, and when the first thread receives the first indication signal, other threads will not receive the first indication signal any more.
Step 102: and determining whether the core dump file needs to be generated according to the first indication signal.
As described above, when an exception occurs in a process, the Linux kernel sends a first indication signal, where the first indication signal includes a first type signal that needs to generate a core dump file and a second type signal that does not need to generate a core dump file, where the first type signal mainly includes: SIGQUIT, SIGILL, SIGTRAP, SIGABRT, SIGFPE, SIGSEGV, SIGBUS, SIGSYS, SIGXCPU, SIGXFSZ.
When the first indication signal received by the first thread is a first type signal (e.g. SIGQUIT), it is determined that a core dump file needs to be generated, when the first indication signal received by the first thread is a second type signal (e.g. other than the first type signal), it is determined that a core dump file is not needed, and when it is determined that a core dump file does not need to be generated, a message is sent to other threads in the process to inform the other threads to exit the current running state, and when it is determined that a core dump file needs to be generated, step 103 is performed.
Step 103: and closing a file handle opened by the process when the core dump file needs to be generated.
In this embodiment of the present application, when the first thread receives the first indication signal and determines that the core dump file needs to be generated, the first thread may send a second indication signal (for example, SIGKILL) to other threads in the process for indicating that the other threads are disassociated from the file and exit from the running state, and when the other threads receive the second indication signal, disassociate from the process file descriptor table (i.e., disassociate from the process file descriptor table), and when the first thread determines that the other threads are disassociated from the process file descriptor table, close the file handle opened by the process.
Specifically, when a new thread is created in a process, the file pointer in the task_struct structure related to each new thread points to the same process file descriptor table, and the count in the process file descriptor table is increased by 1 to indicate that the process file descriptor table is occupied, that is, all threads in the process share one process file descriptor table, when other threads receive a second indication signal that the file association needs to be released and the running state is exited, the file pointer in the related task_struct structure is set to be a null pointer, and the count of the shared process file descriptor table is reduced by 1 to release the occupied process file descriptor table, when the count of the shared process file descriptor table is determined to be equal to 1, the first thread indicates that all other threads have successfully exited the running state, and at the moment, the first thread closes the file handle opened by the process.
For example, an exception process includes 10 threads, where the 10 threads share a process file descriptor table, when the process runs normally, the count of the file descriptor table is 10, thread 2 sends a signal SIGKILL to the other 9 threads when it determines that a core dump file needs to be generated according to the received first indication signal, the other 9 threads disassociate the process file descriptor table when the signal SIGKILL is received, whenever one thread successfully disassociates the process file descriptor table, the count of the shared process file descriptor table is decremented by 1, and when the count of the process file descriptor table is equal to 1, it indicates that only thread 2 of the process file descriptor table is still being used, and all other threads have successfully exited the running state, at this time, thread 2 closes the file opened by itself and the other 9 threads.
Specifically, when closing the file handle opened by the process, the first thread may further acquire a file handle list corresponding to the process, where the file handle list includes all file handles opened by the process, and the first thread may close all file handles opened by the process according to the file handle list. Wherein the file handle list may be generated from records in the file descriptor table.
After the file handle is closed, the process does not occupy the storage resources such as the file handle, namely the storage resources occupied by the process are released. This way, other processes can be allowed to use the storage resource in advance.
Step 104: a core dump file is generated.
In the embodiment of the application, when the first thread determines that the core dump file needs to be generated, a second indication signal for releasing the file association and exiting the running state is sent to other threads so that the other threads exit the running state, all file handles opened by the process are closed after the other threads are determined to release the file association and exit the running state, and then the core dump file is generated and exits the running state. Wherein the first thread is indicated as exiting the run state after the process exits the run state. That is, the first thread closes all file handles opened by the process before the core dump file is generated, so that the process will not occupy file related resources in the process of generating the core dump file, and the operating system can take over storage resources originally occupied by the abnormal process in advance and allocate the storage resources to other needed processes.
For example, in the dual-control storage system, when the dual-control host program exits abnormally to generate the core dump file, the file handle is closed in advance, so that the file system and the raid used by the abnormal process can be released in time, and the dual-control standby machine takes over the storage resource of the dual-control host safely and quickly.
Based on the same inventive concept, the embodiment of the application provides a process abnormal event processing device, which can realize the functions corresponding to the process abnormal event processing method. The process exception event handling means may be a hardware structure, a software module, or a hardware structure plus a software module. The process abnormal event processing device can be realized by a chip system, and the chip system can be formed by a chip or can contain the chip and other discrete devices. Referring to fig. 2, the process exception event processing apparatus includes a communication module 201 and a processing module 202. Wherein:
a communication module 201, configured to receive a first indication signal;
the processing module 202 is configured to determine, when the communication module 201 receives a first instruction signal, whether to generate a core dump file according to the first instruction signal, where the first instruction signal is used to instruct a process to generate an exception, and the core dump file is used to store information required for performing exception analysis, and the first thread belongs to the process;
the processing module 202 is further configured to close a file handle opened by the process when it is determined that the core dump file needs to be generated;
the processing module 202 is further configured to generate the core dump file.
In a possible implementation manner, the communication module 201 is further configured to:
and sending a second indication signal to other threads, wherein the second indication signal is used for indicating the other threads to disassociate files and exit from a running state, and the other threads are other threads except the first thread in the process.
In one possible implementation, the processing module 202 is specifically configured to:
acquiring a file handle list corresponding to the process;
determining all file handles opened by the process according to the file handle list;
and closing all file handles opened by the process.
In one possible implementation, after closing the file handle opened by the process, the storage resources occupied by the process are released.
All relevant contents of each step related to the foregoing embodiment of the process abnormal event processing method may be cited in the functional description of the functional module corresponding to the process abnormal event processing device in the embodiment of the present application, which is not described herein again.
The division of the modules in the embodiments of the present application is schematically only one logic function division, and there may be another division manner in actual implementation, and in addition, each functional module in each embodiment of the present application may be integrated in one processor, or may exist separately and physically, or two or more modules may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules.
Based on the same inventive concept, the embodiment of the application provides electronic equipment. Referring to fig. 3, the electronic device includes at least one processor 301 and a memory 302 connected to the at least one processor, in this embodiment, a specific connection medium between the processor 301 and the memory 302 is not limited, and in fig. 3, the connection between the processor 301 and the memory 302 through a bus 300 is taken as an example, and the bus 300 is shown in a bold line in fig. 3, and a connection manner between other components is only illustrative and not limited. The bus 300 may be divided into an address bus, a data bus, a control bus, etc., and is represented by only one thick line in fig. 3 for convenience of illustration, but does not represent only one bus or one type of bus.
In the embodiment of the present application, the memory 302 stores instructions executable by the at least one processor 301, and the at least one processor 301 may execute the steps included in the foregoing process exception event processing method by executing the instructions stored in the memory 302.
The processor 301 is a control center of the electronic device, and may use various interfaces and lines to connect various parts of the entire electronic device, and by executing or executing instructions stored in the memory 302 and invoking data stored in the memory 302, various functions of the electronic device and processing data, thereby performing overall monitoring on the electronic device. Alternatively, the processor 301 may include one or more processing units, and the processor 301 may integrate an application processor and a modem processor, wherein the application processor primarily processes an operating system and application programs, etc., and the modem processor primarily processes wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 301. In some embodiments, processor 301 and memory 302 may be implemented on the same chip, and in some embodiments they may be implemented separately on separate chips.
The processor 301 may be a general purpose processor such as a Central Processing Unit (CPU), digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, which may implement or perform the methods, steps and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method for processing the process abnormal event disclosed in the embodiment of the application can be directly embodied in a hardware processor or can be executed by a combination of hardware and software modules in the processor.
The memory 302 serves as a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 302 may include at least one type of storage medium, which may include, for example, flash Memory, hard disk, multimedia card, card Memory, random access Memory (Random Access Memory, RAM), static random access Memory (Static Random Access Memory, SRAM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read-Only Memory (ROM), charged erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory), magnetic Memory, magnetic disk, optical disk, and the like. Memory 302 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 302 in the present embodiment may also be circuitry or any other device capable of implementing a memory function for storing program instructions and/or data.
By programming the processor 301, the code corresponding to the process exception event processing method described in the foregoing embodiment may be cured into the chip, so that the chip can execute the steps of the foregoing process exception event processing method when running, and how to program the processor 301 is a technology known to those skilled in the art will not be repeated here.
Based on the same inventive concept, the embodiments of the present application also provide a computer-readable storage medium storing computer instructions that, when run on a computer, cause the computer to perform the steps of the process exception event handling method as described above.
In some possible embodiments, aspects of the method for processing a process exception event provided in the present application may also be implemented in the form of a program product, which includes a program code for causing a detection device to perform the steps in the method for processing a process exception event according to various exemplary embodiments of the present application described above in the present specification when the program product is run on an electronic device.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims (8)

1. A method for processing a process exception event, the method comprising:
when a first thread receives a first indication signal, determining whether a core dump file needs to be generated according to the first indication signal, wherein the first indication signal is used for indicating that an abnormality occurs in a process, the core dump file is used for storing information required for performing abnormality analysis, and the first thread belongs to the process;
if the core dump file needs to be generated, closing a file handle opened by the process when determining that other threads are disassociated from the file and exit from an operating state, and releasing storage resources occupied by the process after closing the file handle opened by the process, wherein the other threads are threads except the first thread in the process;
and generating the core dump file.
2. The method of claim 1, wherein the method further comprises:
and sending a second indication signal to the other threads, wherein the second indication signal is used for indicating the other threads to disassociate files and exit from a running state.
3. The method of claim 1, wherein closing the process open file handle comprises:
acquiring a file handle list corresponding to the process;
determining all file handles opened by the process according to the file handle list;
and closing all file handles opened by the process.
4. A process exception event handling apparatus for application to a first thread, the apparatus comprising:
the communication module is used for receiving the first indication signal;
the processing module is used for determining whether a core dump file needs to be generated according to a first indication signal when the communication module receives the first indication signal, wherein the first indication signal is used for indicating that an abnormality occurs in a process, the core dump file is used for storing information required for performing abnormality analysis, and the first thread belongs to the process;
the processing module is further configured to close the file handle opened by the process when it is determined that the core dump file needs to be generated, and it is determined that other threads are disassociated from the file and exit from the running state, and after the file handle opened by the process is closed, storage resources occupied by the process are released, where the other threads are threads in the process except the first thread;
the processing module is further configured to generate the core dump file.
5. The apparatus of claim 4, wherein the communication module is further to:
and sending a second indication signal to the other threads, wherein the second indication signal is used for indicating the other threads to disassociate files and exit from a running state.
6. The apparatus of claim 4, wherein the processing module is specifically configured to:
acquiring a file handle list corresponding to the process;
determining all file handles opened by the process according to the file handle list;
and closing all file handles opened by the process.
7. An electronic device, comprising:
a memory for storing program instructions;
a processor for invoking program instructions stored in said memory and for performing the steps comprised in the method according to any of claims 1-3 in accordance with the obtained program instructions.
8. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program comprising program instructions which, when executed by a computer, cause the computer to perform the method of any of claims 1-3.
CN202110564156.2A 2021-05-24 2021-05-24 Method and device for processing process abnormal event, electronic equipment and storage medium Active CN113220495B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110564156.2A CN113220495B (en) 2021-05-24 2021-05-24 Method and device for processing process abnormal event, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110564156.2A CN113220495B (en) 2021-05-24 2021-05-24 Method and device for processing process abnormal event, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113220495A CN113220495A (en) 2021-08-06
CN113220495B true CN113220495B (en) 2024-04-16

Family

ID=77097929

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110564156.2A Active CN113220495B (en) 2021-05-24 2021-05-24 Method and device for processing process abnormal event, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113220495B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117724892A (en) * 2023-05-30 2024-03-19 荣耀终端有限公司 Dump data generation method, electronic device and storage medium

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005301570A (en) * 2004-04-09 2005-10-27 Nippon Telegr & Teleph Corp <Ntt> Process dumping method, device and program
US7028056B1 (en) * 2000-04-14 2006-04-11 Microsoft Corporation Method and arrangements for generating debugging information following software failures
US7290175B1 (en) * 2002-08-26 2007-10-30 Unisys Corporation Forcing a memory dump for computer system diagnosis
CN101599039A (en) * 2008-06-03 2009-12-09 华为技术有限公司 Abnormality eliminating method and device under the embedded type C language environment
CN107025135A (en) * 2017-03-03 2017-08-08 网易(杭州)网络有限公司 Application process management method, device and medium in Docker containers
CN107197050A (en) * 2017-07-27 2017-09-22 郑州云海信息技术有限公司 The method and system that file writes in a kind of distributed memory system
WO2019071616A1 (en) * 2017-10-09 2019-04-18 华为技术有限公司 Processing method and device
CN110032502A (en) * 2018-01-11 2019-07-19 武汉斗鱼网络科技有限公司 A kind of method, apparatus and electronic equipment of abnormality processing
CN111563000A (en) * 2020-04-28 2020-08-21 深圳震有科技股份有限公司 File generation method, intelligent terminal and storage medium
CN111625383A (en) * 2020-05-22 2020-09-04 北京达佳互联信息技术有限公司 Process abnormal event processing method and device, electronic equipment and storage medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8122517B2 (en) * 2008-04-02 2012-02-21 International Business Machines Corporation Mediated access of software dumped data through specialized analysis modules
US9740551B2 (en) * 2014-12-02 2017-08-22 International Business Machines Corporation Enhanced restart of a core dumping application

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7028056B1 (en) * 2000-04-14 2006-04-11 Microsoft Corporation Method and arrangements for generating debugging information following software failures
US7290175B1 (en) * 2002-08-26 2007-10-30 Unisys Corporation Forcing a memory dump for computer system diagnosis
JP2005301570A (en) * 2004-04-09 2005-10-27 Nippon Telegr & Teleph Corp <Ntt> Process dumping method, device and program
CN101599039A (en) * 2008-06-03 2009-12-09 华为技术有限公司 Abnormality eliminating method and device under the embedded type C language environment
CN107025135A (en) * 2017-03-03 2017-08-08 网易(杭州)网络有限公司 Application process management method, device and medium in Docker containers
CN107197050A (en) * 2017-07-27 2017-09-22 郑州云海信息技术有限公司 The method and system that file writes in a kind of distributed memory system
WO2019071616A1 (en) * 2017-10-09 2019-04-18 华为技术有限公司 Processing method and device
CN110032502A (en) * 2018-01-11 2019-07-19 武汉斗鱼网络科技有限公司 A kind of method, apparatus and electronic equipment of abnormality processing
CN111563000A (en) * 2020-04-28 2020-08-21 深圳震有科技股份有限公司 File generation method, intelligent terminal and storage medium
CN111625383A (en) * 2020-05-22 2020-09-04 北京达佳互联信息技术有限公司 Process abnormal event processing method and device, electronic equipment and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
dump和coredump;gogoky;《https://www.it610.com/article/5273413.htm》;20160429;第1-3页 *
张淼,邵帅,王浩宇编著.《移动终端安全》.北京:北京邮电大学出版社,2019,第136-139页. *

Also Published As

Publication number Publication date
CN113220495A (en) 2021-08-06

Similar Documents

Publication Publication Date Title
CN110018914B (en) Shared memory based message acquisition method and device
US3771146A (en) Data processing system interrupt arrangements
US9274798B2 (en) Multi-threaded logging
CN109788068B (en) Heartbeat state information reporting method, device and equipment and computer storage medium
US20130160028A1 (en) Method and apparatus for low latency communication and synchronization for multi-thread applications
US7380245B1 (en) Technique for detecting corruption associated with a stack in a storage device
CN110737534A (en) Task processing method and device and server
CN111209110A (en) Task scheduling management method, system and storage medium for realizing load balance
CN111538585B (en) Js-based server process scheduling method, system and device
CN111090502A (en) Streaming data task scheduling method and device
CN111651595A (en) Abnormal log processing method and device
CN115185777A (en) Abnormity detection method and device, readable storage medium and electronic equipment
CN113220495B (en) Method and device for processing process abnormal event, electronic equipment and storage medium
CN113157411A (en) Reliable configurable task system and device based on Celery
CN111831408A (en) Asynchronous task processing method and device, electronic equipment and medium
CN110908866A (en) Software monitoring method and related equipment
CN117591327A (en) core file generation method and device, electronic equipment and storage medium
CN111241594B (en) Method, device, computer equipment and storage medium for signing transaction information
CN117785440A (en) Abnormal process processing method, related device, equipment and storage medium
CN110764962A (en) Log processing method and device
CN112559565A (en) Abnormity detection method, system and device
CN115658295A (en) Resource scheduling method and device, electronic equipment and storage medium
CN114116230A (en) Resource management method, device, equipment, medium and product
CN114741218A (en) Method, device, equipment, system and medium for extracting abnormal index of operating system
CN111404715B (en) Network service instantiation method and device, electronic 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
GR01 Patent grant
GR01 Patent grant