| tag | 8350d5eb81cb4f5459af0b1a38e8e2fab93ef7e4 | |
|---|---|---|
| tagger | Jorge Acereda <jacereda@gmail.com> | Fri Sep 25 18:51:12 2015 +0200 |
| object | eaef8d73cb6d40d0c5beccfe2becbc4f6e90ac6a |
Tagged v0.0.1
| commit | eaef8d73cb6d40d0c5beccfe2becbc4f6e90ac6a | [log] [tgz] |
|---|---|---|
| author | Jorge Acereda <jacereda@gmail.com> | Fri Sep 25 18:45:47 2015 +0200 |
| committer | Jorge Acereda <jacereda@gmail.com> | Fri Sep 25 18:45:47 2015 +0200 |
| tree | e1aaa367e3178636265d4ba63015281da84ce199 | |
| parent | 315a6c187fe9208893c1afc7b8dc16f0d2eecfc2 [diff] |
Avoid use of printfs when emitting. DRY.
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 Windows, type build.bat to compile fsatrace.exe and associated DLLs fsatrace32.dll / fsatrace64.dll. The build script assumes VS 2015 is installed, if that's not the case just edit it so it can find the correct location of vcvarsall.bat.
On Unix, type make to generate a fsatrace.so object.
Make sure the .dll or .so files are in the same path as the executable and run:
fsatrace <output-file> -- <command>
Newline-separated sequence with the following possibilities:
path-to-file-opened-for-readpath-to-file-opened-for-writepath-to-destination-of-move|path-to-source-of-movepath-to-deleted-file