IP Library Granted Patent US 9,767,007
Granted Patent B2
US 9,767,007 · App. 15/299,078 · Granted Sep 19, 2017

Efficient method data recording

Inventors: Eyal Koren (Dafna, IL); Asaf Dafner (Gedera, IL); Shiri Semo Judelman (Kfar-Saba, IL)
Assignee: Identify Software Ltd. (IL)
G06F11/3636G06F8/70G06F9/4425G06F11/302G06F11/3466G06F11/3495G06F11/3688
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,767,007
App. No.
15/299,078
Granted
Sep 19, 2017
Kind
B2
Abstract

According to one general aspect, a method may include monitoring the execution of at least a portion of a software application. The method may also include collecting subroutine call information regarding a plurality of subroutine calls included by the portion of the software application, wherein one or more of the subroutine calls is selected for detailed data recording. The method may further include pruning, as the software application is being executed, a subroutine call tree to include only the subroutine calls selected for detailed data recording and one or more parent subroutine calls of each subroutine calls selected for detailed data recording.

Claims (86)

1. A method executed by a processor, the method comprising:

monitoring the execution of a software application;

collecting subroutine call information regarding a plurality of subroutine calls included in the software application;

selecting one or more of the plurality of subroutine calls for data recording;

maintaining an array of one or more subroutine call elements, each subroutine call element being associated with a respective subroutine call, the maintaining including:

adding a first subroutine call entry element to the array when a first subroutine is called;

retaining, when the first subroutine exits, the first subroutine call entry element in the array based on determining that the first subroutine is associated with a parent subroutine included in the one or more of the plurality of subroutine calls selected for data recording;

selecting at least one subroutine call element from the array of one or more subroutine call elements; and

removing the at least one selected subroutine call element from the array of one or more subroutine call elements; and

generating a subroutine call tree based on the array of one or more subroutine call elements, the subroutine call tree including the first subroutine call associated with the first subroutine call entry element and omitting the subroutine call associated with the at least one selected subroutine call element.

2. The method of claim 1 , wherein maintaining the array of one or more subroutine call elements further includes:

adding a single shared subroutine call entry element to the array;

adding a second subroutine call entry element to the array when a second subroutine is called, the second subroutine call entry element including a first pointer to the single shared subroutine call entry element;

adding a third subroutine call entry element to the array when a third subroutine is called, the third subroutine call entry element including a second pointer to the single shared subroutine call entry element; and

removing, when the third subroutine exits, the third subroutine call entry element from the array based on determining that the third subroutine is not selected for data recording.

3. The method of claim 1 ,

wherein monitoring the execution of the software application includes injecting code into the plurality of subroutine calls selected for data recording; and

wherein collecting subroutine call information regarding the plurality of subroutine calls included in the software application is performed by the injected code included in the plurality of subroutine calls selected for data recording.

4. The method of claim 1 , wherein collecting subroutine call information regarding the plurality of subroutine calls included in the software application includes, only for each subroutine call selected for data recording, collecting all input arguments passed to the subroutine call and a return value, if any, from the call of a respective subroutine.

5. The method of claim 1 , wherein maintaining the array of one or more subroutine call elements further includes:

adding a second subroutine call entry element to the array when a second subroutine is called; and

based on determining that the second subroutine is selected for detailed data recording, and when the second subroutine exits,

retaining the second subroutine call entry element in the array, and

adding a second subroutine call exit element to the array.

6. The method of claim 5 , wherein the second subroutine call exit element includes subroutine call information regarding the second subroutine call.

7. The method of claim 1 , wherein collecting subroutine call information includes:

for each subroutine call, placing on a memory stack an entry time associated with the subroutine call, and a pointer to a subroutine call entry element included in the array and associated with the subroutine call.

8. An apparatus comprising:

a monitoring engine configured to:

monitor execution of a software application;

a processor configured to:

execute the software application,

select one or more of a plurality of subroutine calls for data recording, and

generate a subroutine call tree based on an array of subroutine call elements;

a pruning engine configured to:

manage collecting of subroutine call information regarding the plurality of subroutine calls included in the software application, and

maintain the array of subroutine call elements, each subroutine call element being associated with a respective subroutine call, the maintaining including:

adding a first subroutine call entry element to the array when a first subroutine is called;

retaining, when the first subroutine exits, the first subroutine call entry element in the array based on determining that the first subroutine is associated with a parent subroutine included in the one or more of the plurality of subroutine calls selected for data recording; and

selecting at least one subroutine call element from the array of subroutine call elements; and

removing the at least one selected subroutine call element from the array of subroutine call elements, wherein the subroutine call tree generated by the processor includes the first subroutine call associated with the first subroutine call entry element and omits the subroutine call associated with the removed at least one subroutine call element; and

a memory configured to store the subroutine call information.

9. The apparatus of claim 8 , wherein the monitoring engine is further configured to:

inject code into the plurality of subroutine calls selected for data recording.

10. The apparatus of claim 8 ,

wherein the memory includes a memory stack; and

wherein the processor is further configured to:

for each subroutine call, place on the memory stack an entry time associated with the subroutine call, and a pointer to a subroutine call entry element included in the array and associated with the subroutine call.

11. The apparatus of claim 8 , wherein maintaining the array of subroutine call elements further includes:

