140 results about "Crash" patented technology

The invention relates to a fuzzy test Kubernete-based three-party component vulnerability mining method, which comprises the following steps of: firstly, automatically identifying a user controllable function by combining a large language model based on an official document, a configuration list and source code information of a three-party component, and constructing a keyword dictionary to assist in large-scale identification of a potential target function; then analyzing context information of the target function and an interaction relation of the target function in a Kubernetes cluster, constructing a front dependency library required by fuzzy testing, and automatically generating a fuzzy testing driving program; integrating a fuzzy test driving program with a three-party component source code, performing code instrumentation, pre-compiling and corpus optimization, generating test input according to a set variation strategy, dynamically monitoring a coverage rate and an abnormal behavior, and continuously optimizing a test corpus; and finally, based on the crash behavior of the fuzzy test record, analyzing a trigger path of the vulnerability, performing vulnerability verification in a local Kubernetes cluster environment, and finally generating a vulnerability analysis report.

The invention relates to the technical field of equipment firmware updating, in particular to an AIoT equipment updating method and system.The AIoT equipment updating method comprises the following steps that the process state verification memory address overlapping rate is collected to generate a to-be-updated block, the to-be-updated block is extracted, network parameters are normalized, cosine similarity is calculated, and an updating mark is generated; generating a replacement or skipping instruction by combining the block and the mark comparison version hash, writing incremental data, judging the number of failures through a Q-Learning model, counting the number of failures, analyzing the global state, and executing recovery or version updating. According to the method, the upgrading interruption risk is reduced by dynamically recognizing the memory address conflict overlapping region, the network bandwidth, the packet loss rate and the storage delay parameter are evaluated to avoid low-efficiency updating, the version compatibility is accurately judged through Hash comparison to prevent system crash, the load prediction failure risk is analyzed in combination with Q-Learning, and the updating robustness is enhanced. And a multi-level fault-tolerant mechanism is established to maintain basic functions of the equipment by counting the number of failures, and stability and efficiency are improved by cooperating with dynamic scheduling and environmental perception.

The invention provides an automatic bug fixing method based on a large model sensing dynamic program state. The method comprises the following steps of: 1, running verification: verifying existence of vulnerabilities through running, and extracting non-crash constraints; step 2, obtaining an expected state in a repair positioning step, obtaining the expected state based on non-collapse constraint, specifically obtaining the expected state of a collapse position and obtaining the expected state of a potential repair position; 3, a debugging process in the positioning step is repaired, an interface set is provided for the LLM, a program real state is obtained based on program debugging, and static information is obtained based on a tool set; and 4, summarizing debugging information, and generating and verifying patches. According to the method, an actual running state is obtained through program debugging, and an expected state is deduced based on collapse free constraints. By continuously comparing the two states, the nature of the vulnerability can be deeply understood, so that a more accurate and effective repair patch is generated, and the patch repair accuracy, effectiveness and actual availability are remarkably improved.

The invention discloses a position and knowledge similarity-based software crash error repair scheme recommendation method, which outputs a repair method for error codes according to generated crash stack tracking information and corresponding codes when software crashes, and can help developers to quickly and efficiently solve the problem of software crash. When the method works, firstly, a context knowledge base is constructed, problem posts containing crash stacks on Stack Overflow are preprocessed, a knowledge base and an abnormal dictionary are constructed, and a language model is trained; thirdly, a related question set is preliminarily obtained through stack tracking, the comprehensive similarity of the question and an input stack is calculated through the position related similarity and the additional knowledge similarity, and the most related question and answer set is returned; and finally, performing relevancy calculation on the answer paragraphs based on multiple features, selecting paragraphs related to the crash reason by applying an MMR algorithm, and outputting root cause analysis and repair code snippets related to the crash error.

The invention provides a system operation lagging construction method and device, equipment, a medium and a program product. Relates to the technical field of system performance testing. The method comprises the steps that the CPU thread number and a watchdog threshold value of a current system are obtained; on the basis of the CPU thread number and the watchdog threshold value, the duration of the target thread executing busy waiting operation is calculated through a preset formula; initializing a spin lock of a kernel mode, and creating target threads of which the number is the same as that of the CPU threads, so that the target threads execute preset processing logic to construct system operation jamming; the preset processing logic comprises the following steps: periodically obtaining a spin lock; responding to the situation that the spin lock is not obtained, and continuing to execute the spin lock obtaining operation; and in response to obtaining the spin lock, executing a busy waiting operation. According to the method, CPU resources are continuously occupied through kernel spin lock competition, and a real system jamming scene is simulated. The busy waiting operation duration is dynamically calculated, it is ensured that the single-thread lock holding time is slightly lower than a watchdog threshold value, and crash of a system triggering unrecoverable is avoided.

