Can't trace gcc on Mac

[ndmitchell]

Even after copying the gcc binary into $TMP doing gcc -c main.c doesn't trace the read of main.c or the write of main.o. My guess is because gcc spawns a binary that is itself in system which doesn't get the copy treatment? Anything that can be done about that, short of turning off system protection?

[jacereda]

Maybe using a nixpkgs or homebrew toolchain?

[ndmitchell]

Thanks, that's probably a workable approach for the setup I'm in.