Thanks for your thoughts and advice. I really thought that you might be onto something with stack overflow page - I tried all the suggestions, cleaned my project and tried again. Boom! Crash.
I then tried a completely new project and… No luck. Boom and crash again. Is no one else having this problem with Xcode 4.3.2 on Lion 10.7.3? Am I really the only one? This is consistently reproducible on both my Macs - a Mac Pro 4,1 with 12GB RAM and a MacBook Air 2010 with 4GB RAM. Sadly, I can't see how I can move forward with my project until this Xcode problem is fixed. Fingers crossed for a quick update or solution :-D On 14 Apr 2012, at 21:28, Evadne Wu wrote: > Is it only happening on this project or also for new projects? Works for me > on new project. > > Again, > http://stackoverflow.com/questions/6189879/xcode-4-crashes-when-opening-project > might help. > > This is not funny. > > On Apr 15, 2012, at 3:43 AM, Pascal Harris <45rpmli...@googlemail.com> wrote: > >> Easy enough - I just follow the instructions on >> http://stackoverflow.com/questions/5632477/where-is-the-expression-window-in-xcode-4 >> exactly, and Bang! On both my computers it results in an instant crash. >> Even before I start running my code. >> >> Process: Xcode [1313] >> Path: /Applications/Xcode.app/Contents/MacOS/Xcode >> Identifier: com.apple.dt.Xcode >> Version: 4.3.2 (1177) >> Build Info: IDEApplication-1177000000000000~6 >> App Item ID: 497799835 >> App External ID: 7171108 >> Code Type: X86-64 (Native) >> Parent Process: launchd [143] >> >> Date/Time: 2012-04-14 15:54:16.576 +0100 >> OS Version: Mac OS X 10.7.3 (11D50) >> Report Version: 9 >> >> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >> >> Exception Type: EXC_CRASH (SIGABRT) >> Exception Codes: 0x0000000000000000, 0x0000000000000000 >> >> Application Specific Information: >> ProductBuildVersion: 4E2002 >> ASSERTION FAILURE in >> /SourceCache/IDEDebugger/IDEDebugger-1185/PlugIns/DebuggerUI/VariablesView/DBGVariablesViewContentProvider.m:329 >> Details: Assertion failed: selectedRow >= 0 >> Object: <DBGVariablesViewContentProvider: 0x40227dfe0> >> Method: -addOrEditExpression: >> Thread: <NSThread: 0x40010a220>{name = (null), num = 1} >> Hints: None >> Backtrace: >> 0 0x000000010851db9f -[IDEAssertionHandler >> handleFailureInMethod:object:fileName:lineNumber:messageFormat:arguments:] >> (in IDEKit) >> >> >> Very odd. And very annoying. I mean, I guess that this does normally work >> - it's too high profile, and too dramatic, for Apple to have shipped code >> that does this for everyone, all of the time. But it's strange that it >> should happen on both my computers, of very different type, so consistently. >> >> >> On 14 Apr 2012, at 19:37, Evadne Wu wrote: >> >>> That’s too bad. Would you please post a minimal test case that crashes >>> Xcode? -ev >>> >>> On Apr 14, 2012, at 10:26 PM, Pascal Harris <45rpmli...@googlemail.com> >>> wrote: >> > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
