Correlation of source code with system dump information

Patent metadata

Field	Value
Publication number	US-10437703-B2
Application number	US-201715396715-A
Country	US
Kind code	B2
Filing date	Jan 2, 2017
Priority date	Dec 21, 2012
Publication date	Oct 8, 2019
Grant date	Oct 8, 2019

Abstract

The present arrangements relate to analyzing a software error. At least one dump file created in response to a crash of software executing on a processing system can be accessed. Based on the dump file, a base version of at least one software module that was loaded when the crash occurred can be identified. Based on the dump file, maintenance that has been applied to the at least one software module also can be identified. A report recommending new corrective maintenance to be applied to the at least one software module can be generated.

First claim

What is claimed is:

1. A computer-implemented method, performed within a computer hardware system, of analyzing a crash in software, comprising:
identifying, based on a dump file, a base version of a software module that was loaded when the crash occurred;
identifying, based on the dump file, maintenance that was previously applied to the software module; and
identifying, based upon the base version of the software module and the maintenance that was previously applied to the software module, new corrective maintenance to be applied to the software module, wherein
the dump file is created in response to the crash, and
the base version of the software module is different than a version of the software module that was loaded when the crash occurred.

2. The method of claim 1 , further comprising:
generating an output file including:
source code for the software module, and
the maintenance that was previously applied to the software module.

3. The method of claim 1 , wherein
the base version is identified by processing memory structures contained in the dump file to locate areas in the memory structures that contain information about the software module that was loaded when the crash occurred.

4. The method of claim 3 , wherein
the processing the memory structures includes identifying entries in a loader domain and a program manager domain.

5. The method of claim 1 , wherein
the maintenance indicates updates that have been applied to the base version.

6. The method of claim 1 , further comprising:
identifying a plurality of software modules that were loaded when the crash occurred; and
identifying, for the plurality of software modules, additional maintenance updates that were not applied to the plurality of software modules.

7. A computer hardware system configured to analyze a crash in software, comprising:
a hardware processor programmed to initiate the following executable operations:
identifying, based on a dump file, a base version of a software module that was loaded when the crash occurred;
identifying, based on the dump file, maintenance that was previously applied to the software module; and
identifying, based upon the base version of the software module and the maintenance that was previously applied to the software module, new corrective maintenance to be applied to the software module, wherein

the dump file is created in response to the crash, and
the base version of the software module is different than a version of the software module that was loaded when the crash occurred.

8. The system of claim 7 , wherein the hardware processor is further programmed to initiate the following executable operations:
generating an output file including:
source code for the software module, and
the maintenance that was previously applied to the software module.

9. The system of claim 7 , wherein
the base version is identified by processing memory structures contained in the dump file to locate areas in the memory structures that contain information about the software module that was loaded when the crash occurred.

10. The system of claim 9 , wherein
the processing the memory structures includes identifying entries in a loader domain and a program manager domain.

11. The system of claim 9 , wherein
the maintenance indicates updates that have been applied to the base version.

12. The system of claim 9 , wherein the hardware processor is further programmed to initiate the following executable operations:
identifying a plurality of software modules that were loaded when the crash occurred; and
identifying, for the plurality of software modules, additional maintenance updates that were not applied to the plurality of software modules.

13. A computer program product for analyzing a crash in software, comprising:
a hardware storage device having program code stored thereon,
the program code, which when executed by a computer hardware system, causes the computer hardware system to perform:
identifying, based on a dump file, a base version of a software module that was loaded when the crash occurred;
identifying, based on the dump file, maintenance that was previously applied to the software module; and
identifying, based upon the base version of the software module and the maintenance that was previously applied to the software module, new corrective maintenance to be applied to the software module, wherein

the dump file is created in response to the crash, and
the base version of the software module is different than a version of the software module that was loaded when the crash occurred.

14. The computer program product of claim 13 , wherein the hardware processor is further programmed to initiate the following executable operations:
generating an output file including:
source code for the software module, and
the maintenance that was previously applied to the software module.

15. The computer program product of claim 13 , wherein
the base version is identified by processing memory structures contained in the dump file to locate areas in the memory structures that contain information about the software module that was loaded when the crash occurred.

16. The computer program product of claim 15 , wherein
the processing the memory structures includes identifying entries in a loader domain and a program manager domain.

17. The computer program product of claim 13 , wherein
the maintenance indicates updates that have been applied to the base version.

18. The computer program product of claim 13 , wherein the program code further causes the computer hardware system to perform:
identifying a plurality of software modules that were loaded when the crash occurred; and
identifying, for the plurality of software modules, additional maintenance updates that were not applied to the plurality of software modules.

Assignees

• IBM

Inventors

• Smith Samuel J
• Woolley Mark A
• Wright Andrew

Classifications

• G06F11/079

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title

• G06F11/366

  using diagnostics (G06F11/0703 takes precedence) · CPC title

• G06F11/0706

  the processing taking place on a specific hardware platform or in a specific software environment · CPC title

• G06F11/362 Primary

  Debugging of software · CPC title

• G06F11/0793

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title