No more gdb in Xcode console when building for iPhone simulator

Question

I usually use backtrace gdb to debug my application, but lately I can no longer do this when testing on an iPhone simulator. The blue word gdb stops showing up on the console, and nothing happens when I type "bt" or "backtrace". I can still properly debug and debug on the device.

My version of Xcode is 3.2.3. Is there a way to manually activate gdb (more importantly, backtrace)?

Answer 1

As Jack points out, the Pause button will manually activate gdb and the backtrace that you asked. Perhaps you have a bad installation - sometimes it happens that you try to delete the / Developer folder and reinstall it. Xcode 3.2.3 and the debugger work fine, I use it several times a day.

In particular, CMD-Y is “build and run with a debugger,” while CMD-R simply “builds and runs” (the debugger does not work by default), so make sure you use CMD-Y.

In addition: the problem that I continue to work with after the application shuts down, the red stop icon does not recognize that the application is finished, so I have to “stop” it again. I believe that this is due to the fact that iOS-4 applications are running in the background.

Answer 2

If the program hangs, this is what it sounds. You can click the Pause button on the debugger console or in the Debugger window to interrupt the application and see where it runs.

Answer 3

Also check and make sure that the .gdbinit file of your home folder is in good condition. Set it aside if it exists, and see if the problem persists.

Answer 4

I don’t know if this is the same situation, but it can help. My iPhone was in firmware 4.0.2, but my Xcode SDK was for firmware 4.0.1. Usually Xcode complains that I will need to upgrade to a new Xcode that supports 4.0.2, this time it is not.

I hit my head about why breakpoints could be set, but the debugger did not stop at my breakpoint (the breakpoints were orange - signaling that the characters were not loaded). I decided to restart my iPhone, and now Xcode showed a warning (when it was not before). Switching to Xcode for 4.0.2, of course, fixed my problem. So, maybe your Xcode is not updated for a newer firmware?

Answer 5

Had a similar problem, but could not remember the exact circumstances. The disabled base SDK (on the tab for creating project information) was installed on the device, not on the simulator. A little shot in the dark, but probably worth checking out.