HP Sauce Posted October 10, 2013 Share Posted October 10, 2013 Might anyone be able to shed some light on this? I realize it is no longer supported but if anyone out there knows of what is broken, please let me know. Crashed Thread: 9 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000007b05379e VM Regions Near 0x7b05379e: __LINKEDIT 00000000495bb000-000000004961a000 [ 380K] r--/rwx SM=COW /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriver --> __TEXT 000000008fedb000-000000008ff0e000 [ 204K] r-x/rwx SM=COW /usr/lib/dyld Dyld Error Message: Symbol not found: _OTInitInetAddress Referenced from: /Applications/Vectorworks 2009/Vectorworks 2009.app/Contents/MacOS/Vectorworks Expected in: /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted October 10, 2013 Vectorworks, Inc Employee Share Posted October 10, 2013 That normally indicates a problem with the graphics device or service, but it may not matter. We couldn't even get Vectorworks 2009 running fully on all the test OS X 10.7 machines here. There were even more problems on OS X 10.8 and getting that error on 10.9 is no surprise, sadly. Apple has taken to changing a LOT of underlying components in their OS releases since 10.4, so backwards compatibility for unsupported versions of Vectorworks on the Mac side is nowhere near as constant as it is on the Windows side. Quote Link to comment
HP Sauce Posted October 10, 2013 Author Share Posted October 10, 2013 I was lucky; it had worked flawlessly up until 10.9. What a bugger. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.