Runtime exception and bug identification within an integrated development environment

• US 9,804,950 B2
• Filed: 11/30/2015
• Issued: 10/31/2017
• Est. Priority Date: 10/15/2015
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bhogal, Kulvir S., DeLuca, Lisa Seacat, Peterson, Robert R.
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): MORSHED, HOSSAIN M
• Application Number:
  US14/953,460
• Publication Number:
  US 20170109261A1
• Time in Patent Office: 701 Days
• Field of Search: 171124, 171125, 171127, 171128
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

In one embodiment, a computer-implemented method includes monitoring one or more data sources resulting from execution of one or more program components. One or more events are encountered in the one or more data sources during the execution of the one or more program components. One or more messages are generated, with each message describing an event encountered. Each of the one or more messages is parsed for a name of a corresponding source file in which an associated event was encountered, a corresponding line number at which the event was encountered, and at least one of: a timestamp, severity level, full stack trace, category of the event, and summary of the event. The one or more messages are notified of within an integrated development environment (IDE). Each of the one or more messages is associated in the IDE with the corresponding source file at the corresponding line number.

Claims

1. A computer-implemented method, comprising:

selecting one or more program components to be monitored from among a plurality of program components, wherein the selecting is based on activation by a user;

associating a respective counter with each program component of the one or more program components selected to be monitored;

monitoring one or more data sources responsive to a first execution of the one or more program components;

encountering one or more events in the one or more data sources resulting from the first execution of the one or more program components during the first execution of the one or more program components;

generating one or more messages in one or more notification files, each message describing a respective event encountered during the first execution and related to a program component of the one or more program components, responsive to encountering the one or more events in the one or more data sources; and

incrementing the respective counter associated with each program component of the one or more program components, for each message generated describing a respective event encountered related to the program component;

notifying of the one or more messages within an integrated development environment (IDE), each of the one or more messages associated in the IDE with the corresponding source file at the corresponding line number, wherein the notifying of the one or more messages within the IDE comprises;

parsing, by a computer processor, each of the one or more messages for a name of the corresponding source file in which the associated event was encountered, a corresponding line number at which the associated event was encountered, and a full stack trace of the event;

displaying a respective event notification in the IDE associated with each program component, of the one or more program components, having a respective counter with a value greater than zero, wherein the respective event notification associated with a program component is sized based on the value of the respective counter of the program component and

displaying the full stack trace of the event within the IDE in association with the corresponding line number of the corresponding source file;

wherein the one or more messages notified of within the IDE are related to the one or more program components selected from the plurality of program components.

2. The method of claim 1, further comprising:

monitoring the one or more data sources responsive to a second execution of the one or more program components;

encountering one or more additional events in the one or more data sources resulting from the second execution of the one or more program components during the second execution of the one or more program components;

generating one or more additional messages in the one or more notification files, wherein the one or more additional messages are added to the one or more messages in the one or more notification files, each additional message describing a respective additional event encountered during the second execution and related to a program component of the one or more program components, responsive to encountering the one or more additional events in the one or more data sources; and

notifying of the one or more messages from the first execution along with the one or more additional messages from the second execution within the IDE, wherein notifications within the IDE are based on a history of a plurality of executions of the one or more program components.

3. The method of claim 1, wherein the one or more messages are shared across two or more IDEs of two or more computing devices.

4. The method of claim 1, further comprising:

clearing the one or more notification files responsive to a set of criteria being met;

wherein the one or more messages are cleared from the IDE, responsive to clearing the one or more notification files.

5. The method of claim 1, further comprising:

receiving a user selection of a first event notification displayed in the IDE associated with a first program component of the one or more program components;

displaying in the IDE a first message associated with the first program component, responsive to the user selection of the first event notification;

receiving a user selection of the first message associated with the first program component; and

opening first source code for the first program component and highlight a line at which an event associated with the first message occurs in the first source code, responsive to the user selection of the first message.