ansaurus

Question

iPhone Dev: XCode debugger does not stop on breakpoints

Answer 1

A:

Try running the project by hitting Command-Option-Y (this forces Xcode to start the program with the debugger).

The buttons on the menu bar of Xcode can be somewhat misleading. If the button says 'Run', it doesn't run the program in the debugger. If it says 'Go' it runs the program however it was last built (ie release or debug). Command-Option-Y starts the program specifically in the debugger.

Also, make sure your breakpoints are enabled. You can right click on them to check. Also, in the Debugger window, there should be an option on the toolbar for Activate or Deactivate Breakpoints. Make sure they're activated.

Grant Limberg 2009-03-02 04:28:28

I have cleaned and rebuilt multiple times and started with Command-Option-Y with no luck.

mjmarsh 2009-03-02 13:56:31

Answer 2

A:

cdespinosa 2009-03-02 05:42:14

What info page is this on? I don't remember seeing this on the Executable or Target settings, but I will look again.

mjmarsh 2009-03-02 12:59:39

argh, cannot find this setting anywhere under Target or Executable settings

mjmarsh 2009-03-02 13:55:40

Answer 3

+1 A:

In the XCode preferences go into the debugging section and turn off 'Load symbols lazily'.

That fixed it for me a few months ago when I first run into this problem.

oldbeamer 2009-03-02 23:27:39

He did that...as step #1

epatel 2009-03-02 23:54:17

Ah, sorry, missed that!

oldbeamer 2009-03-03 00:14:07

I had the same problem, and this fixed it for me. Thanks oldbeamer.

Elliot 2009-06-16 06:00:06

Answer 4

+10 A:

cdespinosa 2009-03-04 07:00:05

This is the most promising ting I've heard. I will double check the target's SDK settings tonight and then post back here (hopefully I can mark this one as answered by then)

mjmarsh 2009-03-04 19:10:32

I'm going to vote you up to counter the fact someone voted up my answer. while I guess my answer would be generally useful, the op explicitly said that it was not the case and I don't want to get even half a bounty I don't deserve.

toast 2009-03-05 18:24:58

edited original post. Will post back if I get any feedback from apple mailing list

mjmarsh 2009-03-07 03:31:38

Answer 5

A:

This may be an exceptionally obvious answer, but it could work. Have you tried adding breakpoints in code other than main() ? For instance, in the App Delegate's applicationDidFinishLaunching method? I know it SHOULD go through main first, but since that code in main is not normally modified for iPhone apps, it might be a bit flaky. It's worth a try, anyway.

Also, to find the GCC 4.0 - Code Generation options, click the triangle to open the Targets group, and click on your app's name underneath Targets. Click on the Info button up in the top of the Xcode window and you'll get the settings for your app. Go to Build. Make sure the Show: dropdown is set to All Settings. If you scroll down from there, it should be one of the lists you can edit (after Versioning and before GCC 4.0 - Language)

Bdebeez 2009-03-04 18:47:08

Yes, I've tried right inside the AppDelegate's startup code. Here's the thing. The app runs as I expect, so I know all the code is executed. It just doesn't hit breakpoints. cdespinosa's answer looks promising. Will post back tonight with a result.

mjmarsh 2009-03-04 19:11:56

Answer 6

+1 A:

Another simple suggestion:
Are the breakpoints light blue are dark blue?

XCode allows you to deactivate breakpoints and these are indicated with a light blue arrow (like it has been dimmed).

toast 2009-03-04 19:35:21

checked that already :) Dark blue all around.

mjmarsh 2009-03-04 20:01:00

That's cool, it's just something that had recently bitten me.

toast 2009-03-04 20:02:28

Answer 7

+1 A:

The GCC 4.0 - Code Generation section only shows up when you set the Active SDK to Device - iPhone OS 2.x. Go figure. They disappear when the Active SDK is the simulator.

You should change your Active SDK to Device, change the settings, and then change back to Simulator. The settings made under Device should also hold for Simulator. This also works with eg. setting a -DDEBUG flag for preprocessing.

