You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 28, 2026. It is now read-only.
Binary analysis of ELF files is used in two places: causal profiling and instrumentation. Currently, this step is performed every causal profiling run and every time the omnitrace exe is used but the info is static (unless the file has been modified since the last time it was read). For large applications, this can be time consuming and it is especially tedious when omnitrace-causal is replaying the application numerous times. Proposal is to perform the binary analysis and cache it to a JSON or XML file alongside the file modification timestamp and if the current time is > the modification time, simply read in the cached JSON or XML file.
Binary analysis of ELF files is used in two places: causal profiling and instrumentation. Currently, this step is performed every causal profiling run and every time the
omnitraceexe is used but the info is static (unless the file has been modified since the last time it was read). For large applications, this can be time consuming and it is especially tedious whenomnitrace-causalis replaying the application numerous times. Proposal is to perform the binary analysis and cache it to a JSON or XML file alongside the file modification timestamp and if the current time is > the modification time, simply read in the cached JSON or XML file.