The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Mar. 03, 2009
Filed:
Mar. 25, 2005
Andrew James Edwards, Bellevue, WA (US);
Ronnie I. Chaiken, Woodinville, WA (US);
Dzmitry Suponau, Bellevue, WA (US);
S. Craig Schertz, Issaquah, WA (US);
Andrew James Edwards, Bellevue, WA (US);
Ronnie I. Chaiken, Woodinville, WA (US);
Dzmitry Suponau, Bellevue, WA (US);
S. Craig Schertz, Issaquah, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
Ambiguous stack references in low level software instructions can be resolved when raising a representation of low level software instructions, such as native code. The number of parameters passed to a function can be determined by heuristics, including direct call and indirect call heuristics. Indirect call heuristics can include dataflow-to-target-function, dataflow-to-target-type, import name, and cleanup instructions heuristics. A control flow heuristic can use an alternating direction propagation of seed points to determine the stack height at basic block boundaries. Interpolation can be used within the basic blocks as needed. The raised representation can be used for static analysis of the low level software instructions.