History of AFNI updates  

|
June 30, 2022 04:50PM
One part of this confusion that's Mac specific is the blocking of DYLD variables from one shell to another. The path must be inherited; otherwise, it wouldn't know where to find afni or suma to begin with. This information is for the System Integrity Protection (SIP) that the MacOS introduced in 2015:

"Spawning children processes of processes restricted by System Integrity Protection, such as by launching a helper process in a bundle with NSTask or calling the exec(2) command, resets the Mach special ports of that child process. Any dynamic linker (dyld) environment variables, such as DYLD_LIBRARY_PATH, are purged when launching protected processes."
Subject Author Posted

SIGSEV when trying to drive AFNI from command line

jbteves June 29, 2022 03:08PM

Re: SIGSEV when trying to drive AFNI from command line

ptaylor June 29, 2022 03:54PM

Re: SIGSEV when trying to drive AFNI from command line

ptaylor June 29, 2022 04:02PM

Re: SIGSEV when trying to drive AFNI from command line

jbteves June 29, 2022 04:16PM

Re: SIGSEV when trying to drive AFNI from command line

ptaylor June 29, 2022 04:53PM

Re: SIGSEV when trying to drive AFNI from command line

rick reynolds June 29, 2022 10:09PM

Re: SIGSEV when trying to drive AFNI from command line

jbteves June 29, 2022 10:32PM

Re: SIGSEV when trying to drive AFNI from command line

ptaylor June 29, 2022 10:42PM

Re: SIGSEV when trying to drive AFNI from command line

Daniel Glen June 30, 2022 04:50PM