|author||Tamir Duberstein <email@example.com>||Wed Aug 17 20:02:54 2022 -0400|
|committer||Tamir Duberstein <firstname.lastname@example.org>||Wed Aug 17 20:04:22 2022 -0400|
Pass fifo as absolute path Some actions may immediately change directories before beginning execution. Add a missing error check that helped track this down. Change-Id: Ic45d75a6745fe4b667a5957bedcabef00f6785e4
This tool injects code into other applications in order to trace file accesses.
This can be useful for things like build systems, since it allows to automatically generate dependencies in a toolchain-agnostic way or to ensure declared dependencies match the real ones.
On Unix, type
make to generate the
fsatrace executable and the
fsatrace.so shared library.
On Windows, you'll need recent 64-bit and 32-bit versions of
mingw. You can either adapt the
Makefile to point to your compilers or, alternatively, install https://github.com/commercialhaskell/stack and run the following sequence to get the required compilers:
stack setup --resolver ghc-8.6.5 --arch=x86_64 stack setup --resolver ghc-8.6.5 --arch=i386 stack exec -- pacman -S make
After that, invoke:
stack exec -- make
That should generate
Make sure the .dll or .so files are in the same path as the
fsatrace executable and run:
fsatrace <options> <output-file> -- <command>
Options is a combination of the following characters:
v: print args vector
r: dump read operations
w: dump write operations
m: dump file move operations
d: dump file delete operations
q: dump file stat operations
t: dump touch operations
FSAT_BUF_SIZE: when set, overwrites size of buffer for trace output.
In order to use
fsatrace on systems newer than OS X 10.10, System Integrity Protection must be disabled as detailed in https://developer.apple.com/library/content/documentation/Security/Conceptual/System_Integrity_Protection_Guide/ConfiguringSystemIntegrityProtection/ConfiguringSystemIntegrityProtection.html
Use at your own risk!
Newline-separated sequence with the following possibilities: