Xcode launch project for debugging

Im uses Xcode 4.6.3 to create a library for OS X. My project includes a LibraryTest target, which is a command line application to test the functionality of the library. Both the library and the test application are built perfectly, but when I try to start the application, it immediately terminates, and the debug console shows:

 error: failed to launch '/Users/bdesham/Library/Developer/Xcode/DerivedData/Wavelength_and_Spectrum_Library-byosniusyaoidgdcpzwzuzkitzgv/Build/Products/Debug/LibraryTest' -- error: Host::LaunchProcess (launch_info) => pid=0, path='/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/debugserver' err = error: ::posix_spawnp ( pid => 98649, path = '/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/debugserver', file_actions = 0x10b09e268, attr = 0x10b09e2a0, argv = 0x7fe2701377e0, envp = 0x0 ) err = Bad file descriptor (0x00000009) (0x00000009) error: failed to launch '/Users/bdesham/Library/Developer/Xcode/DerivedData/Wavelength_and_Spectrum_Library-byosniusyaoidgdcpzwzuzkitzgv/Build/Products/Debug/LibraryTest' -- error: Host::LaunchProcess (launch_info) => pid=0, path='/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/debugserver' err = error: ::posix_spawnp ( pid => 98649, path = '/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/debugserver', file_actions = 0x10b09e268, attr = 0x10b09e2a0, argv = 0x7fe2701377e0, envp = 0x0 ) err = Bad file descriptor (0x00000009) (0x00000009) 

(A line break has been added for readability.) I have Xcode 5 DP installed, so I tried to uninstall Xcode 4 and reinstall it from the Mac App Store, but not the cube. Removing DerivedData did not help either. Any ideas?

+6
source share
3 answers

Rebooting my Mac seems to have fixed this.

+7
source

Check "Build Settings" → "Preparation Profile". It should be "none" or some preparation for Max OSX (if you are creating a store application). In my case, he mistakenly had an "iOS pre-training profile." This solved this problem for me.


Note. I found this by checking syslog ("cat -f / var / log / system.log" in the terminal and then running the application). He wrote a crash report in which "... the embedded provisioning profile is invalid: ..." among other lines. Checking the application container itself really showed the file "embedded.provisionprofile", which made me check the build settings for it.

+4
source

I solved this by updating iOS. I used the JailBreak version of iOS.

0
source

Source: https://habr.com/ru/post/949682/


All Articles