* thread #1: tid = 0x1f03, 0x00007fff5fc01028 dyld`_dyld_start, stop reason = execįrame #0: 0x00007fff5fc01028 dyld`_dyld_startīut at this point I'm lost as to what lldb commands to use in order to extract the parameters passed to the call. Process 15080 launched: '/opt/local/Library/Frameworks/amework/Versions/2.7/bin/python2.7' (x86_64) (lldb) r /opt/local/Library/Frameworks/amework/Versions/2.7/lib/python2.7/site-packages/pymol/_init_.py -d _ set stereo_double_pump_mono,quiet=1 -M WARNING: Unable to resolve breakpoint to any actual locations.
(lldb) b apple_visual_create_pfobj Breakpoint 1: no locations (pending). Lldb /opt/local/Library/Frameworks/amework/Versions/2.7/bin/python2.7Ĭurrent executable set to '/opt/local/Library/Frameworks/amework/Versions/2.7/bin/python2.7' (x86_64). Okay, removing the previous /Application/MacPorts python subdirectories, I am able to complete… This means that most likely something in macports got broken in the meanwhile. It looks like the issue only happens when PyMOL is built in the macports environment, and it's not related to any recent changes to PyMOL. I have then asked for assistance in the PyMOL mailing list, and Thomas Holder, a PyMOL developer from Schrodinger, confirmed
Gfxcardstatus 2.2.1 upgrade#
At a certain point I have probably upgraded the installed base (selfupdate + upgrade outdated), and now when I run pymol I get an error (log file attached) and then PyMOL crashes.
Up to a couple of days ago everything was working perfectly fine. Mavericks, installed through MacPorts, but the same happens with pymol
0 kommentar(er)