Techniques for limiting or reducing storage accessibility “hiccups” in active-active clustered systems that perform large writes. The techniques can include executing, by a surviving, failover, or rebooted node of an active-active clustered system, a specialized recovery protocol that includes treating each large write request from a host computer as a plurality of small write requests while execution of the specialized recovery protocol is in progress, draining all dedicated sub-ubers for a primary and secondary node of the active-active clustered system, and, having completed execution of the specialized recovery protocol, resuming normal treatment of large write requests from the host computer. In this way, the need and complexity of managing large writes and maintaining their corresponding sub-uber information during recovery from a forced reboot, crash, or disaster involving the primary or secondary node can be avoided, and storage accessibility hiccups due to performing the large writes can be limited or reduced.

Systems and methods include an Information Handling System (IHS) that is adapted to provide crash handling that is particularized to each phase of the IHS boot sequence. A boot sequence is initiated that includes two or more phases. Prior to each phase of the boot sequence, a crash handler is initiated that is configured to collect state information for IHS hardware configured during that respective phase of the boot sequence. Upon detecting a boot sequence crash by the IHS, the crash handler operating during the phase of the boot sequence of the crash stores hardware state information it has collected to a shared memory location.

The invention discloses an industrial edge application dynamic updating method based on a microkernel, and relates to the field of industrial automation. Designing an industrial edge application based on the microkernel; and constructing a function block as a thread, and dynamically updating the industrial edge application by reconfiguring a thread entry point address. The microkernel architecture is mainly used for designing an operating system, the most basic core functions (scheduling, inter-process communication and address space management) in the operating system are realized, and all other functions such as a file system and a device driver are operated in a user layer as independent services. All services run in different address spaces in the form of threads, different services can be strictly isolated by combining access control based on Capability, and other services and kernels cannot be affected by collapse of any service. The micro-kernel architecture also adopts a modular design, and any independent module can realize thread-level loading and updating, so that dynamic updating and expansion are facilitated.

The invention provides a concurrent vulnerability fuzzy test method and device supporting reproduction, and relates to the technical field of computers, the method comprises the following steps: obtaining a target program obtained by rewriting an original binary program; wherein the target program comprises a plurality of key basic blocks, and the execution sequence of the key basic blocks is used as a thread interleaving feedback signal; performing thread staggering variation based on the key basic block to generate a plurality of target test cases containing a plurality of thread staggering conditions; performing a fuzzy test based on the plurality of target test cases, and reproducing a crash scene based on execution information of the target program under the condition that the target program is triggered to crash in the fuzzy test process; wherein the execution information is obtained by recording the execution sequence of the key basic blocks in the execution process of the target program. Through the method provided by the invention, concurrent vulnerabilities can be effectively mined, and recurrent fuzz testing can be carried out.

The invention discloses an application crash processing method and device, equipment and a medium, when it is detected that an application crash event occurs, crash state information of the crash event is obtained, whether a crash positioning result of the crash event is code crash or data crash is determined according to the crash state information, and if the crash positioning result is code crash, the application crash processing method is executed. If the crash event is a data crash event, obtaining a current operation interface where the crash event is located, and controlling the current operation interface to perform interface switching operation based on a preset interface switching mode, and if the crash positioning result is data crash, determining a repair level for automatically repairing the application, and performing clearing operation on cache data of the application according to the repair level. And automatic repair is realized. It can be seen that when the code crash is determined, the interface switching operation is performed based on the preset interface switching mode, and when the data crash is determined, the application is automatically repaired, so that the application crash can be quickly and effectively repaired, and the user experience is enhanced.

The invention discloses a core dump crash reason positioning method and device, equipment and a storage medium, relates to the technical field of code fault positioning, and discloses a core dump crash reason positioning method, which comprises the following steps of: obtaining a program source code and running log information, and analyzing a core dump file to obtain crash state information; constructing an address-function-code mapping relation through the crash state information and the program source code; positioning a fault code in the program source code according to the address-function-code mapping relation to obtain a program call chain and a fault code block; and positioning a core dump crash reason according to the fault code block, the program call chain and the running log information. Through the technical means of fusing the crash state information, the program source code and the running log information and constructing the address-function-code mapping relation, the technical effect of accurately positioning the core dump crash reason is achieved.

The invention discloses an optimization sensitive test system and method for an AI compiler, and belongs to the technical field of software testing. The method mainly comprises the following steps: firstly, automatically extracting an IR sub-graph mode capable of triggering specific optimization Pass from an existing test of a compiler through dynamic instrumentation; secondly, through a strategy of multiplexing compatible nodes or creating new nodes, the optimization modes are intelligently synthesized into a diversified seed calculation graph context, and a large number of test cases capable of effectively triggering compiler optimization are generated; and finally, efficiently revealing the defects of the AI compiler in the optimization stage by taking crash detection and reasoning consistency comparison as test predictions. The defect that an existing random generation or grammar generation method is insufficient in test coverage rate in the optimization stage is overcome, the deep optimization defect in the AI compiler can be automatically and efficiently detected, and the method has the high error detection rate and good universality.

The invention discloses a method and device for storing crash information, and relates to the technical field of safety protection. The method comprises the following steps: when a first kernel is started, reserving a system memory with target capacity as an information storage area through the first kernel; when the firewall is started, loading the second kernel into the memory by using the kernel calling command; when it is detected that the first kernel crashes, based on a crash recording function, crash information needing to be stored is written into the information storage area; wherein the crash information is used for representing an error report recorded in real time when the kernel crashes; after the second kernel is started, a crash information reading tool is used for reading the data in the information storage area and writing the data into a disk, a crash information record is obtained, and restarting operation is executed. The method is used for achieving the function of storing the crash information.

The invention discloses a storage system fault processing method and electronic equipment, and relates to the technical field of computers. The load mode of a storage system is determined to be a light load mode or a heavy load mode based on load information of the storage system; according to the method, differential fault processing strategies are implemented in combination with the weight of the system load information and the current fault level to process the load fault, system crash caused by blind execution of recovery operation under high load is avoided, meanwhile, the recovery process is accelerated under low load, and therefore the fault-tolerant capability and stability of the storage system are comprehensively improved.

The invention provides a method and system for analyzing system crash, and the method for analyzing the system crash comprises the following steps: firstly, obtaining a parameter group through a system interface; then, marking a parameter group; then, when the system crashes, grabbing the Ramdump information and the useful information in the parameter group; thirdly, storing the Ramdump information and the useful information into a specified partition; analyzing data in the Ramdump information by using the useful information so as to find clues of system crash; in this way, the Ramdump data can be directly grabbed and analyzed without additionally storing and keeping symbol files of various versions and without an analysis function provided by additional external software.

The invention provides a crash processing method and device for a startup application, equipment and a storage medium, and the method comprises the steps: monitoring the crash frequency of the startup application in real time after the startup application of electronic equipment is started and runs; and if the crash frequency is greater than or equal to a preset threshold value, stopping running the startup application, configuring an environment variable of the electronic equipment and broadcasting startup completion information to related applications in the electronic equipment so as to trigger the related applications to start and run. The crash frequency of the startup application is judged, if the crash frequency is larger than or equal to the preset threshold value, running of the startup application is stopped, the environment variables of the electronic equipment are configured, and the startup completion information is broadcasted to the related applications in the electronic equipment, so that the related applications are triggered to start running; the problem that the user cannot normally enter the desktop to use the electronic equipment due to the crash of the startup application is solved, the use experience of the user is ensured, and the complaint rate and the churn rate of the user are reduced.

Systems and methods include an Information Handling System (IHS) that is adapted to provide crash handling that is particularized to each phase of the IHS boot sequence. A boot sequence is initiated that includes two or more phases. Prior to each phase of the boot sequence, a crash handler is initiated that is configured to collect state information for IHS hardware configured during that respective phase of the boot sequence. Upon detecting a boot sequence crash by the IHS, the crash handler operating during the phase of the boot sequence of the crash stores hardware state information it has collected to a shared memory location.

