IP Library Granted Patent US 9,483,391
Granted Patent B2
US 9,483,391 · App. 15/003,280 · Granted Nov 1, 2016

Efficient method data recording

Inventors: Eyal Koren (Dafna, IL); Asaf Dafner (Gedera, IL); Shiri Semo Judelman (Kfar-Saba, IL)
Assignee: Identify Software Ltd.
G06F11/3688G06F8/70G06F9/4425G06F11/3466G06F11/3636
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,483,391
App. No.
15/003,280
Granted
Nov 1, 2016
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 (76)

1. A method executed by a processor, comprising:

monitoring the execution of at least a portion of a software application;

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

selecting one or more of the plurality of subroutine calls for detailed 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 shared subroutine call entry element to the array; and

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

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

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 generating including omitting the subroutine call associated with the removed at least one selected subroutine call element from the subroutine call tree.

2. 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, the second subroutine call entry element including a second pointer to the shared subroutine call entry element; and

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

3. The method of claim 1 , wherein monitoring the execution of at least a portion of a software application includes injecting code into the plurality of subroutine calls selected for detailed data recording.

4. The method of claim 1 , wherein collecting subroutine call information regarding the plurality of subroutine calls included in the portion of the software application includes, only for each subroutine call selected for detail data recording, collecting all of the 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 the maintaining of 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,

not removing the second subroutine call entry element from 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 the maintaining of 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

not removing, when the second subroutine exits, the second subroutine call entry element from the array based on determining that the second subroutine is associated with a parent subroutine that is selected for detailed data recording.

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

9. An apparatus comprising:

a monitoring engine configured to:

monitor execution of at least a portion of a software application,

a processor configured to:

execute the software application,

select one or more of a plurality of subroutine calls for detailed 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 portion of the software application,

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

adding a shared subroutine call entry element to the array of one or more subroutine call elements, and

adding a first subroutine call entry element to the array of one or more subroutine call elements when a first subroutine is called, the first subroutine call entry element including a first pointer to the shared subroutine call entry element, and

remove one or more subroutine call elements from the array of subroutine call elements, the removing omitting respective subroutine calls, associated with the removed one or more subroutine call elements, from the subroutine call tree, and

a memory configured to:

store the subroutine call information.

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

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

11. The apparatus of claim 9 ,

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.

12. The apparatus of claim 9 , wherein the maintaining of 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, the second subroutine call entry element including a second pointer to the shared subroutine call entry element; and

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

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

14. The apparatus of claim 9 , wherein the maintaining of 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,

not removing the second subroutine call entry element from the array, and

adding a second subroutine call exit element to the array.

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

16. The apparatus of claim 9 , wherein the maintaining of 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

not removing, when the second subroutine exits, the second subroutine call entry element from the array based on determining that the second subroutine is associated with a parent subroutine that is selected for detailed data recording.

17. 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 at least a portion of a software application;

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

select one or more of the plurality of subroutine calls for detailed 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 shared subroutine call entry element to the array of one or more subroutine call elements; and

adding a first subroutine call entry element to the array of one or more subroutine call elements when a first subroutine is called, the first subroutine call entry element including a first pointer to the shared subroutine call entry element;

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

remove 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 generating including omitting the subroutine call associated with the removed at least one selected subroutine call element from the subroutine call tree.

18. The computer program product of claim 17 , wherein the maintaining of 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, the second subroutine call entry element including a second pointer to the shared subroutine call entry element; and

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

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

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

20. The computer program product of claim 17 , wherein monitoring the execution of at least a portion of a software application includes injecting code into the plurality of subroutine calls selected for detailed data recording.

Assignments (5)
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 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE ADDRESS PREVIOUSLY RECORDED ON REEL 037609 FRAME 0044. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 20, 2017
From: KOREN, EYAL; DAFNER, ASAF; JUDELMAN, SHIRI S.
To: IDENTIFY SOFTWARE LTD. (IL)
Reel/Frame 043275/0035 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 28, 2016
From: KOREN, EYAL; DAFNER, ASAF; JUDELMAN, SHIRI S.
To: IDENTIFY SOFTWARE LTD. (IL)
Reel/Frame 037609/0044 →
Continuity (2)
Continuation 13630784 · Sep 28, 2012
Related Publication 20160140029A1 · May 19, 2016