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:
Sep. 11, 2018
Filed:
Jul. 29, 2015
National Technology & Engineering Solutions of Sandia, Llc, Albuquerque, NM (US);
Amy Sundermier, Albuquerque, NM (US);
Bettina K. Arpin, Albuquerque, NM (US);
David Karmol, Seattle, WA (US);
Lawrence P. Ray, Albuquerque, NM (US);
Kenneth Michael Munoz, Rio Rancho, NM (US);
William Lawry, Albuquerque, NM (US);
Jamie L. Coram, Albuquerque, NM (US);
Thomas Anthony Artale, Erie, CO (US);
Patrick DeMoss, Albuquerque, NM (US);
Lucas Leighton Nunno, Albuquerque, NM (US);
Aaron Easter, Blue Springs, MO (US);
National Technology & Engineering Solutions of Sandia, LLC, Albuquerque, NM (US);
Abstract
Various technologies pertaining to computer-executable instruction sequence forensics are described herein. In a general embodiment, an application development framework supports a function library that includes a plurality of recording functions. Calls to these functions are inserted into source code or bytecode of the computer-executable instruction sequence. The source code is then compiled, resulting in formation of instrumented machine code of the computer-executable instruction sequence. Alternately, the runtime environment interprets instrumented bytecode for the instruction sequence. A processor executes the machine code, and the called functions cause the processor to generate forensic data pertaining to portions of the computer-executable instruction sequence that correspond to locations in the source code where the calls were inserted. An execution instance of the computer-executable instruction sequence is visualized based upon the forensic data.