Abstract: Systems and methods are provided for enabling interaction between a user and a software probe inserted into application code for monitoring and testing application performance. Communications are initialized with the software probe and a user interface is provided to the user. Command data is received from the user through the interface and forwarded to the software probe. In response, data communications are received from the software probe.

Abstract: A system and method for determining execution path differences in a computer-implemented software application is provided herein. A software application under analysis is executed at least twice, thereby generating first and second call tree data and associated first and second sets of execution data describing the at least two executions of the software application. This data is then compared to determine a set of differences between the first and second executions of the program, the set of differences comprising one or more nodes that are either called differently in the first and second execution paths or executed differently in the first and second sets of execution data. For each node identified in the set of differences, the first and second call trees are then analyzed to identify at least one parent node that is the root cause of the difference in the execution data.

Abstract: A system and method of detecting redundant subroutine calls in a software system is provided. Call path data is obtained for the software system and stored into a call tree comprising a plurality of nodes, each node representing a software routine of the software system, the call tree describing the calling paths between the plurality of software routines. At least one focal node is identified among the plurality of nodes in the call tree for redundancy analysis. The calling redundancy to the focal node is analyzed by determining a common ancestor node list for the focal node and by generating call path data for each of the common ancestor nodes on the list. The common ancestor list data may be sorted and call trees generated for the common ancestors in relation to the focal node. This data may then be displayed on a graphical user interface for redundancy analysis of the focal node.

Abstract: Systems and methods are provided for enabling interaction between a user and a software probe inserted into application code for monitoring and testing application performance. Communications are initialized with the software probe and a user interface is provided to the user. Command data is received from the user through the interface and forwarded to the software probe. In response, data communications are received from the software probe.

Abstract: Systems and methods are provided for identifying memory leaks in a computer system. Testing software is inserted into one or more memory routines of a computer system to cause at least two successive tests of the memory routines during which the memory routines perform memory operations to allocate and de-allocate memory from a plurality of memory areas, such as pools or heaps. Information is captured that identifies at least a number of memory allocations and a number of memory de-allocations performed by the memory routines during the pendency of the tests. The captured information is compared to identify one or more candidate memory areas from the plurality of memory areas. A candidate memory areas is identified when the difference between the number of memory allocations and the number of memory de-allocations increases from one test to the next. Each candidate memory area is then evaluated further to identify any specific memory leaks within the memory area.

Abstract: A system and method for determining execution path differences in a computer-implemented software application is provided herein. A software application under analysis is executed at least twice, thereby generating first and second call tree data and associated first and second sets of execution data describing the at least two executions of the software application. This data is then compared to determine a set of differences between the first and second executions of the program, the set of differences comprising one or more nodes that are either called differently in the first and second execution paths or executed differently in the first and second sets of execution data. For each node identified in the set of differences, the first and second call trees are then analyzed to identify at least one parent node that is the root cause of the difference in the execution data.