And solved (I think ...) #if swift(>=5.9) self.clipsToBounds = true #endif

@eskimo Sorry to ressurect an old thread. I was just faced with this very issue trying to run a shell script using Process(). My program was waiting 10 seconds for enough data to fill the buffer before the 1 second updates from the script were presented to my read handler. On reading man setbuf, I saw a reference to setting the environment variable STDBUF. Inserting export STDBUF="U" into the script seems to have solved the problem and my program now receives each message as it is output from the shell script. I was unable to find reference to this environment variable anywhere else and am just asking for reassurance that it won't suddenly disappear.

Fixed with Xcode 14.3 beta 3

Submitted FB12051702 with a sample project demonstrating the failure.

Instead of looking to call Swift from C++ you should probably look at it the other way round. Use Swift as the main language for your development - it integrates beautifully with Interface Builder and is ideally suited for building a gui. You can then make calls to C/C++/Obj-C using the Swift bridging interfaces. Admittedly there is a bit to learn but I think you'll find Swift to be quite easy to become familiar with. I have found C/C++ to be very useful in Swift applications for dealing with Posix/System interfaces, then passing results back to Swift either as arguments or via closure/callbacks.

Not a commandline solution but whatroute (https://whatroute.net) will perform tcp traceroute.

I run the script under rosetta on an M1 with python3 by using: arch -x86_64 scripts/SMJobBlessUtil-python3.py check path_to_bundle It seems to work

If you are using an Apple Silicon Mac, have you tried running the script under Rosetta2?

I ran into a similar problem a few months back. The solution was to upgrade SMJobBlessUtil.py to python3. The issue was covered in https://developer.apple.com/forums/thread/699310 The conversion seems to work but I have only run it with my own use cases and not done any rigorous testing.

I have a suspicion that this problem is related to the libresolv security patches applied in https://support.apple.com/en-us/HT213257 and https://support.apple.com/en-us/HT213256 to macOS. Presumably this same libresolv security fix was also applied to iOS.

I have a suspicion that this problem is related to the libresolv security patches applied in https://support.apple.com/en-us/HT213257 and https://support.apple.com/en-us/HT213256.

@mikeyh Thank you so much for this. I have just tried your patched code and it is working in my build process. I'll refrain from marking your solution as accepted for now, just in case there are more comments/improvements from others, but it seems to be working fine.

I am pretty sure the limiting factor here is not the RAM allocated to the copy/move process but instead the speed of your devices. What is the transfer rate of your source device? What is the transfer rate of the target? Are you using USB? Are these SSD devices? Is it a network connecton? All of these have for more impact than the amount of memry allocated to the process.