Analyzing a dump file from a data storage device together with debug history to diagnose/resolve programming errors

• US 8,949,672 B1
• Filed: 04/18/2011
• Issued: 02/03/2015
• Est. Priority Date: 04/18/2011
• Status: Active Grant

• Current Assignee: Western Digital Technologies Incorporated (Western Digital Corporation)
• Original Assignee: Western Digital Technologies Incorporated (Western Digital Corporation)
• Inventors: Srihamat, Apisak, Phan, Kuan Chin
• Primary Examiner(s): Riad, Amine
• Application Number:
  US13/089,083
• Time in Patent Office: 1,387 Days
• Field of Search: 714/38.1
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

A method is disclosed for diagnosing programming errors for a data storage device, wherein a dump file is received from the data storage device comprising program execution data. The dump file is converted into a plurality of debug stop records, wherein each debug stop record comprises trace information related to a programming error. A first debug stop record is evaluated relative to a history of debug stop records stored in a history database. When the first debug stop record corresponds to a second debug stop record in the history database, the programming error is resolved for the first debug stop record using resolution information associated with the second debug stop record.

Claims

1. A method of diagnosing programming errors for a data storage device, the method comprising:

receiving a dump file from the data storage device, wherein the dump file comprises program execution data;

converting the dump file into a plurality of debug stop records, wherein each debug stop record comprises trace information related to a programming error;

evaluating a first debug stop record relative to a history of debug stop records stored in a history database;

when the first debug stop record corresponds to a second debug stop record in the history database, providing second resolution information associated with the second debug stop for resolution of the programming error for the first debug stop record; and

when the first debug stop record does not correspond to any debug stop records in the history database;

obtaining first resolution information relating to resolution of the programming error for the first debug stop record;

associating the first resolution information with the first debug stop record; and

storing the first debug stop record in the history database,

wherein the first and second resolution information is generated and entered into the history database by a user and comprises a description of the respective resolution.

2. The method as recited in claim 1, wherein the first debug stop record comprises an identifier, further comprising searching the history database using the identifier.

3. The method as recited in claim 2, further comprising displaying a plurality of debug stop records in the history database corresponding to the identifier.

4. The method as recited in claim 3, wherein when a user selects one of the plurality of debug stop records, further comprising displaying resolution information for the selected debug stop record.

5. The method as recited in claim 1, wherein the second resolution information comprises a data file attached to the second debug stop record.

6. The method as recited in claim 1, when the first debug stop record corresponds to a second debug stop record in the history database, further comprising:

associating the second resolution information with the first debug stop record; and

storing the first debug stop record in the history database.

7. The method as recited in claim 1, wherein the data storage device comprises a head actuated over a disk.

8. The method as recited in claim 1, wherein the data storage device comprises a non-volatile semiconductor memory.

9. Non-transitory computer readable medium comprising a computer program, the computer program comprising code segments for diagnosing programming errors for a data storage device, wherein the code segments, when executed by a processor, cause the processor to perform a method comprising:

receiving a dump file from the data storage device, wherein the dump file comprises program execution data;

converting the dump file into a plurality of debug stop records, wherein each debug stop record comprises trace information related to a programming error;

evaluating a first debug stop record relative to a history of debug stop records stored in a history database;

when the first debug stop record corresponds to a second debug stop record in the history database, providing second resolution information associated with the second debug stop for resolution of the programming error for the first debug stop record; and

when the first debug stop record does not correspond to any debug stop records in the history database;

obtaining first resolution information relating to resolution of the programming error for the first debug stop record;

associating the first resolution information with the first debug stop record; and

storing the first debug stop record in the history database,

wherein the first and second resolution information is generated and entered into the history database by a user and comprises a description of the respective resolution.

10. The non-transitory computer readable medium as recited in claim 9, wherein the first debug stop record comprises an identifier, further comprising code segments that, when executed by the processor, cause the processor to perform searching the history database using the identifier.

11. The non-transitory computer readable medium as recited in claim 10, further comprising code segments that, when executed by the processor, cause the processor to perform identifying a plurality of debug stop records in the history database corresponding to the identifier.

12. The non-transitory computer readable medium as recited in claim 11, wherein when a user selects one of the plurality of debug stop records, further comprising code segments that, when executed by the processor, cause the processor to perform identifying resolution information for the selected debug stop record.

13. The non-transitory computer readable medium as recited in claim 9, wherein the second resolution information comprises a data file attached to the second debug stop record.

14. The non-transitory computer readable medium as recited in claim 9, when the first debug stop record corresponds to a second debug stop record in the history database, further comprising code segments that, when executed by the processor, cause the processor to perform:

associating the second resolution information with the first debug stop record; and

storing the first debug stop record in the history database.

15. The non-transitory computer readable medium as recited in claim 9, wherein the data storage device comprises a head actuated over a disk.

16. The non-transitory computer readable medium as recited in claim 9, wherein the data storage device comprises a non-volatile semiconductor memory.

17. A computer system comprising a computer program and a processor for executing the computer program, the computer program comprising code segments for diagnosing programming errors for a data storage device, the computer system executing the computer program with the processor to perform operations comprising:

receiving a dump file from the data storage device, wherein the dump file comprises program execution data;

converting the dump file into a plurality of debug stop records, wherein each debug stop record comprises trace information related to a programming error;

evaluating a first debug stop record relative to a history of debug stop records stored in a history database;

when the first debug stop record corresponds to a second debug stop record in the history database, providing second resolution information associated with the second debug stop for resolution of the programming error for the first debug stop record; and

when the first debug stop record does not correspond to any debug stop records in the history database;

obtaining first resolution information relating to resolution of the programming error for the first debug stop record;

associating the first resolution information with the first debug stop record; and

storing the first debug stop record in the history database,

wherein the first and second resolution information is generated and entered into the history database by a user and comprises a description of the respective resolution.

18. The computer system as recited in claim 17, wherein the first debug stop record comprises an identifier, the computer program further comprising code segments for searching the history database using the identifier.

19. The computer system as recited in claim 18, wherein the computer program further comprising code segments for identifying a plurality of debug stop records in the history database corresponding to the identifier.

20. The computer system as recited in claim 19, wherein when a user selects one of the plurality of debug stop records, the computer program further comprising code segments for identifying resolution information for the selected debug stop record.

21. The computer system as recited in claim 17, wherein the second resolution information comprises a data file attached to the second debug stop record.

22. The computer system as recited in claim 17, when the first debug stop record corresponds to a second debug stop record in the history database, the computer program further comprising code segments for:

associating the second resolution information with the first debug stop record; and

storing the first debug stop record in the history database.