Poll the fifo once before reading to detect when a process never loads libc The fifo should be opened for writing from the traced process itself after the LD_PRELOAD injection. This however will not happen if the process does not dynamically link libc. And this happens to be the case in most Go programs. This change adds two tests to ensure fsatrace exits when run on a process that does not load libc and does not hang if the write end of the fifo exits before the read end consumes any bytes. Change-Id: If1a717614f42761c706724d1b6e560db055a5539
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 fsatrace.exe, fsatracehelper.exe, fsatrace32.dll and fsatrace64.dll.
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 vectorr: dump read operationsw: dump write operationsm: dump file move operationsd: dump file delete operationsq: dump file stat operationst: dump touch operationsFSAT_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:
r|path-to-file-opened-for-writew|path-to-file-opened-for-readm|path-to-destination-of-move|path-to-source-of-moved|path-to-deleted-fileq|path-to-queried-filet|path-to-touched-file