Program Crash Signature Isolation via Stack Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for determining the reason for a program crash are inaccurate due to varying signatures across different computer systems and environments, leading to incorrect identification of crash causes in application programs.
Innovation Solution
A method and device that acquire and analyze stack information during a program crash, isolating first stack information specific to the application program to generate a unique signature for crash identification, independent of system settings, using algorithms like MD5 for identification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If conventional signature methods are used for program crashes, then the signature generation process is simple, but the signature varies across different computer systems and environments leading to inaccurate crash reason determination
Solution Approach 1:
The patent segments the stack information into two distinct parts: first stack information specific to the application program process, and second stack information related to the computer system environment. By separating these components, the invention isolates the application-specific signature elements from system-dependent variations, enabling accurate crash reason determination across different environments while maintaining a manageable signature generation process
Solution Approach 2:
The patent extracts and removes the second stack information (system environment-related) from the complete stack information to retain only the first stack information (application program-specific). This extraction process eliminates the source of variability caused by different computer systems and running environments, allowing the signature to accurately reflect the crash reason without being influenced by external system differences
2Stability of the object's composition
If system-specific stack information is included in the signature, then the signature reflects the complete crash context, but the signature becomes inconsistent across different running environments
Solution Approach 1:
The patent divides the stack information into application-specific and system-specific segments, retaining only the application-specific first stack information for signature generation. This segmentation preserves the essential crash context related to the application's execution flow while discarding system environment details that cause inconsistency, achieving both signature stability and relevant information retention
Solution Approach 2:
The patent applies local quality by making the signature generation process selective about which stack information to include. Instead of uniformly including all stack information, it specifically selects and retains only the portion (first stack information) that has consistent quality across different running environments, while excluding the variable system-related portions
Data Source
AI summary
A method and a device for signing a program crash are disclosed, which are applied to the filed of communication technology. The device for signing the program crash firstly acquires stack information invoked when the program crash occurs during executing a process of an application program by a computer system, then acquires first stack information corresponding to the process of the application program from the acquired stack information, and signs the occurred program crash based on the first stack information.