After that, my next guess would perhaps another issue related to the stack-check issue with Xcode 11. See e.g. the fix I added for OpenBLAS
https://github.com/macports/macports-ports/commit/6e78e5c9495b4dc4e7e050fae2b41dd5b9accfdd#diff-a755de84ca7f97ab071328807d829e0b > On 13 Oct 2019, at 2:31 pm, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > > Hi, > > What Xcode version are you using ? If 11.0, first try updating to 11.1 and > then rebuild the various ports (including python). > > Chris > >> On 13 Oct 2019, at 1:52 pm, Jack Howarth <howarth.at.macpo...@gmail.com> >> wrote: >> >> >> The +python37 variant of pymol runs fine under its Qt interface on >> Catalina, however the stock +python27 variant crashes Qt as follows... >> >> Process: Python [46230] >> Path: >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python >> Identifier: Python >> Version: 2.7.16 (2.7.16) >> Code Type: X86-64 (Native) >> Parent Process: zsh [907] >> Responsible: Terminal [342] >> User ID: 501 >> >> Date/Time: 2019-10-13 08:42:10.315 -0400 >> OS Version: Mac OS X 10.15 (19A583) >> Report Version: 12 >> Anonymous UUID: 4A09CC71-7509-3F2D-8C77-BB546FDAFB8D >> >> Sleep/Wake UUID: A3189974-D375-47A3-B65F-45F7E7DE5271 >> >> Time Awake Since Boot: 16000 seconds >> Time Since Wake: 12000 seconds >> >> System Integrity Protection: disabled >> >> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >> >> Exception Type: EXC_BAD_ACCESS (SIGSEGV) >> Exception Codes: KERN_INVALID_ADDRESS at 0xffffffffffffffff >> Exception Note: EXC_CORPSE_NOTIFY >> >> Termination Signal: Segmentation fault: 11 >> Termination Reason: Namespace SIGNAL, Code 0xb >> Terminating Process: exc handler [46230] >> >> The entire crash report is attached. Any idea what is going on here as it >> seems to be specific to python2.7? >> Jack >> >> >> <pymol_python27_crash.log>