Systems and methods for in-system, self-recovery (ISSR) in a system-on-a-chip (SoC) are disclosed for detecting and recovering from a bit corruption event that has caused an SoC subsystem to crash. If a bit flip event is detected through observation of a subsystem crash, ISSR steps are taken in an attempt to correct the issue. If the ISSR steps are successful, then the system is not halted and mission mode operations continue. If the ISSR steps are unsuccessful, then the system is halted and an return material authorization (RMA) can then be issued for return of the failed part to the OEM. Crash events and self-recovery attempts preferably are logged by the ISSR system and provided to the OEM.

The invention discloses an exception handling method. The method can be applied to an application program. A user can trigger the application program starting operation, and correspondingly, the application program can receive the application program starting operation and respond to the application program starting operation. If the number of times that the application program continuously generates the startup crash reaches a preset number of times, the application program can display at least one interaction identifier, and the at least one interaction identifier is used for triggering an interaction operation for solving the startup crash. Therefore, a user can trigger the interaction operation for solving the startup crash through the at least one interaction identifier to solve the startup crash, so that the user can normally use the application program. Therefore, according to the scheme, a user does not need to execute a series of operations, the interaction operation for solving the startup crash can be triggered through the at least one interaction identifier, the user operation is convenient, and the user experience can be improved.

The application discloses a file naming method and an electronic device, relates to the software field, and is used for helping to locate a crashed process by naming a crash report file as the name of the crashed process. The file naming method is applied to a Crashpad run by the electronic device, the Crashpad comprises a Crashpad processing end and a Crashpad client, and the method comprises the following steps: in response to a crash of a target process, the Crashpad processing end acquires a command line of the target process, the command line comprising the name of the target process; the Crashpad processing end analyzes the command line to obtain the name of the target process; the Crashpad processing end sends a target string to the Crashpad client; and the Crashpad client converts a crash report into a crash report file named by the target string, the target string comprising the name of the target process.

The invention is suitable for the technical field of plug-in management, and provides a plug-in operation control method, device and equipment, and the method comprises the steps: responding to a starting instruction of a main plug-in, when the current process state of a sub-plug-in is determined to be crash, obtaining historical operation data and configuration information of the sub-plug-in, and according to the historical operation data and the configuration information, starting the sub-plug-in according to the historical operation data and the configuration information; and determining whether the sub-plug-in executes a restart strategy or a recovery strategy, controlling the sub-plug-in to restart when determining that the sub-plug-in executes the restart strategy, and updating and recovering the sub-plug-in when determining that the sub-plug-in executes the recovery strategy. Through the method and the device, the problem that the overall running reliability of the main plug-in is influenced due to process crash of the sub-plug-in can be solved.

The present invention provides a method, device, electronic device, and storage medium for locating the location of a program crash. The method includes: when a system crash occurs during program execution, obtaining the globally unique identifier of the current program module running at the time of the crash and the entry physical address corresponding to the globally unique identifier of the current program module; reading the physical address of the instruction address register stored in the instruction address register in the system at the time of the crash; subtracting the entry physical address from the physical address of the instruction address register to obtain a first offset address; obtaining a first mapping file corresponding to the globally unique identifier of the current program module; searching for the first function name corresponding to the first offset address; searching for the offset address of the function corresponding to the first function name according to the first mapping file; using the offset address of the function corresponding to the first function name as the crash location and outputting it. The present invention can locate the crash location of a program.

The application belongs to the technical field of computer storage, and specifically discloses a method and device for ensuring crash consistency of persistent memory data. The method comprises the following steps: removing a log operation for ensuring crash consistency of memory data in a system; after the system crashes and restarts, performing a log-free crash recovery process; the log-free crash recovery process is used for sequentially scanning each encoding strip stored in a memory space, so that when data crash inconsistency occurs in the encoding strip, original check data of the encoding strip is used for data recovery. Through the application, the write performance of the persistent memory system can be effectively enhanced, the delay and throughput of the system can be significantly improved, and the overall performance of the system can be improved.

