|Publication number||US6671876 B1|
|Application number||US 09/429,510|
|Publication date||Dec 30, 2003|
|Filing date||Oct 28, 1999|
|Priority date||Oct 28, 1999|
|Publication number||09429510, 429510, US 6671876 B1, US 6671876B1, US-B1-6671876, US6671876 B1, US6671876B1|
|Inventors||Robert R. Podowski|
|Original Assignee||Lucent Technologies Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (13), Non-Patent Citations (3), Referenced by (46), Classifications (15), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates generally to the operation of computer programs and is particularly directed to the monitoring of the access, or use, of blocks of code during the operation of a computer program and the display in real time of this information.
There are various aids for computer programmers in the design of a computer program. One programming aid makes use of log files which are reports on system performance, system status, and software faults. This approach provides for the graphic analysis of log files to analyze the occurrence of the log file and to possibly determine the cause of the report. An example of this after-the-fact analysis of computer program operation can be found in U.S. Pat. No. 5,847,972. Another programming aid is described in an article entitled “Visualizing Performance Debugging,” by Ted Lehr et al. This approach makes use of the Parallel Programming and Instrumentation Environment (PIE) to develop performance-efficient parallel and sequential computations in a multi-processor system. The PIE system affords a visualization approach in computer program performance debugging. Finally, an article entitled “ParaGraph: A Graphical Tuning Tool for Multiprocessor Systems,” published in the Fujitsu Scientific & Technical Journal, Vol. 29 (1993) Summer, No. 2, by Awikawa et al., describes a system that gathers periodical statistics of the computational and communication load of each processor in a multiprocessor arrangement during program execution. This data is collected in both the higher level of programming language and lower level of implementation, and is presented in a graphic form on a video display to allow a user to determine the best processor load distribution algorithm.
One problem of increasing importance in computer programming not addressed in the aforementioned programming aids is the size of the software product required to operate a system. As system complexities increase, the length and complexity of the program increases. Subsequent improvements to the program involve the writing of additional code. The tendency today is to write too much code without regard for the size of the software program. This tendency has been encouraged by the conventional wisdom that memory is cheap and programmers are expensive. This has led to large, unwieldy, software packages which run inefficiency and are cumbersome to modify or update. In addition, the operation of the device being controlled is also frequently limited by this approach. For example, the modified and expanded computer program becomes more cumbersome and slower to execute, typically resulting in an increased response time of the hardware carrying out the software-controlled operation. As the limits of computer storage capacity are approached, the computer components must be replaced with newer hardware.
The present invention addresses these problems encountered in the prior art by monitoring the running of selected blocks of software code and presenting this information in real time on a video display to allow for the determination of how frequently selected blocks of code are being accessed and conversely which blocks of code are not being accessed and can be deleted from the program.
This invention contemplates the monitoring of blocks of software code in a computer program to determine (1) how often a block of code is being run, (2) if a block of code is no longer being run, and (3) if new blocks are being run. This permits unused codes to be identified and deleted from the program thus allowing the program to run more efficiently and saving memory for other applications. This information is presented on a video display in two selectable formats in real time. In a first mode of operation, the times at which a selected block of code is accessed within a given time period is displayed along a horizontal axis and the number of times of access at each time it occurs is represented along a vertical axis in bar graph form. In a second mode of operation, the various monitored blocks of code are displayed along a horizontal axis in a spaced manner and the number of times each of the individual blocks is accessed as the computer program runs is presented in bar graph form vertically.
The invention is implemented in a manner similar to that of an oscilloscope with its voltage/current probes attached at various locations in the circuit under analysis. The present invention employs special lines of code added to each software module being observed which function as probes. There is a one-to-one relationship between the software probes and the blocks of code. Every time a given block of code is run, a counter is incremented. The contents of the various counters each corresponding to a block of code are processed and presented on the video display. The contents of the counters are reset as determined by the sweep parameters and the stop and start selectors. Parameter settings such as horizontal sweep, event triggering, and vertical scale are examined first, and are then combined with the data recorded for determining how the data is to be displayed. The display is operated in a manner typical of a Microsoft Windows® application.
The appended claims set forth those novel features which characterize the invention. However, the invention itself, as well as further objects and advantages thereof, will best be understood by reference to the following detailed description of a preferred embodiment taken in conjunction with the accompanying drawings, where like reference characters identify like elements throughout the various figures, in which:
FIG. 1 is a simplified combined schematic and block diagram of a software monitoring system in accordance with the principles of the present invention;
FIG. 2 is a combined block and schematic diagram of control circuitry implemented by software in the monitoring of software operation in a computer program in a first display mode of operation of the present invention;
FIG. 3 illustrates a typical presentation of information on a video display as provided by the present invention when operated in the first display mode of operation;
FIG. 4 is a combined block and schematic diagram of control circuitry implemented by software in the monitoring of software operation in a computer program in a second display mode of operation of the present invention;
FIG. 5 shows a typical presentation of information on a video display as provided by the present invention when operated in the second display mode of operation;
FIGS. 6a, 6 b and 6 c are simplified flow charts showing the difference between prior art computer programs and a computer program for monitoring software operation in accordance with the present invention; and
FIGS. 7-12 show various presentations provided on a video display which permit a user to enter various selected inputs in monitoring and displaying the software operation of a computer program in accordance with the present invention.
The present invention operates in a manner somewhat similar to the operation of an oscilloscope in the analysis of the operation of hardware. The purpose of the present invention is to provide a means of observing, in real time, the running of selected blocks of software code in a computer program. More specifically, the action of entering a selected block of code is recorded on a counter associated with that block. Data on selected blocks of code is collected over time, processed, and then presented on a video display similar to the electrical data displayed on a hardware oscilloscope.
Referring to FIG. 1, there is shown a simplified combined block and schematic diagram of a software monitoring system 10 in accordance with the present invention. The software monitoring system 1 0 includes a computer terminal 12 with a keyboard 14 and a mouse control 16. The computer terminal 12 is connected to a processor 18 which runs a target program 22. It is the target program 22 which the present invention monitors and analyzes in real time, with the results of this analysis presented on the video display of the computer terminal 12. In accordance with the present invention, processor 18 also runs a probe program 20 which operates in conjunction with the target program 22 as described in detail below. While the processor 18 is shown coupled to the probe program 20 and target program 22, in actual practice the probe program and the target program are stored within the processor and operate under the control of the processor.
Target program 22 is shown as including various blocks of code such as first, second and third code blocks 24, 26 and 28 as well as a Kth code block 30. While only four blocks of code are shown in the target program 22 in FIG. 1, the present invention is capable of analyzing virtually any number of blocks of code, thus the designation of the Kth code block as element 30. Each block of code carries out a specific task or a series of tasks and together the blocks of code form the operating program which is being analyzed. The probe program 20 includes first, second and third probe registers 40, 42 and 44, as well as a Kth probe register 46. Software probes connect each probe register in the probe program 20 to an associated block of software code in the target program 22. Thus, first, second and third software probes 32, 34 and 36 respectively couple the first probe register 40 to the first code block 24, the second probe register 42 to the second code block 26, and the third probe register 44 to the third code block 28. Similarly, a Kth software probe connects the Kth probe register 46 to the Kth code block 30.
Referring to FIGS. 6a, 6 b and 6 c, there is shown a comparison of prior art approaches with the present invention. Each of FIGS. 6a, 6 b and 6 c is a simplified flow chart indicating the start and operation of a computer program. Thus, as shown in FIG. 6a, prior art approaches initiated the start of the operation of a computer program at step 100, followed by the carrying out of the steps of the computer program at step 102. In accordance with the present invention, as shown in FIG. 6b, the computer program is started at step 104, followed by loading of the contents of a probe register in the probe program 20 in the block of code associated with that register at step 106. Thus, for the case of a register designated as K, the contents of this register is loaded at step 106 into its associated block of code in the target program 22. Each time the block of code K is accessed by the computer program, a counter is incremented at step 108. The new count is then provided from the block of code K in the target program 22 to the associated probe register in the probe program at step 110. The program then continues to operate in either accessing or not accessing the block of code containing the K software probe at step 112. FIG. 6c is similar to FIG. 6b except that in FIG. 6c the contents of register XY12 is loaded from a probe register in the probe program 20 into an associated block of code in the target program 22. Thus, operation of the computer program is initiated at step 114, followed by loading of the contents of the XY12 register into an associated block of code in the target program 22 at step 116. Each time the block of code containing the XY12 software probe is accessed, a counter is incremented by 1 at step 112 and the new count is provided to the XY12 register in the probe program 20 at step 120. The program continues to operate at step 122, continuously monitoring for access of the block of code containing the XY12 software probe. In summary, each block of code in the target program 22 has an associated probe register in the probe program 20 which are connected by means of a respective software probe. Every time a block of code is run in the target program 22, its corresponding register in the probe program 20 is incremented by 1. This is the only operational connection of the probe program 20 with the target program 22. Thus, the impact of the probe program 20 on the target program 22 is minimized because all manipulation of probe data is performed at the probe register in the probe program and is not performed in the target program 22.
Referring to FIG. 2, there is shown a combined block and schematic diagram of a software probe sample circuit 50 for use in a first, regular mode of operation. FIG. 2 represents the series of steps involved in recording and displaying data in accordance with this aspect of the present invention. While shown in terms of logic components in the figure, this series of steps is actually performed by the operating program stored in the processor 18 of FIG. 1. In addition, while the following description is in terms of the first software probe, it is equally as well applicable to any of the software probes. FIG. 3 illustrates a typical presentation of information on a video display 76 as provided by the present invention when operated in the first, regular display mode of operation. In the figures, the same element shown in the various figures is assigned the same reference character throughout the figures.
A software probe is loaded into the first probe register 40. The probe register 40 is incremented each time its associated block of code in the target program is accessed, or run. FIG. 2 shows how this data is cleared and collection restarted as well as how these operations are synchronized with the display of data. A timing source such as a sample clock 56 provides timing for the software monitoring system. If, for example, the sample clock 56 is running at a rate of one pulse every one microsecond as shown by the pulse diagram output from the sample clock, the value of the probe register 40 is loaded into a display stack 64 every microsecond. The value of the probe register 40 is gated by AND gate 52 which also receives the pulsed, timed output of the sample clock 56. A time delay of t1 is introduced into the clock signal provided by the sample clock 56 to the first probe register 40 by means of a delay circuit 54. This time delayed input to the first probe register 40 provides for resetting of the probe register. A display stack pointer for the display stack 64 is incremented every clock pulse output by the sample clock 56. As a result, the display stack 64 contains values taken by the first probe register 40 in an ordered array with respect to time. For example, the first sample is PV1, but while the last sample is PVN. The pulsed output of the sample clock 56 is also provided to a second AND gate 60 as well as to a ÷N circuit 58. The divided down output of the ÷N circuit 58 is provided to the other input of AND gate 60 and the pulsed output of the AND gate is provided to a display trigger as well as to a second t2 delay circuit 62. In the present example, N is equal to 500. The output of the second t2 delay circuit 62 is provided to the display stack 64 for clearing the contents of the display stack to 0 after the second time delay. As samples from the first register probe 40 are read into the display stack 64 after a time delay of t1, the probe register is reset to zero by the output of the time delay circuit 54. After N periods of the system clock, the display stack 64 contains a history of the number of times the first block of code has been run, or accessed, within the last, in the present example, 0.5 milliseconds. The display trigger pulses output by the second AND gate 60 are provided to a video display for synchronizing these operations with the display of data.
FIG. 3 shows the presentation of the regular display mode of operation in the present invention. In the example shown, the software probe is connected to a block of code designated as CD3. The display mode of operation selected is single sweep. The display 76 shows six occurrences of the CD3 block of code being run within a period of 50 milliseconds. The display sweep time is started the first time the CD3 block of code is accessed. This mode of operation is particularly adapted for viewing the number of times a particular block of code is run relative to a selected time base. If the CD3 block of code is accessed more than once within a given 5 millisecond period, this would be shown by an increased length in the vertical direction of the bar graph element for that particular time period within the 50 millisecond scan period.
Referring to FIG. 4, there is shown a combined block and schematic diagram of a software probe sample circuit 66 for use in a second, storage display mode of operation in accordance with another aspect of the present invention. Again, FIG. 4 shows the manner in which data is recorded and displayed in terms of hardware logic, although in the preferred embodiment of the present invention these steps are carried out in the operating program stored in the processor of FIG. 1. FIG. 5 shows a typical presentation of information on a video display 78 as provided by the present invention when operated in the second, storage display mode of operation. The software probe sample circuit 66 for the storage mode of operation includes the aforementioned first, second, third and Kth registers 40, 42, 44 and 46 which respectively receive the first, second, third and Kth software probes. In addition to the previously described second AND gate 60, the software probe sample circuit 66 for the storage mode of operation includes third, fourth, fifth and sixth AND gates 68, 70, 72 and 74. In the storage mode of operation, virtually any number of probe registers may be incorporated in the software probe sample circuit 66 and their data stored in the display stack 64. The counts in the display stack 64 are allowed to accumulate for the entire sweep period. Counting N pulses of the sample clock 56 again defines the sweep period. In the example shown in FIGS. 4 and 5, the sweep period is 0.5 milliseconds. A combination of the sample clock 56, a ÷N circuit 58, the second AND gate 60 and the t2 delay circuit 62 operate as previously described with respect to the software probe sample circuit 50 for the regular mode of operation in clearing the display stack 64 and clocking a detected software probe associated with a given probe register into the display stack. In the present example, the K probe register 46 is incremented every time block of code K is run in the target program. The display stack register 64 continues to increment the detected counts for the entire sweep period of 0.5 milliseconds. This is shown symbolically by AND gate 74. Also as shown in the example of FIG. 5, three blocks of code have been run by the target program. The display shows a block of code identified as AA1 as run 19 times within a 50 millisecond period. Another block of code identified as element 80 was run eight times within the same 50 millisecond period. A third block of code identified as element 82 was run four times within the same 50 millisecond sweep time. The mode select switch is in the single sweep mode providing only a single scan of 50 milliseconds. The data collected is stored in a file called SCAN ONE. The trigger source is the AA1 block of code, where the 50 millisecond sweep starts on the first entry into the AA1 block of code. Thus, in the present example, the AA1 block of code was run an additional 18 times within the 50 millisecond period after the initial running of this block of code. The video display stays up until the next time the start button 75 is selected by moving the mouse pointer over the start button and clicking the mouse pointer. The various functions and parameter settings are accessible along the top of the display on the toolbar 84 as in a conventional Microsoft Windows® application. Each item in the toolbar 84 has a pull-down menu as described in detail below. The mouse pointer is positioned over the item and the mouse button is clicked to cause the desired pull-down menu to appear.
In FIGS. 3 and 5, arrow 81 shown on the video display represents the mouse pointer. When the arrow 81 associated with the mouse pointer is placed next to or adjacent a vertical bar, a pop-up window appears. In FIG. 3, the mouse pointer represented by arrow 81 indicates in pop-up window 79 that block of code CD3 has been accessed once. Similarly, the mouse pointer represented by arrow 81 in FIG. 5 indicates in pop-up window 83 that block of code AA1 has been accessed 19 times within the 50 millisecond time period.
FIGS. 7-12 show various presentations provided on a video display which permit a user to enter various selected inputs in monitoring and displaying the software operation of a computer program in accordance with the present invention. The file pull-down menu is shown in the display 86 of FIG. 7. The file pull-down menu allows a user the ability to open a new file, open a previous file, or close the current file. The current file can also be saved with its current file name, or saved under a new file name. Selection of the exit command ends the software monitoring session and exits the software analysis program.
Connecting the software probes to their respective blocks of software code is accomplished by bringing up the PROBE's pull-down menu shown in the display 88 of FIG. 8. In this context, “connection” is taken to mean that data from a probe register is read into its associated block of code. If a software probe is disconnected, data from a probe register is not read into the display stack. The intent of this design is to minimize the impact on the target program of the software probes that have been inserted in the target program. The item names listed in alpha-numeric character form are the names of the software blocks that have special lines of code added to them as previously described in accordance with the present invention. Using display 88, each of the blocks of code to be observed is connected to an associated probe register by means of a software probe by clicking inside a selected check box shown in the display. Alternate clicking of the mouse on a given check box results in connecting and disconnecting the software probe from its associated block of code. In this example, probes AB2, EF and GH1 are asserted. Virtually any number of blocks of code can be selected and assigned an associated software probe using display 88. The list of blocks of code selected is generated by reading the contents from a file of software probes. Software probes can be added to or deleted from the software monitoring operation of the present invention by means of display 90 shown in FIG. 9. The identity of the selected probe is entered in the “name” location and either the ADD, DELETE or CANCEL command is selected by the user.
In both the regular and storage display modes of operation, SINGLE SWEEP is selected on the display for a single pass of data collection. Data collection stops when the sweep time setting times out. For example, if 50 milliseconds is selected, after 50 milliseconds, data collection stops. While the software probes are always collecting data, data from the corresponding registers is not read. In the continuous mode of operation for both the regular and storage display modes, data collection from the corresponding probe registers continues until the STOP selector 77 is clicked by means of the mouse control. The data collected over the 50 millisecond period is then displayed. In the regular display mode of operation, after 50 milliseconds the data, i.e., the software probe counters, is (are) cleared. A new 50 millisecond period of data collection is initiated and this data is then presented on the video display. The display of this updated data continues until the STOP selector 77 is clicked by the mouse pointer. In the storage display mode of operation, data is collected for 50 milliseconds. At the end of this 50 millisecond period, the data i.e., the software probe counters, is (are) not cleared. The display 78 as shown in FIG. 5 in this case presents cumulative data, with the number of times a given block of code was accessed now displayed as a histogram. A bar-like vertical image for a given block of code continues to increase in length along the vertical direction each time the associated block of code is accessed. The storage display mode of operation thus permits viewing the accessing of several different blocks of code and their relative frequency of running. An important feature of this invention is that the software probes connected to the target program are always ON, resulting in the least impact on the operation of the target program.
Operating parameters, including those controlling the video display, can be changed only when the software monitoring system is in the STOP mode. Moving the mouse pointer to a position over the STOP selector 77 causes the software monitoring system to stop operating. In this state, operating parameters such as those that control the display of information on the video display can now be changed. For example, the horizontal sweep rate of the display can be changed by selecting a value from the pull-down list that appears under Horizontal Scale 98 as shown in FIGS. 3 and 5. Moving the mouse pointer to the horizontal scale selector 98 as shown in FIG. 3 and clicking the mouse button causes a horizontal scale list to appear. Moving the mouse pointer to the box next to the 50 millisecond/scan and then clicking the mouse button causes a check mark to appear in that box. In a similar manner, the trigger source may be selected from the pull-down menu shown in the display 92 of FIG. 10. In the present example, the software block designated as AA1 is the selected trigger. This means that the data will be displayed from left to right on the video display, with the AA1 software probe as the leftmost entry. The order is determined by the order that appears in the Probe's window shown in the display 88 of FIG. 8. The sampling period in the present example is 50 milliseconds. In the example previously described and shown in FIG. 5, the AA1 software block was accessed 19 times within the 50 millisecond period. Scroll bars 91 a and 91 b in display 92 of FIG. 10 allow for the designation of additional software probes beyond those listed in the figure. The vertical scale of the video display can be changed by selecting a value from the list in the pull-down list under the vertical scale selector 100 as shown in FIGS. 3 and 5. One of the selections available is designated AUTO. This selection provides an AUTO-scaling feature. After all of the data has been collected, but before it is displayed, a scan of all the data determines the highest value. A vertical scale that will best fit the highest value in the group of recorded data is then automatically selected. For example, if the highest value detected is 19 for the AA1 block of code, then a vertical scale of two events/division on the video display for a total of 20 would automatically be selected. The software modules to be monitored are selected by means of the pull-down menu that appears under Probes as shown in the display 88 of FIG. 8. The software probe names come from the list generated. The cancel selector 102 shown on the display 90 in FIG. 9 is used to stop any further action in that window and return to the probe's pull-down menu shown in the display 88 of FIG. 8.
While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that changes and modifications may be made without departing from the invention in its broader aspects. Therefore, the aim in the appended claims is to cover all such changes and modifications as fall within the true spirit and scope of the invention. The matter set forth in the foregoing description and accompanying drawing is offered by way of illustration only and not as a limitation. The actual scope of the invention is intended to be defined in the following claims when viewed in their proper perspective based on the prior art.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5355487 *||Jul 23, 1993||Oct 11, 1994||International Business Machines Corporation||Non-invasive trace-driven system and method for computer system profiling|
|US5539907 *||Mar 1, 1994||Jul 23, 1996||Digital Equipment Corporation||System for monitoring computer system performance|
|US5732273 *||Jan 3, 1997||Mar 24, 1998||Digital Equipment Corporation||System for monitoring compute system performance|
|US5774724 *||Nov 20, 1995||Jun 30, 1998||International Business Machines Coporation||System and method for acquiring high granularity performance data in a computer system|
|US5847972||Sep 24, 1993||Dec 8, 1998||Eick; Stephen Gregory||Method and apparatus for graphically analzying a log-file|
|US6026236 *||Jun 3, 1997||Feb 15, 2000||International Business Machines Corporation||System and method for enabling software monitoring in a computer system|
|US6026401 *||Oct 14, 1997||Feb 15, 2000||International Business Machines Corporation||Locking tool data objects in a framework environment|
|US6049666 *||Aug 21, 1998||Apr 11, 2000||Rational Software Corp.||Method and apparatus for accurate profiling of computer programs|
|US6161200 *||Mar 2, 1998||Dec 12, 2000||Applied Microsystems, Inc.||Method and apparatus for analyzing software executed in embedded systems|
|US6212491 *||Nov 9, 1998||Apr 3, 2001||International Business Machines Corporation||Automatic adjustment for counting instrumentation|
|US6349394 *||Mar 31, 1999||Feb 19, 2002||International Business Machines Corporation||Performance monitoring in a NUMA computer|
|US6530079 *||Jun 2, 1999||Mar 4, 2003||International Business Machines Corporation||Method for optimizing locks in computer programs|
|US20020157086 *||Nov 8, 2001||Oct 24, 2002||Lewis Brad R.||Methods and systems for developing data flow programs|
|1||"Graphical Analysis of Computer Log Files" by Stephen G. Eick, Michael C. Nelson and Jeffrey D. Schmidt, Dec. 19, 1992.|
|2||"ParaGraph: A Graphical Tuning Tool for Multiprocessor Systems" by Seiichi Aikawa, Mayumi Kamiko, Takashi Chikayama, in Fujitsu Scientific & Technical Journal, 29, 2 (Jun. 1993).|
|3||"Visualizing Performance Debugging" by Ted Kehr et al, in Computer, Oct. 1989, pp. 38 through 51.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7103876 *||Dec 26, 2001||Sep 5, 2006||Bellsouth Intellectual Property Corp.||System and method for analyzing executing computer applications in real-time|
|US7178131 *||Sep 29, 2003||Feb 13, 2007||International Business Machines Corporation||Inspecting the runtime behavior of a program while minimizing perturbation|
|US7251810 *||Apr 26, 2000||Jul 31, 2007||Microsoft Corporation||Minimal instrumentation for lossless call profiling|
|US7392508 *||Jun 7, 2004||Jun 24, 2008||Robert Podowski||Software oscilloscope|
|US7406686||Jun 9, 2003||Jul 29, 2008||Sun Microsystems, Inc.||Systems and methods for software performance tuning|
|US7739689 *||Feb 27, 2004||Jun 15, 2010||Symantec Operating Corporation||Internal monitoring of applications in a distributed management framework|
|US7904894 *||Mar 29, 2006||Mar 8, 2011||Microsoft Corporation||Automatically optimize performance of package execution|
|US8171340 *||Dec 11, 2009||May 1, 2012||Red Hat, Inc.||Software performance counters|
|US8200828||Oct 30, 2009||Jun 12, 2012||Citrix Systems, Inc.||Systems and methods for single stack shadowing|
|US8230096 *||Jan 14, 2005||Jul 24, 2012||Citrix Systems, Inc.||Methods and systems for generating playback instructions for playback of a recorded computer session|
|US8230414 *||Jun 16, 2006||Jul 24, 2012||Infinera Corporation||Software distribution and cache management across client machines on a network|
|US8286192||Dec 4, 2009||Oct 9, 2012||Red Hat, Inc.||Kernel subsystem for handling performance counters and events|
|US8291399 *||Mar 26, 2008||Oct 16, 2012||Avaya Inc.||Off-line program analysis and run-time instrumentation|
|US8296441||Oct 30, 2009||Oct 23, 2012||Citrix Systems, Inc.||Methods and systems for joining a real-time session of presentation layer protocol data|
|US8422851||Jan 11, 2010||Apr 16, 2013||Citrix Systems, Inc.||System and methods for automatic time-warped playback in rendering a recorded computer session|
|US8484623||Sep 29, 2008||Jul 9, 2013||Avaya, Inc.||Efficient program instrumentation|
|US8566796 *||Apr 4, 2008||Oct 22, 2013||Sas Institute Inc.||Systems and methods for interactions with software probes|
|US8615159||Sep 20, 2011||Dec 24, 2013||Citrix Systems, Inc.||Methods and systems for cataloging text in a recorded session|
|US8739145||Mar 26, 2008||May 27, 2014||Avaya Inc.||Super nested block method to minimize coverage testing overhead|
|US8752007||Mar 26, 2008||Jun 10, 2014||Avaya Inc.||Automatic generation of run-time instrumenter|
|US8935316||Oct 30, 2009||Jan 13, 2015||Citrix Systems, Inc.||Methods and systems for in-session playback on a local machine of remotely-stored and real time presentation layer protocol data|
|US8935703||Dec 11, 2009||Jan 13, 2015||Red Hat, Inc.||Performance counter inheritance|
|US8954996||Dec 11, 2009||Feb 10, 2015||Red Hat, Inc.||Profiling the system providing performance statistics in real time|
|US9021446 *||Jun 28, 2006||Apr 28, 2015||Oracle America, Inc.||Uncoverage tool|
|US9665461||Dec 4, 2009||May 30, 2017||Red Hat, Inc.||Obtaining application performance data for different performance events via a unified channel|
|US9727318 *||Feb 18, 2014||Aug 8, 2017||Facebook, Inc.||Techniques to identify and purge unused code|
|US20040128446 *||Dec 27, 2002||Jul 1, 2004||Carole Dulong||Value profiling with low overhead|
|US20040250234 *||Jun 9, 2003||Dec 9, 2004||Sun Microsystems, Inc.||Systems and methods for software performance tuning|
|US20040250235 *||Jun 9, 2003||Dec 9, 2004||Sun Microsystems, Inc.||Methods and apparatus for enhanced statistical performance|
|US20050021655 *||Jun 9, 2003||Jan 27, 2005||Sun Microsystems, Inc.||System for efficiently acquiring and sharing runtime statistics|
|US20050071815 *||Sep 29, 2003||Mar 31, 2005||International Business Machines Corporation||Method and system for inspecting the runtime behavior of a program while minimizing perturbation|
|US20060089984 *||Oct 22, 2004||Apr 27, 2006||International Business Machines Corporation||Process and implementation for autonomous probe enablement|
|US20060161555 *||Jan 14, 2005||Jul 20, 2006||Citrix Systems, Inc.||Methods and systems for generating playback instructions for playback of a recorded computer session|
|US20070234240 *||Mar 29, 2006||Oct 4, 2007||Microsoft Corporation||Automatically optimize performance of package execution|
|US20080022262 *||Jun 28, 2006||Jan 24, 2008||Raj Prakash||Uncoverage tool|
|US20090249285 *||Mar 26, 2008||Oct 1, 2009||Avaya Technology Llc||Automatic Generation of Run-Time Instrumenter|
|US20090249305 *||Mar 26, 2008||Oct 1, 2009||Avaya Technology Llc||Super Nested Block Method to Minimize Coverage Testing Overhead|
|US20090249306 *||Mar 26, 2008||Oct 1, 2009||Avaya Technology Llc||Off-Line Program Analysis and Run-Time Instrumentation|
|US20090249309 *||Sep 29, 2008||Oct 1, 2009||Avaya Inc.||Efficient Program Instrumentation|
|US20090254821 *||Apr 4, 2008||Oct 8, 2009||Sas Institute Inc.||Systems And Methods For Interactions With Software Probes|
|US20110138146 *||Dec 4, 2009||Jun 9, 2011||Ingo Molnar||Kernel subsystem for handling performance counters and events|
|US20110138389 *||Dec 4, 2009||Jun 9, 2011||Ingo Molnar||Obtaining application performance data for different performance events via a unified channel|
|US20110145651 *||Dec 11, 2009||Jun 16, 2011||Ingo Molnar||Software performance counters|
|US20110145829 *||Dec 11, 2009||Jun 16, 2011||Ingo Molnar||Performance counter inheritance|
|US20110145838 *||Dec 11, 2009||Jun 16, 2011||De Melo Arnaldo Carvalho||Profiling the system providing performance statistics in real time|
|US20150234652 *||Feb 18, 2014||Aug 20, 2015||Facebook, Inc.||Techniques to identify and purge unused code|
|U.S. Classification||717/130, 717/131, 714/E11.2, 717/158, 717/127, 714/E11.192|
|International Classification||G06F9/45, G06F11/34|
|Cooperative Classification||G06F11/3409, G06F2201/88, G06F11/348, G06F2201/865, G06F11/3419|
|European Classification||G06F11/34C, G06F11/34T|
|Oct 28, 1999||AS||Assignment|
Owner name: LUCENT TECHNOLOGIES, INC., NEW JERSEY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PODOWSKI, ROBERT R.;REEL/FRAME:010348/0899
Effective date: 19991025
|Jun 22, 2007||FPAY||Fee payment|
Year of fee payment: 4
|Jun 28, 2011||FPAY||Fee payment|
Year of fee payment: 8
|Aug 7, 2015||REMI||Maintenance fee reminder mailed|
|Dec 30, 2015||LAPS||Lapse for failure to pay maintenance fees|
|Feb 16, 2016||FP||Expired due to failure to pay maintenance fee|
Effective date: 20151230