Home/ Questions/Q 786247
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T21:00:40+00:00

I could resolve this problem just now but assuming others might have the same

  • 0

I could resolve this problem just now but assuming others might have the same problem, I post the “solution” here anyway.
When building a project in XCode using “Build and Debug” and then running it the iPhone simulator would exit without printing an error message to the console. Like for example I would access an invalid pointer and it would just terminate without printing Program received signal: “EXC_BAD_ACCESS”.

I used to use SDK 2.X and never experienced this and now I switched to 3.2 and this bug totally sucks.
Anyway. The “solution”, if you want to call it that, is to set a breakpoint on the line where you access your invalid pointer, open the debugger, step over it and in the next cycle step into it. After that press continue and then close the debugger and simulator.
Then running the project using the “Build and Debug” button on the “Debugger Console” was fixed, i.e. when the simulator crashes it now prints “EXC_BAD_ACCESS” just like it used to in SDK 2.X.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Xcode will “normally” continue on an untrapped exception and display the appropriate message in the Debugger Console. However, if you have set “Run->Stop on Objective-C Exceptions” it will first pause in gdb before displaying the message. I would imagine that you may have set this breakpoint at some time – there are a few related breakpoints you can set in .gdbinit that will have a similar effect.

    • 0