(Update: I was only half right. See Chris Espinosa's accepted answer re: this SDK bug. It's not that the GCC 4.0 section shows up when the Active SDK is set to "Device," it's that your Base SDK and Active SDK must match up to access these settings).

Ryan McCuaig 2009-03-04 19:54:47

I'll try the Base/Active SDK changes tonight and post back here with results.

mjmarsh 2009-03-04 20:01:46

Answer 8

A:

When the program is running, can you do a CTRL-C in the Console window (while cursor is there). If you interrupt the program type info br which should give a list of the active breakpoints, question then is, are they what you set?

epatel 2009-03-07 20:47:52

(gdb) info brNum Type Disp Enb Address What1 breakpoint keep y 0x000028cf in main at /Projects/TestApp/main.m:13 --- it does not stop at this breakpoint. This is the first line in main()

mjmarsh 2009-03-07 21:58:36

Answer 9

A:

There are two gdb configuration files that can be good to have a look at.

/etc/gdb.conf

Mine have MD5 (/etc/gdb.conf) = 31b58e1ecf038554faadf777d63e9085

~/.gdbinit

I have no, do you have one?

epatel 2009-03-07 21:04:14

MD5 (gdb.conf) = 31b58e1ecf038554faadf777d63e9085:) - no .gdbinit

mjmarsh 2009-03-07 22:02:05

Answer 10

A:

Have you verified that your build configuration is using your development certificate for code signing?

If you are using an Ad Hoc certificate, it'll still build and run fine, but shortly after launching the app, Xcode will detach from the device so no breakpoints will ever hit. You can quickly tell whether it has detached or not if you look in the bottom left of the main Xcode window after you've clicked Build & Go - if you aren't using the actual development device certificate, you'll see a message that says something like "Invalid Hex Code Received from Device".

Adam Byram 2009-03-07 22:19:26

Answer 11

A:

I looks like you are running the program as root, that doesn't seem to be right...

epatel 2009-03-07 22:21:46

i got desperate and logged in as root. I'll try in a different account

mjmarsh 2009-03-07 22:24:17

tried it as a regular user, same result

mjmarsh 2009-03-07 22:35:07

what if you use the ctrl-c trick and add a new breakpoint, ie "br somefile.m:23" for a place in a button action? and "cont" try the button?

epatel 2009-03-07 22:41:46

Answer 12

+1 A:

This is sort of a "is it plugged in" answer, but hey, sometimes that is the problem: Are breakpoints enabled? Sometimes when I debug, I forget to click the button in the debugging toolbar that enables and disables breakpoints.

Kevin Conner 2009-03-10 02:59:49

Answer 13

A:

If you are using an Ad Hoc certificate, it'll still build and run fine, but shortly after launching the app, Xcode will detach from the device so no breakpoints will ever hit.

This helped me.

2009-07-25 21:57:51

Answer 14

A:

I have to ask, as I had the same problem, is this a 'real' mac? There is this exact problem with the voodoo hacintosh kernal. If you are using the voodoo kernal, boot with std_dyld=1 and all will be well

John Burch 2009-10-22 18:29:34

I've seen it on a real mac and a hackin0sh. Not sure of the distro on the latter. If this tip works I'll vote up your comment.

mjmarsh 2009-10-22 19:53:46

Answer 15

A:

This really works on voodoo kernel, booting with std_dyld=1 make xCode stop at breakpoint. Amazing tip, really. Many thanks to you John your a kind of life saver !!! I used OSX86Tools to add this boot flag automatically. Polo

pololebreton1 2009-10-26 10:41:14

Answer 16

A:

Apple should really improve the overall Xcode experience. I understand its free (hey, you get what you pay for), but still, the bugs in it is almost insulting to developers.

AlvinfromDiaspar 2010-09-23 09:01:47

This is not a helpful answer, but I completely agree. I'd gladly pay $500 for a better Cocoa development IDE, but nobody is going to make one of those. The fact that Xcode is free discourages others from producing anything better, so Apple has responsibilities beyond those of many "free" projects.

Kristopher Johnson 2010-09-23 13:45:54

ansaurus

tags:

views:

answers:

iPhone Dev: XCode debugger does not stop on breakpoints

related questions