osx-mountain-lion

LaunchD Plist not working

人盡茶涼 提交于 2019-12-08 01:11:57
问题 EDIT: It appears as if I am getting an error in the console com.apple.launchd: (com.xxxx.adbind[57]) Exited with code: 1 What does that even mean? Also; if I load the launchd plist file logged in by using the launchctl command it works fine! I'm driving myself crazy trying to figure out why my launchd is not working. I'm using this in Mountain Lion 10.8.2 When I manually start it using launchctl it says it's loaded, but the script is not running. The script when ran manually works fine as

NSOpenPanel crashes when debugging with Xcode 4.5.1

孤人 提交于 2019-12-07 18:50:15
问题 I have a document-based application. Since upgrading to XCode 4.5.1 (from 4.4) NSOpenPanel crashes when I debug the application from Xcode. It does not crash when I start the program directly. I use NSOpenPanel on two occasions: When the user selects "Open" from the "File" menu (since it is a document-based application, none of my own code is involved) and for importing some data into my document (so it gets called by my own code). NSOpenPanel crashes on both occasions (the dialog opens, but

Matlab 2012a Mex to work with Xcode 4.5 on Mountain Lion

六月ゝ 毕业季﹏ 提交于 2019-12-07 08:55:09
问题 I have Mountain Lion installed with Xcode 4.5 and Matlab 2012a. I installed and ran the patch supplied on the MathWorks website however I still received the following error: /Applications/MATLAB_R2012a.app/bin/mex: line 305: llvm-gcc-4.2: command not found /Applications/MATLAB_R2012a.app/bin/mex: line 1326: llvm-gcc-4.2: command not found mex: compile of ' "hello.c"' failed. Error using mex (line 206) Is there a known solution for that ? Solution: Open Xcode --> Preferences --> Downloads -->

OSX preferences file - removePersistentDomainForName has different functionality in 10.8?

倾然丶 夕夏残阳落幕 提交于 2019-12-07 07:48:27
This code works for one of our developers on 10.7 but not for me on 10.8 working = it deletes the preferences .plist file for the bundle. The dev on 10.7 also has a lockfile whereas I do not. It's not a problem of file access - I tried [resetStandardUserDefault] and that made a new file, but that's not exactly we want to do. NSString *appDomain = [[NSBundle mainBundle] bundleIdentifier]; [[NSUserDefaults standardUserDefaults] removePersistentDomainForName:appDomain]; I am having trouble locating any info about changes in 10.8 - does this sound familiar to anyone? I have the same issue and

How do I build PIL on OS X Mountain Lion?

跟風遠走 提交于 2019-12-06 21:34:27
When I try to build PIL on Mac OS X 10.8.1 Mountain Lion, I get the following result: $ sudo python setup.py install Password: running install running build running build_py running build_ext --- using frameworks at /System/Library/Frameworks building '_imaging' extension clang -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -pipe -DHAVE_LIBJPEG -DHAVE_LIBZ -IlibImaging -I

Crash of Garbage Collection Work Queue if dylib is loaded

时光怂恿深爱的人放手 提交于 2019-12-06 19:01:28
问题 We are porting an app from 10.6 to 10.8. I am looking at dylib we load in app. I am facing very unusual crash in Garbage Collection Work Queue with following message. malloc: Thread::suspend(): unable to suspend a thread: err = 268435459, Thread 0x111000000: _pthread = 0x108129000, _thread = 0x8b07, _stack_base = 0x108129000, enlivening on, 0 local blocks For application GCC_ENABLE_OBJC_GC = required is set. If I have GCC_ENABLE_OBJC_GC = required in dylib it will still crash. I cannot turn

Network Link Conditioner seems to have no effect on network behavior on Lion, Mountain Lion

我与影子孤独终老i 提交于 2019-12-06 17:02:34
问题 The Network Link Conditioner preference pane (installed from the "Hardware IO Tools for Xcode - Late July 2012" DMG on the Apple developer site) doesn't appear to have any effect when turned on. The original author of this question reported the symptoms on Mountain Lion. A later editor experienced the same symptoms and lack of expected network behavior change on Lion, with Xcode 4.5.1 installed. When enabled, /var/log/system.log shows: Jan 17 17:36:14 matt-mmf-macbook [0x0-0x1d01d].com.apple

phpize reports “Cannot find config.m4”

孤者浪人 提交于 2019-12-06 16:32:53
问题 I am trying to run the 'phpize' command on MacOSx Mountain Lion, but this is what I get: Cannot find config.m4. Make sure that you run '/opt/local/bin/phpize' in the top level source directory of the module How do I resolve this error ? 回答1: The phpize command is meant to be run at the top level of an extension source dir (this source dir should contain a file name config.m4). See http://php.net/manual/en/install.pecl.phpize.php for more information. 回答2: In plain English, it means you're

Running wxPython 2.9 on OS X 10.8 (64 bit)

寵の児 提交于 2019-12-06 16:10:10
I have EPD 7.3 and have installed wxPython 2.9 through the Enthought repositories. I tried running winPDB, which requires wxPython and I got this message : This program needs access to the screen. Please run with a Framework build of python, and only when you are logged in on the main display of your Mac. I have seen similar messages from wxPython on Mac, but I haven't found a solution yet. Does anyone know about this message? And, has anyone got WinPDB to work on OS X 10.8 w/ wxPython 2.9? This error message will happen when the Python used to run a wxPython script is not a full framework

CIImage drawing EXC_BAD_ACCESS

北城以北 提交于 2019-12-06 13:42:45
So, I have a CIImage that I'm attempting to draw in an NSView 's -drawRect method. This is the line of code that I call to draw the image: [outputCoreImage drawInRect: [self bounds] fromRect: originalBounds operation: NSCompositeSourceOver fraction: 1]; outputCoreImage , originalBounds , and [self bounds] are all non- nil , and indeed are their respective expected values. On Lion (OS X 10.7), this worked fine, however on Mountain Lion (OS X 10.8) I receive an EXC_BAD_ACCESS on this line. If I walk up the stack, I find that the internal function call that breaks is on CGLGetPixelFormat . frame