Fault tolerant compilation with automatic optimization adjustment
US-9207921-B2 · Dec 8, 2015 · US
US9483381B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9483381-B2 |
| Application number | US-201414570998-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 15, 2014 |
| Priority date | Dec 15, 2014 |
| Publication date | Nov 1, 2016 |
| Grant date | Nov 1, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An information handling system, method, and computer-readable media for obfuscating debugging filenames during a software build are described. The system comprises one or more processors, a memory, and one or more program modules stored on the memory and executable by the one or more processors. The one or more program modules compile a source code file of a plurality of source code files into a program, generate a debugging file including debugging information for the program, utilize a one-way deterministic function to generate an obfuscated filename for the debugging file, and include a link to the debugging file in the program, the link including the obfuscated filename.
Opening claim text (preview).
What is claimed is: 1. An information handling system for obfuscating debugging filenames during a software build, the information handling system comprising: one or more processors; a memory; one or more program modules stored on the memory and executable by the one or more processors to: compile a source code file or a plurality of source code files into software modules; pass file names of the software modules to a script; generate, at least in part by the script and based at least in part on a one-way deterministic function, obfuscated filenames for the filenames of the software modules; pass the obfuscated filenames as arguments to a linker module; and generate, by the linker module, a software image file to include links to debugging files, the links including the obfuscated filenames. 2. The information handling system of claim 1 , wherein the one-way deterministic function utilizes at least an original filename of the source code file or the program as an input into the one-way deterministic function to generate the obfuscated filename. 3. The information handling system of claim 2 , wherein the one-way deterministic function utilizes at least a cryptographic salt as another input into the one-way deterministic function to generate the obfuscated filename. 4. The information handling system of claim 1 , wherein the one or more program modules are further executable by the one or more processors to generate a reverse-lookup file that associates the obfuscated filename with an original filename of the source code file or the program. 5. The information handling system of claim 1 , wherein: the link to the debugging file in the program includes a directory pathway; and links for each of a plurality of debugging files, corresponding to each of the source code files, include the directory pathway. 6. The information handling system of claim 1 , wherein the one-way deterministic function is a hash function. 7. The information handling system of claim 1 , wherein the program is one of a plurality of programs included in an executable binary file, wherein the executable binary file includes links to a plurality of debugging files, one debugging file for each of the plurality of programs. 8. The information handling system of claim 7 , wherein the executable binary file is a Basic Input/Output System (BIOS) file. 9. A method for obfuscating debugging filenames during a software build, the method comprising: compile a source code file or a plurality of source code files into software modules; pass file names of the software modules to a script; generate, at least in part by the script, based at least in part on a one-way deterministic function, obfuscated filenames for the filenames of the software modules; pass the obfuscated filenames as arguments to a linker module; and generate, by the linker module, a software image file wherein the software image file is a Basic Input/Output System (BIOS) file, wherein the software image file includes links to debugging files, the links including the obfuscated filename. 10. The method of claim 9 , further comprising utilizing at least an original filename of the source code file or the program as an input into the one-way deterministic function to generate the obfuscated filename. 11. The method of claim 10 , utilizing a cryptographic salt as another input into the one-way deterministic function to generate the obfuscated filename. 12. The method of claim 9 , further comprising generating a reverse-lookup file that identifies the obfuscated filename with an original filename of the source code file or the program. 13. The method of claim 9 , wherein: the program is one of a plurality of programs included in the BIOS file; and the BIOS file includes links to a plurality of debugging files, one debugging file for each of the plurality of programs. 14. One or more non-transitory computer-readable media having programming instructions that are executable by one or more processors to perform acts comprising: compiling a source code file or a plurality of source code files into software modules; passing filenames of the software modules to a script; generating, at least in part by the script and based at least in part on a one-way deterministic function, obfuscated filenames for the filenames of the software modules; passing, by the script, the obfuscated filenames as arguments to a linker module; and generating, by the linker module, a software image file wherein the software image file is a Basic Input/Output System (BIOS) file, the software image file including links to the debugging file in the program, the link including the obfuscated filename. 15. The one or more non-transitory computer-readable media of claim 14 , wherein the acts further comprise utilizing at least an original filename of the source code file or the program as an input into the one-way deterministic function to generate the obfuscated filename. 16. The one or more non-transitory computer-readable media of claim 15 , wherein the acts further comprise utilizing a cryptographic salt as another input into the one-way deterministic function to generate the obfuscated filename. 17. The one or more non-transitory computer-readable media of claim 16 , wherein the one-way deterministic function is a hash function. 18. The one or more non-transitory computer-readable media of claim 14 , wherein: the program is one of a plurality of programs included in the BIOS file; and the BIOS file includes links to a plurality of debugging files, one debugging file for each of the plurality of programs. 19. The one or more non-transitory computer-readable media of claim 14 , wherein: the link to the debugging file in the program includes a directory pathway; and links for each of a plurality of debugging files, corresponding to each of the source code files, include the directory pathway. 20. The one or more non-transitory computer-readable media of claim 14 , wherein the one-way deterministic function comprises a hash function.
File name conversion · CPC title
Compilation · CPC title
by performing operations on the source code, e.g. via a compiler · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.