This application discloses a program running method and apparatus. The method and apparatus determine a target process to be allocated to a lightweight program from a preset program process, wherein each preset program process has independent running resources; the target process's running resources uniquely run the lightweight program with the allocated relationship. By limiting the number of preset program processes and ensuring that the corresponding target process exclusively occupies running resources during the lightweight program's operation, process-level isolation between different lightweight programs is achieved. A crash in a single lightweight program only affects its own process and will not cause abnormalities in the host app or other lightweight programs, thus ensuring overall operational stability. Each process uniquely runs its corresponding lightweight program, avoiding conflicts caused by multiple instances sharing process resources and improving the independence and reliability of lightweight program operation.

The application is an independent automatic crash detection software development kit, which provides an improved SDK so that the SDK itself can determine whether the crash is related to it when the crash occurs. The SDK includes a set of APIs and a crash handler registered with the operating system. Each API is an interface accessible by computer software applications. Each API determines the current thread ID at the entry, and if the current thread ID is not in the list of thread IDs and their corresponding API call counters, it is inserted into the list. Each thread ID corresponds to an API call counter, which is incremented by 1 at the API entry and decremented by 1 at the API exit. The SDK also records the threads created internally. When a crash occurs, the crash handler is executed. If the crash thread belongs to the internal thread, it is determined that the crash is related to the SDK; otherwise, further determine whether the API call counter corresponding to the crash thread ID is greater than zero, and also determine that the crash is related to the SDK.

Systems and methods for in-system, self-recovery (ISSR) in a system-on-a-chip (SoC) are disclosed for detecting and recovering from a bit corruption event that has caused an SoC subsystem to crash. If a bit flip event is detected through observation of a subsystem crash, ISSR steps are taken in an attempt to correct the issue. If the ISSR steps are successful, then the system is not halted and mission mode operations continue. If the ISSR steps are unsuccessful, then the system is halted and an return material authorization (RMA) can then be issued for return of the failed part to the OEM. Crash events and self-recovery attempts preferably are logged by the ISSR system and provided to the OEM.

The application discloses a kind of methods for monitoring crash log, equipment, device and storage medium, the method comprises: if the application program of running exists exception is monitored, the exception data corresponding to the application program is obtained;Abnormal data is filtered and handled based on the exception type corresponding to the exception type, and the filtered exception data is stored. By quickly investigating the exception of application program, so that the developer more timely, accurate solution crash problem.

The present disclosure provides a file parsing method, apparatus, computer equipment and storage medium, wherein the method comprises: obtaining a crash file generated when an application crashes; the crash file comprises at least one type of information: system information, crash stack information, and library information; determining a first identification code in the crash file; wherein the first identification code is used to indicate a target executable file for parsing the crash file; when it is determined that the first identification code does not meet the identification requirements, querying a target mapping table for a second identification code that matches the crash file; the target mapping table is used to indicate a mapping relationship between a resource library and an identification code contained in the application; and parsing the crash file based on the second identification code to obtain a file parsing result.

The embodiment of the invention provides an application monitoring method and device, equipment, a storage medium and a program product, and relates to the field of big data. The method comprises the following steps: in response to a captured memory exception event when a to-be-monitored application runs, acquiring memory stack information corresponding to the memory exception event; wherein the memory exception event comprises at least one of a memory leak event, a memory depletion event and an exceptional memory allocation event; the memory stack information, the crash event data and the operation behavior data are subjected to association analysis, an association analysis result is obtained, and the association analysis result comprises associated transaction identifiers and corresponding memory stack information within a preset duration before the crash triggering time; and according to the correlation analysis result, identifying an abnormal reason of the to-be-monitored application. According to the method, the abnormal problem identification accuracy of the application can be effectively improved.

The invention discloses a global monitoring and collecting method and device for Android application crash information and a medium, belongs to the technical field of mobile terminal technologies, and is used for solving the problems that existing Android terminal crash information monitoring is not comprehensive, specific reasons of crash are difficult to locate, use experience of a user is not facilitated, and user experience is poor. And the processing complexity of a developer is increased. The method comprises the following steps: performing data monitoring processing on crash information of a Java layer by customizing a default uncaptured abnormal processor of a system, and collecting and obtaining Java layer crash structured data; the method comprises the following steps: intercepting key crash signals of a Native layer through a global signal processor, and asynchronously acquiring and obtaining Native layer crash related data; performing structured assembly of related data packets on the Java layer crash structured data and the Native layer crash related data, and performing asynchronous transmission to obtain a crash report; and transmitting the crash report to a server through the asynchronous queue to obtain crash report information.