Automatic bug reporting tool

• US 8,694,831 B2
• Filed: 05/29/2009
• Issued: 04/08/2014
• Est. Priority Date: 05/29/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Arapov, Anton, Moskovcak, Jiri, Prikryl, Zdenek
• Primary Examiner(s): Maskulinski, Michael
• Assistant Examiner(s): MILES, NEIL D
• Application Number:
  US12/475,410
• Publication Number:
  US 20100306593A1
• Time in Patent Office: 1,775 Days
• Field of Search: 714/38
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

An apparatus and a method for detecting and reporting malfunctions in computer programs is described. A malfunction detector detects at least one type of a software malfunction as defined in a configurable malfunction library. A data collector collects data of the software malfunction. A crash reporter reports the crash report in a manner specified in a configurable reporting library corresponding to the type of software malfunction to one or more remote computers.

Claims

1. A method comprising:

receiving, by a software malfunction reporting tool executing on a client device separate from applications of the client device, crash data from at least one of a plurality of crash handlers of the client device, each of the plurality of crash handlers corresponding to one of an application or an operating system of the client device;

detecting, by the software malfunction reporting tool, a type of a software malfunction of the crash data, the type of software malfunction defined in a malfunction library of the software malfunction reporting tool, the malfunction library comprising a plurality of addon modules that each are dedicated to a software language of software applications executed on the client device and that each specify how to detect a malfunction in the software applications executed in the software language associated with the addon module;

determining, by the software malfunction reporting tool, a manner for reporting data of the software malfunction as defined in a reporting library of the software malfunction reporting tool, the reporting library comprising a plurality of plugin modules that correspond to types of software malfunctions and each comprise a reporter component defining a manner to report a type of software malfunction corresponding to the plugin module;

generating, by a core component of the software malfunction reporting tool, a crash report describing the data of the software malfunction, wherein the crash report is generated in the manner determined by the reporter component of the plugin module corresponding to the type of software malfunction; and

reporting, by the core component, the crash report in the manner specified by the reporter component of the plugin module corresponding to the type of software malfunction;

wherein the plurality of addon modules and the plurality of plugin modules are loaded as part of the software malfunction reporting tool upon an initialization of the software malfunction reporting tool on the client device, and wherein the core component is a compiled-in feature of the software malfunction reporting tool.

2. The method of claim 1 wherein the plurality of addon modules comprise at least one of a C/C++ application crashes catcher, a Linux™

kernel crashes catcher, a Python™

applications crashes catcher, or a Run Application Action.

3. The method of claim 1 wherein a core function component performs the generating the crash report.

4. The method of claim 3 wherein the core function component comprises at least one of a Graphical User Interface, an Applet, or a Daemon.

5. The method of claim 1 wherein the plugin module further comprises a database component.

6. A non-transitory computer-readable storage medium, having instructions stored therein, which when executed, cause a processing device to perform operations comprising:

receiving, by a software malfunction reporting tool executed by the processing device of a client device separate from applications of the client device, crash data from at least one of a plurality of crash handlers of the client device, each of the plurality of crash handlers corresponding to one of an application or an operating system of the client device;

detecting, by the software malfunction reporting tool, a type of a software malfunction of the crash data, the type of software malfunction defined in a malfunction library of the software malfunction reporting tool, the malfunction library comprising a plurality of addon modules that each are dedicated to a software language of software applications executed on the client device and that each specify how to detect a malfunction in the software applications executed in the software language associated with the addon module;

determining, by the software malfunction reporting tool, a manner for reporting data of the software malfunction as defined in a reporting library of the software malfunction reporting tool, the reporting library comprising a plurality of plugin modules that correspond to types of software malfunctions and each comprise a reporter component defining a manner to report a type of software malfunction corresponding to the plugin module;

generating, by a core component of the software malfunction reporting tool, a crash report describing the data of the software malfunction, wherein the crash report is generated in the manner determined by the reporter component of the plugin module corresponding to the type of software malfunction; and

reporting, by the core component, the crash report in the manner specified by the reporter component of the plugin module corresponding to the type of software malfunction;

wherein the plurality of addon modules and the plurality of plugin modules are loaded as part of the software malfunction reporting tool upon an initialization of the software malfunction reporting tool on the client device, and wherein the core component is a compiled-in feature of the software malfunction reporting tool.

7. The non-transitory computer-readable storage medium of claim 6 wherein the plurality of addon modules comprise at least one of a C/C++ application crashes catcher, a Linux™

kernel crashes catcher, a Python™

applications crashes catcher, or a Run Application Action.

8. The non-transitory computer-readable storage medium of claim 6 wherein a core function component performs the generating the crash report.

9. The non-transitory computer-readable storage medium of claim 8 wherein the core function component comprises at least one of a Graphical User Interface, an Applet, or a Daemon.

10. The non-transitory computer-readable storage medium of claim 6 wherein the plugin module further comprises a database component.

11. A computer system comprising:

a memory;

a processing device coupled to the memory;

a configurable malfunction reporting application programming interface (API) executable from the memory by the processing device, the configurable malfunction reporting API comprising;

a malfunction detector executing separate from applications of the computer system, the malfunction detector to;

receive crash data from at least one of a plurality of crash handlers of the client device, each of the plurality of crash handlers corresponding to one of an application or an operating system of the computer system; and

detect a type of software malfunction of the crash data, the type of software malfunction defined in a malfunction library, the malfunction library comprising a plurality of addon modules that each are dedicated to a software language of software applications executed on the client device and that each specify how to detect a malfunction in the software applications executed in the software language associated with the addon module;

a data collector coupled to the malfunction detector, the data collector comprising;

a plurality of plugin modules that correspond to types of software malfunctions and each comprise a reporter component defining a manner to report an associated type of software malfunction corresponding to the plugin module, wherein a plugin module of the plurality of plugin modules corresponding to the detected type of the software malfunction determines a manner for reporting data of the software malfunction according to the reporter component of the plugin module; and

a core component to generate a crash report describing the data of the software malfunction, wherein the crash report is generated in the manner determined by the reporter component of the plugin module corresponding to the type of software malfunction; and

a crash reporter coupled to the data collector, the crash reporter to report the crash report in the manner specified by the reporter component of the plugin module corresponding to the type of software malfunction;

wherein the plurality of addon modules and the plurality of plugin modules are loaded as part of the configurable malfunction reporting API upon an initialization of the configurable malfunction reporting API on the computer system, and wherein the core component is a compiled-in feature of the configurable malfunction reporting API.

12. The computer system of claim 11 wherein the plurality of addon modules comprise at least one of a C/C++ application crashes catcher, a Linux™

kernel crashes catcher, a Python™

applications crashes catcher, or a Run Application Action.

13. The computer system of claim 11 wherein the crash reporter comprises the core component.

14. The computer system of claim 13 wherein the core function component comprises at least one of a Graphical User Interface, an Applet, or a Daemon.

15. The computer system of claim 11 wherein the plugin module further comprising a database component.