Patent US5966541A successfully refreshed from Google Patents.
US5966541A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Test protection, and repair through binary-code augmentation
Assignee: Incert Software Corp
•
Filing: 1997-12-04
•
Granted: 1999-10-12
•
Expires: 2017-12-04
Abstract
Abstract A type mismatch problem in computer programs is said to occur when there is a mismatch between the form or classification of a value encountered during program execution and that anticipated by the program. A method for repairing or testing for many type mismatch problems in programs works by transforming a binary representation of the program into a new binary in which the problem is fixed or identified. The fix or identification is implemented by converting code that operates on variables that can suffer a mismatch into code that correctly accounts for or tests for the mismatch. Static or dynamic correlation methods, and/or control and data flow graphs are used to track certain values, to determine where to install patches and how to adjust branch, jump and procedure call references after patch installation has shifted the target references.
Inventors
- 👤 Anant Agarwal
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-04 21:27
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/40; G06F8/52
Claims Analysis
Total Claims: 34
Claim 1
Independent Claim
125 words
A method of testing, protecting, or correcting binary code, comprising: generating, from the binary code, a control flow representation of the binary code; generating, from the binary code, a data flow representation of the binary code; choosing which values or variables to track; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; using the data flow representation to track the chosen values or variables, wherein determining where to install the software patches is further based on an analysis of the data flow representation; and rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 2
Independent Claim
125 words
A method of testing, protecting, or correcting binary code, comprising: generating, from the binary code, a control flow representation of the binary code; generating, from the binary code, a data flow representation of the binary code; choosing which values or variables to track; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; using the data flow representation to track the chosen values or variables, wherein determining where to install the software patches is further based on an analysis of the data flow representation; and rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 3
Dependent Claim
19 words
A method as claimed in claim 1, wherein such method is used to perform overflow detection, repair and test.
Claim 4
Dependent Claim
16 words
A method as claimed in claim 1, wherein such method is used to perform assertion checking.
Claim 5
Dependent Claim
16 words
A method as claimed in claim 1, wherein such method is used to perform coverage testing.
Claim 6
Dependent Claim
18 words
A method as claimed in claim 1, wherein such method is used to perform argument remediation coverage testing.
Claim 7
Dependent Claim
16 words
A method as claimed in claim 1, wherein such method is used to perform continuous testing.
Claim 8
Dependent Claim
17 words
A method as claimed in claim 1, wherein such method is used to perform bootstrap regression testing.
Claim 9
Dependent Claim
17 words
A method as claimed in claim 1, wherein such method is used to perform test path identification.
Claim 10
Dependent Claim
16 words
A method as claimed in claim 1, wherein such method is used to perform date identification.
Claim 11
Dependent Claim
17 words
A method as claimed in claim 1, wherein such method is used to perform zip code identification.
Claim 12
Dependent Claim
20 words
A method as claimed in claim 1, wherein such method is used to perform telephone number or area code identification.
Claim 13
Dependent Claim
16 words
A method as claimed in claim 1, wherein such method is used to perform currency identification.
Claim 14
Independent Claim
153 words
A method of testing, protecting, or correcting binary code, comprising: generating a control flow representation of the binary code; generating a data flow representation of the binary code; choosing which values or variables to track; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; using the data flow representation to track the chosen values or variables, wherein determining where to install the software patches is further based on an analysis of the data flow representation; rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches; and wherein such method is used to perform date overflow and detection and further comprising the step of identifying date variables and values and wherein the software patches perform a windowing function on date values and variables.
Claim 15
Independent Claim
153 words
A method of testing, protecting, or correcting binary code, comprising: generating a control flow representation of the binary code; generating a data flow representation of the binary code; choosing which values or variables to track; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; using the data flow representation to track the chosen values or variables, wherein determining where to install the software patches is further based on an analysis of the data flow representation; rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches; and wherein such method is used to perform date overflow and detection and further comprising the step of identifying date variables and values and wherein the software patches perform a windowing function on date values and variables.
Claim 16
Dependent Claim
21 words
A method as claimed in claim 13 wherein date variables and values are identified by identifying variable names in source code.
Claim 17
Dependent Claim
24 words
A method as claimed in claim 13 wherein date variables and values are identified by identifying, in source code, system calls which obtain dates.
Claim 18
Dependent Claim
25 words
A method as claimed in claim 13 wherein date variables and values are identified by identifying, in the binary code, system calls which obtain dates.
Claim 19
Dependent Claim
21 words
A method as claimed in claim 13 wherein date variables and values are indentified by identifing date fields from a database.
Claim 20
Independent Claim
76 words
A method of testing, protecting, or correcting binary code, comprising: executing the original binary code under interpretation; generating a control flow reprcsentation of the binary code; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 21
Independent Claim
76 words
A method of testing, protecting, or correcting binary code, comprising: executing the original binary code under interpretation; generating a control flow reprcsentation of the binary code; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 22
Dependent Claim
20 words
A method as claimed in claim 18 wherein the step of executing under interpretation is used to identify branch targets.
Claim 23
Dependent Claim
22 words
A method as claimed in claim 18 wherein the step of executing under interpretation is used to identify instructions that use dates.
Claim 24
Independent Claim
154 words
A method of testing, protecting, or correcting binary code, comprising; generating a control flow representation of the binary code; generating a data flow representation of the binary code; choosing which values or variables to track; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; using the data flow representation to track the chosen values or variables, wherein determining where to install the software patches is further based on an analysis of the data flow representation; rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches; and wherein such method is used to perform date overflow and detection and further comprises the step of identifying date variables and values and wherein the software patches perform a date expansion function on date values and variables.
Claim 25
Independent Claim
154 words
A method of testing, protecting, or correcting binary code, comprising; generating a control flow representation of the binary code; generating a data flow representation of the binary code; choosing which values or variables to track; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; using the data flow representation to track the chosen values or variables, wherein determining where to install the software patches is further based on an analysis of the data flow representation; rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches; and wherein such method is used to perform date overflow and detection and further comprises the step of identifying date variables and values and wherein the software patches perform a date expansion function on date values and variables.
Claim 26
Independent Claim
79 words
A method of testing, protecting, or correcting binary code, comprising; using a static target correlation to identify branch targets; generating a control flow representation of the binary code; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; and rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 27
Independent Claim
79 words
A method of testing, protecting, or correcting binary code, comprising; using a static target correlation to identify branch targets; generating a control flow representation of the binary code; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; and rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 28
Independent Claim
79 words
A method of testing, protecting, or correcting binary code, comprising; using a dynamic target correlation to identify branch targets; generating a control flow representation of the binary code; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; and rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 29
Independent Claim
79 words
A method of testing, protecting, or correcting binary code, comprising; using a dynamic target correlation to identify branch targets; generating a control flow representation of the binary code; defining binary software patches; determining where to install the software patches based on an analysis of the control flow representation; and rewriting the binary code by installing the binary software patches into the original binary code and further modifying the original binary code to account for the installed binary software patches.
Claim 30
Dependent Claim
84 words
A data processing system for testing, protecting, or correcting binary code, comprising: correlation means for identifying control points; a control flow representation of the binary code; binary software patches; means for determining where to install the software patches based on an analysis of the control flow representation; and means for rewriting the binary code by installing the binary software patches into the original binary code and by modifying the original binary code to account for code displacements due to the installed binary software patches.
Claim 31
Dependent Claim
84 words
A data processing system for testing, protecting, or correcting binary code, comprising: correlation means for identifying control points; a control flow representation of the binary code; binary software patches; means for determining where to install the software patches based on an analysis of the control flow representation; and means for rewriting the binary code by installing the binary software patches into the original binary code and by modifying the original binary code to account for code displacements due to the installed binary software patches.
Claim 32
Dependent Claim
62 words
A data processing system as claimed in claim 24, further comprising: a data flow representation of the binary code; means for choosing which values or variables to track; and means for using the data flow representation to track the chosen values or variables wherein determining where to install the software patches is further based on an analysis of the data flow representation.
Claim 33
Dependent Claim
22 words
A data processing system as claimed in claim 24, wherein said correlation means comprises static target correlation means for identifying control points.
Claim 34
Dependent Claim
22 words
A data processing system as claimed in claim 24, wherein said correlation means comprises dynamic target correlation means for identifying control points.
References Cited (Backward Citations)
US4951195A
Cited
US5241678A
Cited
US5488714A
Cited
US5428786A
Cited
US5546586A
Cited
US5675803A
Cited
US5615369A
Cited
US5764992A
Cited
US5732275A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-10-11 | 2003-04-12 | 2003-10-12 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-10-11 | 2007-04-12 | 2007-10-12 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-10-11 | 2011-04-12 | 2011-10-12 | $7700.00 | Window Closed / Lapsed |