adding a single shared subroutine call entry element to the array;

adding a second subroutine call entry element to the array when a second subroutine is called, the second subroutine call entry element including a first pointer to the single shared subroutine call entry element;

adding a third subroutine call entry element to the array when a third subroutine is called, the third subroutine call entry element including a second pointer to the single shared subroutine call entry element; and

removing, when the third subroutine exits, the third subroutine call entry element from the array based on determining that the third subroutine is not selected for data recording.

12. The apparatus of claim 8 , wherein managing collecting of subroutine call information includes, only for each subroutine call selected for data recording, collecting all input arguments passed to the subroutine call and a return value, if any, from the call of a respective subroutine.

13. The apparatus of claim 8 , wherein maintaining the array of subroutine call elements further includes:

adding a second subroutine call entry element to the array when a second subroutine is called; and

based on determining that the second subroutine is selected for detailed data recording, and when the second subroutine exits,

retaining the second subroutine call entry element in the array, and

adding a second subroutine call exit element to the array.

14. The apparatus of claim 13 , wherein the second subroutine call exit element includes subroutine call information regarding the second subroutine call.

15. A computer program product for aiding software analysis, the computer program product being tangibly and non-transitorily embodied on a non-transitory computer-readable medium and including executable code that, when executed, is configured to cause an apparatus to:

monitor the execution of a software application;

collect subroutine call information regarding a plurality of subroutine calls included by the software application;

select one or more of the plurality of subroutine calls for data recording;

maintain an array of one or more subroutine call elements, each subroutine call element being associated with a respective subroutine call, the maintaining including:

adding a first subroutine call entry element to the array when a first subroutine is called;

retaining, when the first subroutine exits, the first subroutine call entry element in the array based on determining that the first subroutine is associated with a parent subroutine included in the one or more of the plurality of subroutine calls selected for data recording;

selecting at least one of the subroutine call elements from the array of one or more subroutine call elements; and

removing the at least one selected subroutine call element from the array of one or more subroutine call elements; and

generate a subroutine call tree based on the array of one or more subroutine call elements, the subroutine call tree including the first subroutine call associated with the first subroutine call entry element and omitting the subroutine call associated with the at least one selected subroutine call element.

16. The computer program product of claim 15 , wherein the executable code that, when executed, is configured to cause the apparatus to maintain the array of one or more subroutine call elements includes executable code that, when executed, is configured to further cause the apparatus to:

add a single shared subroutine call entry element to the array;

add a second subroutine call entry element to the array when a second subroutine is called, the second subroutine call entry element including a first pointer to the single shared subroutine call entry element;

add a third subroutine call entry element to the array when a third subroutine is called, the third subroutine call entry element including a second pointer to the single shared subroutine call entry element; and

remove, when the third subroutine exits, the third subroutine call entry element from the array based on determining that the third subroutine is not selected for data recording.

17. The computer program product of claim 15 , wherein the executable code, when executed, is configured to further cause the apparatus to:

only for each subroutine call selected for data recording, collect all input arguments passed to the subroutine call and a return value, if any, from the call of a respective subroutine.

18. The computer program product of claim 15 ,

wherein the executable code that, when executed, is configured to cause the apparatus to monitor the execution of the software application includes executable code that, when executed, is configured to further cause the apparatus to inject code into the plurality of subroutine calls selected for data recording, and

wherein the executable code that, when executed, is configured to cause the apparatus to collect subroutine call information regarding the plurality of subroutine calls included in the software application includes executable code that, when executed, is configured to further cause the apparatus to collect the subroutine call information using the injected code included in the plurality of subroutine calls selected for data recording.

19. The computer program product of claim 15 , wherein the executable code that, when executed, is configured to cause the apparatus to maintain the array of one or more subroutine call elements includes executable code that, when executed, is configured to further cause the apparatus to:

add a second subroutine call entry element to the array when a second subroutine is called; and

based on determining that the second subroutine is selected for data recording, and when the second subroutine exits,

retain the second subroutine call entry element in the array, and

add a second subroutine call exit element to the array.

20. The computer program product of claim 15 , wherein the executable code that, when executed, is configured to cause the apparatus to collect subroutine call information includes executable code that, when executed, is configured to further cause the apparatus to, for each subroutine call, place on a memory stack an entry time associated with the subroutine call, and a pointer to a subroutine call entry element included in the array and associated with the subroutine call.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 17, 2026
From: BMC SOFTWARE ISRAEL LTD
To: BMC HELIX ISRAEL LTD.
Reel/Frame 075403/0859 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2018
From: IDENTIFY SOFTWARE LTD.
To: BMC SOFTWARE ISRAEL LTD.
Reel/Frame 047465/0855 →
MERGER Recorded Nov 9, 2018
From: IDENTIFY SOFTWARE LTD.
To: BMC SOFTWARE ISRAEL LTD.
Reel/Frame 047465/0871 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 20, 2017
From: KOREN, EYAL; DAFNER, ASAF; JUDELMAN, SHIRI S.
To: IDENTIFY SOFTWARE LTD. (IL)
Reel/Frame 043054/0763 →
Continuity (3)
Continuation 15003280 · Jan 21, 2016
Continuation 13630784 · Sep 28, 2012
Related Publication 20170039127A1 · Feb 9, 2017