IP Library › Granted Patent US 10,191,837
Granted Patent B2
US 10,191,837 · App. 15/415,047 · Granted Jan 29, 2019

Automated end-to-end analysis of customer service requests

Inventors: Sowgandh Sunil Gadi (San Jose, CA); Naveen Prakash Rao (Sunnyvale, CA); Travis Finch (Austin, TX); Ayoob Khan (Sunnyvale, CA)
Assignee: VMware, Inc.
G06F11/366G06F11/079G06F11/3664
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,191,837
App. No.
15/415,047
Granted
Jan 29, 2019
Kind
B2
Abstract

An automated end-to-end analysis of customer service requests is disclosed. A core dump is received, wherein the core dump corresponds to a customer service request regarding a crash of a computer system. The core dump is automatically analyzed with a processor to generate analysis results. A graphical representation for display on a graphic user interface of a computer is generate, wherein the graphical representation corresponds to the analysis results for the core dump.

Claims (45)

1. A computer-implemented method for providing an automated end-to-end analysis of customer service requests, said method comprising:

receiving a core dump, wherein said core dump corresponds to said customer service request regarding a crash of a computer system;

automatically analyzing said core dump with a processor to generate analysis results, wherein said automatically analyzing said core dump further comprises:

automatically determining a culprit module responsible for said crash of said computer system; and

automatically generating a signature back trace, wherein said signature back trace pertains to a symptom of said crash of said computer system, and wherein said automatically determining a culprit module responsible for said crash of said computer system further comprises:

generating an essential stack of functions corresponding to said crash of said computer system;

determining a tag sequence and a tag depth corresponding to said essential stack of functions;

deriving a list of permissible tag permutations corresponding to said computer system; and

utilizing said tag sequence and said tag depth in combination with said list of permissible tag permutations to identify a culprit module responsible for said computer crash; and

generating a graphical representation for display on a graphic user interface of a computer, wherein said graphical representation corresponds to said analysis results for said core dump.

2. The computer-implemented method of claim 1 , wherein said receiving said core dump further comprises:

automatically receiving said core dump.

3. The computer-implemented method of claim 1 , further comprising:

generating a core summary from said core dump.

4. The computer-implemented method of claim 1 , wherein said automatically generating a signature back trace comprises:

generating a signature back trace from said essential stack of functions including at least one function corresponding to said culprit module, wherein said signature back trace pertains to a symptom of said crash of said computer system.

5. In an automated end-to-end system for analysis of customer service requests, a method for analyzing a core dump corresponding to a crash of a computer system, said method comprising:

receiving said core dump, wherein said core dump corresponds to said crash of said computer system;

automatically analyzing said core dump to generate analysis results for said core dump wherein said automatically analyzing said core dump further comprises:

automatically determining a culprit module responsible for said crash of said computer system, and wherein said automatically determining said culprit module responsible for said crash of said computer system comprises:

generating an essential stack of functions corresponding to said crash of said computer system;

determining a tag sequence and a tag depth corresponding to said essential stack of functions;

deriving a list of permissible tag permutations corresponding to said computer system; and

utilizing said tag sequence and said tag depth in combination with said list of permissible tag permutations to identify said culprit module responsible for said computer crash; and

automatically generating a signature back trace, wherein said signature back trace pertains to a symptom of said crash of said computer system; and

generating a graphical representation of said analysis results for said core dump.

6. The method of claim 5 , wherein said receiving said core dump further comprises:

automatically receiving said core dump.

7. The method of claim 5 further comprising:

generating a core summary from said core dump.

8. The method of claim 5 , wherein said automatically generating a signature back trace comprises:

generating said signature back trace from said essential stack of functions including at least one function corresponding to said culprit module, wherein said signature back trace pertains to a symptom of said crash of said computer system.

9. The method as recited in claim 5 , wherein said generating said essential stack of functions corresponding to said crash of said computer system comprises:

generating a list of functions and corresponding tags pertaining to a culprit thread determined to be responsible for said crash of said computer system; and

redacting said list of functions to generate said essential stack of functions, wherein said essential stack of functions contains functions pertaining to said symptom of said crash of said computer system.

10. The method as recited in claim 5 , wherein said deriving said list of permissible tag permutations corresponding to said computer system comprises:

analyzing said computer system to determine said permissible tag permutations associated with said computer system.

11. The method as recited in claim 8 , wherein said generating said signature back trace from said essential stack of functions including said at least one function corresponding to said culprit module comprises:

compiling a list of functions selected from said essential stack to comprise said signature back trace, said list of functions including said at least one function corresponding to said culprit module, and at least one function not corresponding to said culprit module.

12. The method as recited in claim 8 , wherein said generating said signature back trace from said essential stack of functions including said at least one function corresponding to said culprit module comprises:

including an offset of said at least one function corresponding to said culprit module in said signature back trace.

13. The method as recited in claim 8 , wherein said generating said signature back trace from said essential stack of functions including said at least one function corresponding to said culprit module comprises:

including a size of said at least one function corresponding to said culprit module in said signature back trace.

14. The method as recited in claim 5 , further comprising:

outputting said graphical representation of said analysis results for said core dump to a repository.

Assignments (2)
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 25, 2017
From: GADI, SOWGANDH SUNIL; RAO, NAVEEN PRAKASH; FINCH, TRAVIS; KHAN, AYOOB
To: VMWARE, INC.
Reel/Frame 041081/0323 →
Continuity (2)
Provisional Application 62353721 · Jun 23, 2016
Related Publication 20170371765A1 · Dec 28, 2017