Runtime Stack Cross-Reference Mechanism for Variable File Names
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cross-reference systems are incomplete as they cannot accurately reflect associations between executable objects and files, especially when file names are defined by variables whose values are unknown at compilation time, leading to incomplete cross-reference information.
Innovation Solution
A method that collects and stores runtime data to generate comprehensive, system-wide cross-reference information by retrieving file names from the runtime stack and updating cross-reference data to include associations made during application execution, even when file names are resolved at runtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If cross-reference information is gathered by source code analyzers or compilers at compilation time, then the process is simple and fast, but the cross-reference information is incomplete because variable values are unknown at compilation time
Solution Approach 1:
The system performs preliminary actions by instrumenting the runtime stack to automatically capture file access information during execution. This preliminary data collection at runtime ensures complete cross-reference information is gathered before security analysis, resolving the incompleteness issue without requiring complex manual instrumentation later.
Solution Approach 2:
The patent introduces a runtime stack as an intermediary mechanism between the application execution and the cross-reference data collection. This intermediary automatically captures variable resolutions and file access patterns during runtime, providing complete cross-reference information without directly modifying source code or complicating the compilation process.
2Loss of information
If variable values are resolved at runtime, then complete file associations can be captured, but conventional compilers and source code analyzers cannot include this information in cross-reference files
Solution Approach 1:
The system implements continuous data collection during the entire runtime execution of applications. The runtime stack continuously monitors and captures file access information as it occurs, ensuring no file access information is lost without requiring separate post-processing time, as the collection happens continuously during normal execution.
Solution Approach 2:
The runtime stack performs self-service by automatically capturing its own execution state and file access information without external intervention. This self-reflective capability allows the system to collect complete cross-reference data during normal execution without adding significant overhead or requiring additional collection time.
3Reliability
If runtime data collection is implemented, then complete and accurate cross-reference information is obtained, but the system complexity increases
Solution Approach 1:
The runtime stack is designed with multi-functionality, serving both normal application execution and cross-reference data collection purposes. This universal mechanism handles both computational tasks and monitoring tasks without requiring separate dedicated systems, thereby improving reliability while minimizing the increase in overall system complexity.
Solution Approach 2:
The patent embeds the cross-reference data collection mechanism within the existing runtime stack structure, creating a nested architecture where the monitoring function is integrated inside the execution framework. This nesting approach allows accurate data collection while leveraging existing runtime infrastructure, reducing the need for additional complex external systems.
Data Source
AI summary
Techniques for computer security are provided. A request to access a first file referenced as a variable in a source code of an application is received. A file name of the first file is then retrieved from a runtime stack, and the file name is stored in a system-wide accessible cross-reference file.