RUNTIME EXCEPTION AND BUG IDENTIFICATION WITHIN AN INTEGRATED DEVELOPMENT ENVIRONMENT

• US 20170109256A1
• Filed: 10/15/2015
• Published: 04/20/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.
• Granted Patent: US 9,785,537 B2
• Time in Patent Office: Days
• 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-7. -7. (canceled)

8. A system comprising:

a memory; and

one or more computer processors, communicatively coupled to the memory, the one or more computer processors configured to;

select 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 of monitoring of the one or more program components;

monitor one or more data sources resulting from execution of the one or more program components;

encounter one or more events in the one or more data sources during the execution of the one or more program components;

generate one or more messages, each message describing a respective event encountered, responsive to encountering the one or more events in the one or more data sources; and

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

parsing 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 at least one of a timestamp, a severity level, a full stack trace, a category of the event, and a summary of the event; and

displaying the at least one of the timestamp, the severity level, the full stack trace, the category of the event, and the summary 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.

9. The system of claim 8, wherein the one or more messages notified of within the IDE are based on messages generated over a history of a plurality of executions of the one or more program components.

10. The system of claim 8, wherein the one or more computer processors are further configured to write the one or more messages to one or more notification files, and wherein the one or more notification files are accessible by the IDE.

11. The system of claim 10, wherein the one or more computer processors are further configured to:

clear 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.

12. The system of claim 8, wherein the one or more computer processors are further configured to:

receive a user selection of a first message of the one or more messages notified of within the IDE; and

display the at least one message in the IDE, responsive to the user selection.

13. The system of claim 8, wherein notifying of the one or more messages within the IDE comprises notifying of a first message in association with the full stack trace, and wherein the first message describes an event encountered at the full stack trace.

14. A computer program product for notifying of events encountered in program components, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to perform a 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 of monitoring of the one or more program components;

monitoring one or more data sources resulting from execution of one or more program components;

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

generating one or more messages, each message describing a respective event encountered, responsive to encountering the one or more events in the one or more data sources; and

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 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 at least one of a timestamp, a severity level, a full stack trace, a category of the event, and a summary of the event; and

displaying the at least one of the timestamp, the severity level, the stack trace, the category of the event, and the summary 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.

15. The computer program product of claim 14, wherein the one or more messages notified of within the IDE are based on messages generated over a history of a plurality of executions of the one or more program components.

16. The computer program product of claim 14, wherein the one or more messages are shared across two or more IDEs of two or more computing devices.

17. The computer program product of claim 14, the method further comprising writing the one or more messages to one or more notification files, wherein the one or more notification files are accessible by the IDE.

18. The computer program product of claim 17, the method 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.

19. The computer program product of claim 14, the method further comprising:

receiving a user selection of a first message of the one or more messages notified of within the IDE; and

displaying the at least one message in the IDE, responsive to the user selection.

20. The computer program product of claim 14, wherein notifying of the one or more messages within the IDE comprises notifying of a first message in association with the full stack trace, and wherein the first message describes an event encountered at the full stack trace.