Currently Being ModeratedSep 8, 2012 2:28 AM (in response to luvelle)
Having exactly the same problem. I have tried most of the above solutions and and all the one listet at stackoveroflow, however nothing worked. I need help desperatly.
Currently Being ModeratedSep 10, 2012 8:06 PM (in response to bdorno)
Are you still having the error? I've formatted my computer (yet again) and it worked for awhile, but broke after a few runs. It's very frustrating. I'd like to know, what's the make of your MacBook? Is it the earlier white one?
Currently Being ModeratedSep 13, 2012 11:45 AM (in response to luvelle)
Yes, I still get the error. I am running xcode on the 2011 iMac i5, with mountain lion. However I works on my old 2006 white macbook running lion and xcode 4.3. Maybe it is something to do with using both versions of xcode on the same project. But I am only speculating. Where you able to fix it, somehow?
I hope the xcode update shipping with iOS 6 will help.
Currently Being ModeratedSep 20, 2012 11:40 PM (in response to bdorno)
Haven't been able to fix it.
But maybe the upgrade of Mountain Lion OS X and Xcode 4.5 will help! I'm formatting my computer again to try this out... *crossing fingers* Let me know how it goes for you
Currently Being ModeratedNov 28, 2012 6:49 PM (in response to luvelle)
I had exactly the same problem: when using any current version of Xcode 4.xx and the LLDB debugger, plus any version of the Simulator, Xcode consistently crashed with 'failed to attach to process ..'. My only resolution was to switch to the GDB debugger. This was disappointing since I really wanted to try the new, robust LLDB in XCode 4.6-DP.
And then I remembered; I had changed my network/server host file at ...etc/hosts some time ago to accomodate several Apache2 server virtual hosts, i.e., I removed the line:
That was it. Removing that line, Xcode crashed on attaching to the Simulator with LLDB.
Restoring that line, XCode worked just fine with LLDB and the Simulator.
Anyway, this may not be your problem but it's worth exploring. As far as I'm concerned, it's a serious undocumented bug.
Currently Being ModeratedNov 28, 2012 7:28 PM (in response to Michael Superczynski)
No bug report yet. I was waiting for it to be confirmed by at least one other developer.
Currently Being ModeratedJan 3, 2013 3:00 AM (in response to HLBControls)
Hi, I had the same problem and after I checked the hosts file and wrote the "127.0.0.1 localhost" line in it then everything become fine. Thanks!
Currently Being ModeratedJan 19, 2013 3:47 AM (in response to HLBControls)
Man, You saved my life!!! Thank You, I appreciate you contribution to the discussion!
Currently Being ModeratedJul 12, 2013 11:27 AM (in response to luvelle)
@HLBControls that worked for me like a charm! thanks, I dealt with that same issue for a while now It works on my macbook air!