IP Library Granted Patent US 8,972,791
Granted Patent B2
US 8,972,791 · App. 13/362,751 · Granted Mar 3, 2015

Managing code-tracing data

Inventor: Richard Han (Angus, GB)
Assignee: NCR Corporation
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 8,972,791
App. No.
13/362,751
Granted
Mar 3, 2015
Kind
B2
Abstract

A method of managing code-tracing data in a target program is described. The method comprises the steps of: identifying when an exception occurs in the target program; accessing a stack trace of a call stack to identify a module in the target program that threw the exception; and activating code-tracing at a high detail level in that module.

Claims (44)

1. A method of managing code-tracing data in a target program, the method comprises the steps of:

identifying when an exception occurs in the target program;

accessing a stack trace of a call stack to identify a module in the target program that threw the exception;

assigning a level of code tracing in that module including activating code-tracing at a high detail level in that module; and

returning the code-tracing levels to a default value after a time period expires with no exception being thrown.

2. A method according to claim 1 , wherein the method comprises the further steps of:

accessing the stack trace to identify a module in the target program that called the exception-throwing module; and

activating code-tracing at a medium detail level in that module.

3. A method according to claim 2 , wherein the method comprises the further steps of:

accessing the stack trace to identify a module in the target program that called the module that called the exception-throwing module; and

activating code-tracing at a low detail level in that module that called the module that called the exception-throwing module.

4. A method according to claim 3 , wherein the method comprises the further step of:

activating code-tracing at a minimal detail level in the rest of the target program.

5. A method according to claim 1 , wherein the method comprises the further steps of:

identifying modules called by the exception-throwing module; and

activating code-tracing at a medium detail level in those modules.

6. A method according to claim 5 , wherein the step of identifying the called modules is implemented using a call identification module that analyses the exception module.

7. A method according to claim 1 , wherein the method comprises the additional step of:

accessing a code-tracing map that indicates what code-tracing settings should be activated if an exception occurs in a specified module.

8. A method of managing code-tracing data in a target program, the method comprises the steps of:

identifying when an exception occurs in the target program;

accessing a stack trace of a call stack to identify a module in the target program that threw the exception;

assigning a level of code tracing in that module including activating code-tracing at a high detail level in that module; and

decreasing the code-tracing levels over time if no exception is thrown.

9. A method of managing code-tracing data in a target program, the method comprises the steps of:

identifying when an exception occurs in the target program;

accessing a stack trace of a call stack to identify a module in the target program that threw the exception;

assigning a level of code tracing in that module including activating code-tracing at a high detail level in that module; and

increasing the code-tracing levels over time if an exception is thrown within a preset time period of restarting the target program.

10. A method of managing code-tracing data in a target program, the method comprises the steps of:

identifying when an exception occurs in the target program;

accessing a stack trace of a call stack to identify a module in the target program that threw the exception;

activating code-tracing at a high detail level in that module; and

returning the code-tracing levels to a default value after a time period expires with no exception being thrown.

11. A method of managing code-tracing data in a target program, the method comprises the steps of:

identifying when an exception occurs in the target program;

accessing a stack trace of a call stack to identify a module in the target program that threw the exception;

activating code-tracing at a high detail level in that module; and

decreasing the code-tracing levels over time if no exception is thrown.

12. A method of managing code-tracing data in a target program, the method comprises the steps of:

identifying when an exception occurs in the target program;

accessing a stack trace of a call stack to identify a module in the target program that threw the exception;

activating code-tracing at a high detail level in that module; and

increasing the code-tracing levels over time if an exception is thrown within a preset time period of restarting the target program.

Assignments (10)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE PROPERTIES SECTION BY INCLUDING IT WITH TEN PREVIOUSLY OMITTED PROPERTY NUMBERS PREVIOUSLY RECORDED ON REEL 65346 FRAME 367. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Aug 13, 2025
From: NCR ATLEOS CORPORATION; CARDTRONICS USA, LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 072445/0072 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 30, 2024
From: NCR VOYIX CORPORATION
To: NCR ATLEOS CORPORATION
Reel/Frame 067590/0109 →
CHANGE OF NAME Recorded May 30, 2024
From: NCR CORPORATION
To: NCR VOYIX CORPORATION
Reel/Frame 067578/0417 →
CORRECTIVE ASSIGNMENT TO CORRECT THE DOCUMENT DATE AND REMOVE THE OATH/DECLARATION (37 CFR 1.63) PREVIOUSLY RECORDED AT REEL: 065331 FRAME: 0297. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Oct 31, 2023
From: NCR ATLEOS CORPORATION
To: CITIBANK, N.A.
Reel/Frame 065627/0332 →
SECURITY INTEREST Recorded Oct 25, 2023
From: NCR ATLEOS CORPORATION; CARDTRONICS USA, LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 065346/0367 →
RELEASE OF PATENT SECURITY INTEREST Recorded Oct 25, 2023
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: NCR VOYIX CORPORATION
Reel/Frame 065346/0531 →
SECURITY INTEREST Recorded Oct 24, 2023
From: NCR ATLEOS CORPORATION
To: CITIBANK, N.A.
Reel/Frame 065331/0297 →
SECURITY AGREEMENT Recorded Apr 18, 2016
From: NCR CORPORATION; NCR INTERNATIONAL, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 038646/0001 →
SECURITY AGREEMENT Recorded Jan 15, 2014
From: NCR CORPORATION; NCR INTERNATIONAL, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 032034/0010 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 23, 2012
From: HAN, RICHARD
To: NCR CORPORATION
Reel/Frame 027753/0008 →
Continuity (1)
Related Publication 20130198572A1 · Aug 1, 2013