Software System State Recovery via Core Dump Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Unintentional software system shutdowns on computer platforms result in data loss and require users to manually redeploy applications and documents, leading to inefficiencies and potential data corruption due to outdated checkpoints.

Innovation Solution

Generating a core dump file upon shutdown, which allows for the copying of software system-related data back into the system upon restart, enabling the software system to continue execution from its previous state, thereby reducing runtime overhead and manual redeployment needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If checkpoints are saved to restore application state after shutdown, then data recovery is improved, but runtime overhead increases due to continuous checkpoint generation

Engineering Contradiction:
Improvedata recoveryVSAvoidruntime overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the checkpoint saving operation from continuous runtime execution and performs it only at shutdown. The core dump is generated once when the application exits, rather than continuously during operation. This eliminates the runtime overhead of continuous checkpoint generation while maintaining the ability to recover application state after shutdown by loading the saved core dump data.

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of information

If application state is continuously saved to maintain data integrity, then data loss is reduced, but system performance deteriorates due to frequent I/O operations

Engineering Contradiction:
Improvedata lossVSAvoidsystem performance
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent implements periodic action by saving the application state only at specific intervals - namely at shutdown. Instead of continuous or frequent periodic saving during runtime, the core dump is generated once when the application exits. This reduces the frequency of I/O operations from continuous/multiple times per hour to once per shutdown event, significantly improving system performance while still capturing the application state for recovery.

Inventive Principle:
Principle #19Periodic action

3Device complexity

If manual redeployment of applications and documents is required after shutdown, then system simplicity is maintained, but user productivity decreases due to time-consuming manual restoration

Engineering Contradiction:
Improvesystem simplicityVSAvoidmanual restoration time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent implements self-service by enabling the system to automatically restore application state without user intervention. The library automatically detects the core dump file, loads the saved application state data (including window positions, document locations, and application configurations), and restores the application to its previous state. This eliminates the need for users to manually redeploy applications and documents, reducing restoration time from potentially minutes to automatic background processing.

Inventive Principle:
Principle #25Self-service

4Reliability

If core dump files are generated for every shutdown to enable recovery, then data integrity is improved, but storage requirements increase

Engineering Contradiction:
Improvedata integrityVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent treats core dump files as disposable temporary objects rather than permanent storage requirements. The core dump is generated at shutdown, used immediately upon restart to restore application state, and then can be discarded. This approach accepts the storage cost of temporary core dump files as a necessary trade-off for enabling automatic recovery, but the files are short-lived and only exist transiently during the restart process rather than being retained long-term.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS9164846B2Restarting a software system
Publication Date: 2015.10.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9164846B2 patent drawing
  • US9164846B2 patent drawing
  • US9164846B2 patent drawing

AI summary

In one aspect, a technique for restarting a software system on a computer platform after an unintentional software system shutdown. The technique includes, for instance, generating a core dump file on the computer platform when the software system shuts down unintentionally, restarting the software system, using a library for copying software system related data from the core dump file to the software system, and continuing execution of the software system.