Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13

[Clemens Lang]

Hi,

On Sun, Apr 29, 2018 at 09:34:10AM +0200, Mojca Miklavec wrote:
> Hi,
> 
> This looks pretty strange to me:
> 
> --->  Fetching distfiles for pymol
> Executing:  cd "/path/to/pymol/work" && /usr/bin/svn --non-interactive
> --trust-server-cert export
> http://svn.code.sf.net/p/pymol/code/trunk/pymol@4187 2>&1
> dyld: warning: could not load inserted library
> '/opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib'
> into library validated process because no suitable image found.  Did
> find:
> /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib: code
> signing blocked mmap() of
> '/opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib'
> /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib:
> stat() failed with errno=1
> dyld: warning: could not load inserted library
> '/opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib'
> into library validated process because no suitable image found.  Did
> find:
> /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib: code
> signing blocked mmap() of
> '/opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib'
> /opt/local/libexec/macports/lib/darwintrace1.0/darwintrace.dylib:
> stat() failed with errno=1

Those are normal in signed binaries. Apple's system integrity protection
prevents loading the trace mode library into signed processes, unless it
is also signed (which our copy is not).

This usually means that the binary will not run under trace mode, i.e.
your svn fetch was run without trace mode. In consequence, this means
that your fetch failure could not have been related to trace mode.

-- 
Clemens Lang