Why aren t Xcode breakpoints functioning

Question

I have breakpoints set but Xcode appears to ignore them

User · Answer

if you using Xcode Version 11 1  11A1027  make sure you are not using the app store credential provisioning profiles    because in this case  build will be installed and no log or debugger will work  it took me hell lot of time to figure it out   updated Xcode has chagned   now build getting installed on the device without any warning

User · Answer

It has happened the same thing to me in XCode 6 3 1   I managed to fix it by    Going to View- Navigators- Show Debug Navigators Right click in the project root -  Move Breakpoints  If selected the User option   I also Selected the option share breakpoints  even though I m not sure if that necessary     After doing that change I set the Move breakpoints options back to the project  and unselecting the Share breakpoints option  and still works    I don t exactly know why but this get my breakpoints back

User · Answer

Also make sure that the AppStore distribution of the app is not also installed on the device

User · Answer

Go to the Xcode Debugging preferences  Make sure that  Load Symbols lazily  is NOT selected

User · Answer

I have Xcode 3 2 3 SDK 4 1 Breakpoints will fail at random  I have found if you clean the build and use the touch command under build they work again

User · Answer

I was facing the same problem when I wanted to debug a web plug-in where the custom executable was Safari 5 1  It was working fine till upgraded my Safari to 5 1 from 4 0 5  Once I installed Safari 4 0 5 again  all breakpoints started working without modifying any Xcode setting

User · Answer

if you using Xcode Version 11 1  11A1027  make sure you are not using the app store credential provisioning profiles    because in this case  build will be installed and no log or debugger will work  it took me hell lot of time to figure it out   updated Xcode has chagned   now build getting installed on the device without any warning

User · Answer

Another reason the breakpoints can turn yellow is if the application binary you are debugging has been modified since it was first run  In my case  I added a folder to the application s Contents Resources folder after having debugged the program once  On the debug run after adding the folder  the breakpoints turned yellow and were ignored  I modified my procedure  I did a clean  a build  added the folder  then ran  and all was well   Perhaps Xcode  or OS X  creates and remembers its own digital signature of the application  which was not digitally signed  and then  sensing that the application was modified  refuses to try to set breakpoints  By making my mods before the first  debug  run of the application  the digital signature was made with my mods   All this on OS X 10 6 8 using Xcode 3 2 2

User · Answer

When setting your break point  right click and you should get several options about how the break point is handled  log vars and continue  pause execution  etc   Also make sure the  Load Symbols lazily  is not selected in the debug preferences    Applies to Xcode 3 1  not sure about past future versions

User · Answer

I tried all the above things but for me only deactivating the debugging breakpoints once and then activating them worked

User · Answer

For Xcode 4 x     Goto Product Debug Workflow and uncheck  Show Disassembly When Debugging    For Xcode 5 x    Goto Debug Debug Workflow and uncheck  Show Disassembly When Debugging

User · Answer

There appears to be 3 states for the breakpoints in Xcode  If you click on them they ll go through the different settings  Dark blue is enabled  grayed out is disabled and I ve seen a pale blue sometimes that required me to click on the breakpoint again to get it to go to the dark blue color   Other than this make sure that you re launching it with the debug command not the run command   You can do that by either hitting option   command   return  or the Go  debug  option from the run menu

User · Answer

I have a lot of problems with breakpoints in Xcode  2 4 1   I use a project that just contains other projects  like a Solution in Visual Studio   I find sometimes that breakpoints don t work at all unless there is at least one breakpoint set in the starting project  i e  the one containing the entry point for my code   If the only breakpoints are in  lower level  projects  they just get ignored   It also seems as if Xcode only handles breakpoint operations correctly if you act on the breakpoint when you re in the project that contains the source line the breakpoint s on     If I try deleting or disabling breakpoints via another project  the action sometimes doesn t take effect  even though the debugger indicates that it has  So I will find myself breaking on disabled breakpoints  or on a  now invisible  breakpoint that I removed earlier

User · Answer

Another reason the breakpoints can turn yellow is if the application binary you are debugging has been modified since it was first run  In my case  I added a folder to the application s Contents Resources folder after having debugged the program once  On the debug run after adding the folder  the breakpoints turned yellow and were ignored  I modified my procedure  I did a clean  a build  added the folder  then ran  and all was well   Perhaps Xcode  or OS X  creates and remembers its own digital signature of the application  which was not digitally signed  and then  sensing that the application was modified  refuses to try to set breakpoints  By making my mods before the first  debug  run of the application  the digital signature was made with my mods   All this on OS X 10 6 8 using Xcode 3 2 2

User · Answer

I ve had my breakpoints not work and then done Build   Clean All Targets to get them working again

User · Answer

In case of Xcode 4 and later  Load symbols lazily  is seems to be dropped  So refer this post click here  Simple and detailed explanation worked for me

User · Answer

Thing to try     1   restart xcode 2   select another simulator -- which was my case 3   reboot mac   if none of this works  then look at the project settings    which is leeast possible thing

User · Answer

I have Xcode Version 4 6 3 and Breakpoints were never working in sub-groups of included projects  The project would compile and run fine  it would even attach to the debugger and spit out NSLog output appropriately   The issue was related to my Header Search Paths  I had some of them set  recursive  instead of the default  non-recursive   Changing them all to  non-recursive  and updating all of the related imports appropriately fixed the problem

User · Answer

Having both Xcode 5 and 6 GM caused the former to lose breakpoint functionality  Xcode 6 betas were ok    I tried many of the suggested methods but finally gave up and I m just using Xcode 6 now

User · Answer

First of all  I agree 100  with the earlier folks that said turn OFF Load Symbols Lazily   I have two more things to add    My first suggestion sounds obvious  but the first time someone suggested it to me  my reaction went along these lines   come on  please  you really think I wouldn t know better        oh      Make sure you haven t accidentally set  Active Build Configuration  to  Release   Under  Targets  in the graphical tree display of your project  right click on your Target and do  Get Info    Look for a property named  Generate Debug Symbols   or similar  and make sure this is CHECKED  aka ON    Also  you might try finding  also in Target    Get Info  a property called  Debug Information Format  and setting it to  Dwarf with dsym file     There are a number of other properties under Target    Get Info that might affect you   Look for things like optimizing or compressing code and turn that stuff OFF  I assume you are working in a debug mode  so that this is not bad advice    Also  look for things like stripping symbols and make sure that is also OFF  For example   Strip Linked Product  should be set to  No  for the Debug target

User · Answer

For Xcode 4      go Product - gt  Debug - gt   Activate Breakpoints

User · Answer

First of all  I agree 100  with the earlier folks that said turn OFF Load Symbols Lazily   I have two more things to add    My first suggestion sounds obvious  but the first time someone suggested it to me  my reaction went along these lines   come on  please  you really think I wouldn t know better        oh      Make sure you haven t accidentally set  Active Build Configuration  to  Release   Under  Targets  in the graphical tree display of your project  right click on your Target and do  Get Info    Look for a property named  Generate Debug Symbols   or similar  and make sure this is CHECKED  aka ON    Also  you might try finding  also in Target    Get Info  a property called  Debug Information Format  and setting it to  Dwarf with dsym file     There are a number of other properties under Target    Get Info that might affect you   Look for things like optimizing or compressing code and turn that stuff OFF  I assume you are working in a debug mode  so that this is not bad advice    Also  look for things like stripping symbols and make sure that is also OFF  For example   Strip Linked Product  should be set to  No  for the Debug target

User · Answer

I was facing the same problem when I wanted to debug a web plug-in where the custom executable was Safari 5 1  It was working fine till upgraded my Safari to 5 1 from 4 0 5  Once I installed Safari 4 0 5 again  all breakpoints started working without modifying any Xcode setting

User · Answer

First of all  I agree 100  with the earlier folks that said turn OFF Load Symbols Lazily   I have two more things to add    My first suggestion sounds obvious  but the first time someone suggested it to me  my reaction went along these lines   come on  please  you really think I wouldn t know better        oh      Make sure you haven t accidentally set  Active Build Configuration  to  Release   Under  Targets  in the graphical tree display of your project  right click on your Target and do  Get Info    Look for a property named  Generate Debug Symbols   or similar  and make sure this is CHECKED  aka ON    Also  you might try finding  also in Target    Get Info  a property called  Debug Information Format  and setting it to  Dwarf with dsym file     There are a number of other properties under Target    Get Info that might affect you   Look for things like optimizing or compressing code and turn that stuff OFF  I assume you are working in a debug mode  so that this is not bad advice    Also  look for things like stripping symbols and make sure that is also OFF  For example   Strip Linked Product  should be set to  No  for the Debug target

User · Answer

In Xcode 4  - Product menu  gt  Manage Schemes - Select the scheme thats having debugging problems  if only one choose that  - Click Edit button at bottom - Edit Scheme dialog appears - in left panel click on Run APPNAME app - on Right hand panel make sure youre on INFO tab - look for drop down DEBUGGER  - someone had set this to None - set to LLDB if this is your preferred debugger - can also change BUILD CONFIGURATION drop down to Debug  -      but I have other targets set to AdHoc which debug fine once Debugger is set

User · Answer

What solved it in my case was quite simple  in Xcode - Product - Clean Build Folder followed by Product - Run  not the Play Xcode button      Had the issue on Xcode 11 -beta 4 after switching to unit testing with Xcode play button long press

User · Answer

I have a lot of problems with breakpoints in Xcode  2 4 1   I use a project that just contains other projects  like a Solution in Visual Studio   I find sometimes that breakpoints don t work at all unless there is at least one breakpoint set in the starting project  i e  the one containing the entry point for my code   If the only breakpoints are in  lower level  projects  they just get ignored   It also seems as if Xcode only handles breakpoint operations correctly if you act on the breakpoint when you re in the project that contains the source line the breakpoint s on     If I try deleting or disabling breakpoints via another project  the action sometimes doesn t take effect  even though the debugger indicates that it has  So I will find myself breaking on disabled breakpoints  or on a  now invisible  breakpoint that I removed earlier

User · Answer

I tried all the above things but for me only deactivating the debugging breakpoints once and then activating them worked

User · Answer

If all else fails  instead of a breakpoint  you can call the following function   void BreakPoint void        int i 1       if    OPTIMIZE       printf  Code is waiting  hit pause to see  n        while i        endif     To resume  manually set i to zero  then hit the resume button

User · Answer

I found the problem  Somehow the  Show Disassembly when debugging  was enabled in my XCode which creates that problem  When I disabled it  all my debugger stopped in my source code   You can find it under  Product- gt Debug Workflow- gt Show Disassembly when debugging

User · Answer

Having both Xcode 5 and 6 GM caused the former to lose breakpoint functionality  Xcode 6 betas were ok    I tried many of the suggested methods but finally gave up and I m just using Xcode 6 now

User · Answer

I think the problem could be incompatibility between device versions and Xcode  I have this problem when attempting to debug on my iPhone 4S running iOS 5 0 1  I am still using Xcode 3 2 5  I got the symbols from the handset by selecting  use this device for development  in the Organiser window  This phone refuses to breakpoint however  My old 3GS will breakpoint  same Xcode project  same settings    just different device and it s running iOS 4 0  I guess this is an Xcode bug in 3 2 5  since I have the symbols  Having tried all the solutions posted here so far  I have decided the solution to my problem is to go ahead and upgrade to XCode 4  Perhaps you cannot debug effectively unless your base SDK is at least as high as the system on which to debug  Maybe that s obvious - can anyone confirm   Edit  I will update when I can confirm this is true

User · Answer

One of the possible solutions for this could be     go to Product Scheme Edit scheme   Under Run info Executable  check  Debug executable

User · Answer

Go to the Xcode Debugging preferences  Make sure that  Load Symbols lazily  is NOT selected

User · Answer

In case of Xcode 4 and later  Load symbols lazily  is seems to be dropped  So refer this post click here  Simple and detailed explanation worked for me

User · Answer

First of all  I agree 100  with the earlier folks that said turn OFF Load Symbols Lazily   I have two more things to add    My first suggestion sounds obvious  but the first time someone suggested it to me  my reaction went along these lines   come on  please  you really think I wouldn t know better        oh      Make sure you haven t accidentally set  Active Build Configuration  to  Release   Under  Targets  in the graphical tree display of your project  right click on your Target and do  Get Info    Look for a property named  Generate Debug Symbols   or similar  and make sure this is CHECKED  aka ON    Also  you might try finding  also in Target    Get Info  a property called  Debug Information Format  and setting it to  Dwarf with dsym file     There are a number of other properties under Target    Get Info that might affect you   Look for things like optimizing or compressing code and turn that stuff OFF  I assume you are working in a debug mode  so that this is not bad advice    Also  look for things like stripping symbols and make sure that is also OFF  For example   Strip Linked Product  should be set to  No  for the Debug target

User · Answer

In Xcode 7  what worked for me was   Make sure that the Target  gt  Scheme  gt  Run - is in Debug mode  was Release   Make sure to check the option  quot Debug executable quot

User · Answer

Solution for me with XCode 9 4 1  did not stop at any breakpoint    Under build Target -  Build Settings -  Optimization Level  Switched from  Optimize for speed  -   No optimization   now it s slower but works

User · Answer

If you are using subversion  just revert your project files  only  to the last time you knew the debugger was working

User · Answer

You can Activate   Disactivate Breakpoints in dropdown menu

User · Answer

This happens from time to time with an iOS project at least  To fix it  I had to reboot the iOS device  quit Xcode  and rebuild the project

User · Answer

There appears to be 3 states for the breakpoints in Xcode  If you click on them they ll go through the different settings  Dark blue is enabled  grayed out is disabled and I ve seen a pale blue sometimes that required me to click on the breakpoint again to get it to go to the dark blue color   Other than this make sure that you re launching it with the debug command not the run command   You can do that by either hitting option   command   return  or the Go  debug  option from the run menu

User · Answer

When setting your break point  right click and you should get several options about how the break point is handled  log vars and continue  pause execution  etc   Also make sure the  Load Symbols lazily  is not selected in the debug preferences    Applies to Xcode 3 1  not sure about past future versions

User · Answer

I ve had problems with Xcode losing breakpoints when using the simulator and having the Scheme Launch setting to  wait for executable   Change that to  launch automatically  and breakpoints come back to life

User · Answer

I believe that a project can also become corrupted in regards to breakpoints   I have a project  for example  that  WILL NOT break on any breakpoints that it remembers from the previous session   I first wrote about this here

User · Answer

See this post  Breakpoints not working in Xcode   You might be pushing  Run  instead of  Debug  in which case your program is not running with the help of gdb  in which case you cannot expect breakpoints to work

User · Answer

I have a lot of problems with breakpoints in Xcode  2 4 1   I use a project that just contains other projects  like a Solution in Visual Studio   I find sometimes that breakpoints don t work at all unless there is at least one breakpoint set in the starting project  i e  the one containing the entry point for my code   If the only breakpoints are in  lower level  projects  they just get ignored   It also seems as if Xcode only handles breakpoint operations correctly if you act on the breakpoint when you re in the project that contains the source line the breakpoint s on     If I try deleting or disabling breakpoints via another project  the action sometimes doesn t take effect  even though the debugger indicates that it has  So I will find myself breaking on disabled breakpoints  or on a  now invisible  breakpoint that I removed earlier

User · Answer

I have started to get this issue when updated my xCode into Version 11 0  11A420a   To solved that I have installed additional simulator version 12 2 and updated my iPhone version into 13 1  Now both on iOs simulator and on my device break points get hit

User · Answer

In Xcode 7  what worked for me was   Make sure that the Target  gt  Scheme  gt  Run - is in Debug mode  was Release   Make sure to check the option  quot Debug executable quot

User · Answer

I haven t done Xcode in a bit  but I recommend that you disable  Zerolink  and  Load Symbols Lazily   that will fix most problems  Zerolink is an abomination anyway

User · Answer

In my case i was overriding the existing app store build with my build I removed the same and its working now

User · Answer

When setting your break point  right click and you should get several options about how the break point is handled  log vars and continue  pause execution  etc   Also make sure the  Load Symbols lazily  is not selected in the debug preferences    Applies to Xcode 3 1  not sure about past future versions

User · Answer

In my case  I found out that the breakpoints have been accidentally deactivated  You can reactivate it again via Debug- Activate Breakpoints  Cmd Y   If you notice grey ed out breakpoint markers instead of the usual blue marker  this is likely the case    As it turned out you can always toggle breakpoints activation with Cmd Y keys  you might have hits this combination key not noticing it  This report is based on Xcode 7 2

User · Answer

One of the possible solutions for this could be     go to Product Scheme Edit scheme   Under Run info Executable  check  Debug executable

User · Answer

There appears to be 3 states for the breakpoints in Xcode  If you click on them they ll go through the different settings  Dark blue is enabled  grayed out is disabled and I ve seen a pale blue sometimes that required me to click on the breakpoint again to get it to go to the dark blue color   Other than this make sure that you re launching it with the debug command not the run command   You can do that by either hitting option   command   return  or the Go  debug  option from the run menu

User · Answer

If you tried all basic checks  check for for Optimization Level in project target and project settings  make sure you selected None for debug

User · Answer

Solution for me with XCode 9 4 1  did not stop at any breakpoint    Under build Target -  Build Settings -  Optimization Level  Switched from  Optimize for speed  -   No optimization   now it s slower but works

User · Answer

Go to the Xcode Debugging preferences  Make sure that  Load Symbols lazily  is NOT selected

User · Answer

In my case i was overriding the existing app store build with my build I removed the same and its working now

User · Answer

On Xcode 6 4  I needed to reboot my Mac     Tried enabling disabling breakpoints  rebooting iOS device  restarting Xcode  deleting breakpoint files from the workspace package

User · Answer

If you tried all basic checks  check for for Optimization Level in project target and project settings  make sure you selected None for debug

User · Answer

I haven t done Xcode in a bit  but I recommend that you disable  Zerolink  and  Load Symbols Lazily   that will fix most problems  Zerolink is an abomination anyway

User · Answer

See this post  Breakpoints not working in Xcode   You might be pushing  Run  instead of  Debug  in which case your program is not running with the help of gdb  in which case you cannot expect breakpoints to work

User · Answer

Also make sure that the AppStore distribution of the app is not also installed on the device

User · Answer

You can check one setting in target setting Apple LLVM Compiler 4 1 Code Generation Section Generate Debug Symbol   YES

User · Answer

You can Activate   Disactivate Breakpoints in dropdown menu

User · Answer

I have a lot of problems with breakpoints in Xcode  2 4 1   I use a project that just contains other projects  like a Solution in Visual Studio   I find sometimes that breakpoints don t work at all unless there is at least one breakpoint set in the starting project  i e  the one containing the entry point for my code   If the only breakpoints are in  lower level  projects  they just get ignored   It also seems as if Xcode only handles breakpoint operations correctly if you act on the breakpoint when you re in the project that contains the source line the breakpoint s on     If I try deleting or disabling breakpoints via another project  the action sometimes doesn t take effect  even though the debugger indicates that it has  So I will find myself breaking on disabled breakpoints  or on a  now invisible  breakpoint that I removed earlier

User · Answer

I ve had my breakpoints not work and then done Build   Clean All Targets to get them working again

User · Answer

I believe that a project can also become corrupted in regards to breakpoints   I have a project  for example  that  WILL NOT break on any breakpoints that it remembers from the previous session   I first wrote about this here

User · Answer

Just solved this in XCode 4 2  none of above helped  The thing was  I m not sure what actually happened  but  maybe this helps someone   my teammate created new build configurations and updated project in SVN  I had old build configuration set up in Run Scheme settings  so the steps for me were    Product -  Edit Scheme    Select  Run  project name app    or whatever causes problem  In build configuration combo select that new build configuration from my teammate   And that s all  breakpoints are back again  Hope this helps

User · Answer

I haven t done Xcode in a bit  but I recommend that you disable  Zerolink  and  Load Symbols Lazily   that will fix most problems  Zerolink is an abomination anyway

User · Answer

Here s an obscure one I ve run into  if you re working on a shared library  or a plugin   your breakpoints will go yellow on startup  which might cause you to hammer your keyboard in frustration and kill the debug process  Well  don t do that  The symbols won t get loaded until the app loads the library  at which point the breakpoints will become valid  I ran into this problem with a browser plugin    BPs were disabled until I browsed to a page that instantiated my plugin

User · Answer

What solved it in my case was quite simple  in Xcode - Product - Clean Build Folder followed by Product - Run  not the Play Xcode button      Had the issue on Xcode 11 -beta 4 after switching to unit testing with Xcode play button long press

User · Answer

Deleting my Build folder solved the problem for me

User · Answer

Came to this page with the same problem  C code in Xcode 6 not stopping at breakpoints  and none of the solutions above worked  the project was practically out of the box  settings-wise  so little chance for any of the debugger settings to be set to the wrong value      After wasting quite some time reducing the problem  I finally figured out the culprit  for my code    Xcode   LLVM  does not like Bison-style  line preprocessor commands   Removing them fixed the problem  debugger stopped at my breakpoints

User · Answer

Another reason  Set DeploymentPostprocessing to NO in BuildSettings - details here  In short -      Activating this setting indicates that binaries should be stripped and   file mode  owner  and group information should be set to standard   values   DEPLOYMENT POSTPROCESSING

User · Answer

Another thing to check is that if you have an  Entitlements  plist file for your debug mode  possibly because you re doing stuff with the Keychain   make sure that plist file has the  get-task-allow    YES row   Without it  debugging and logging will be broken

User · Answer

I have Xcode Version 4 6 3 and Breakpoints were never working in sub-groups of included projects  The project would compile and run fine  it would even attach to the debugger and spit out NSLog output appropriately   The issue was related to my Header Search Paths  I had some of them set  recursive  instead of the default  non-recursive   Changing them all to  non-recursive  and updating all of the related imports appropriately fixed the problem

User · Answer

In Xcode 4  - Product menu  gt  Manage Schemes - Select the scheme thats having debugging problems  if only one choose that  - Click Edit button at bottom - Edit Scheme dialog appears - in left panel click on Run APPNAME app - on Right hand panel make sure youre on INFO tab - look for drop down DEBUGGER  - someone had set this to None - set to LLDB if this is your preferred debugger - can also change BUILD CONFIGURATION drop down to Debug  -      but I have other targets set to AdHoc which debug fine once Debugger is set

User · Answer

I have started to get this issue when updated my xCode into Version 11 0  11A420a   To solved that I have installed additional simulator version 12 2 and updated my iPhone version into 13 1  Now both on iOs simulator and on my device break points get hit

User · Answer

There appears to be 3 states for the breakpoints in Xcode  If you click on them they ll go through the different settings  Dark blue is enabled  grayed out is disabled and I ve seen a pale blue sometimes that required me to click on the breakpoint again to get it to go to the dark blue color   Other than this make sure that you re launching it with the debug command not the run command   You can do that by either hitting option   command   return  or the Go  debug  option from the run menu

User · Answer

I was just having this same issue  again   After triple-checking  Load symbols lazily  and stripping and debug info generation flags  I did the following    quit Xcode open a terminal window and cd to the project directory cd into the  xcodeproj directory delete everything except the  pbxproj file  I had frank mode1v3 and frank pbxuser    You can accomplish the same task in finder by right option-clicking on the  xcodeproj bundle and picking  Show Package Contents    When I restarted Xcode  all of my windows had reset to default positions  etc  but breakpoints worked

User · Answer

Just solved this in XCode 4 2  none of above helped  The thing was  I m not sure what actually happened  but  maybe this helps someone   my teammate created new build configurations and updated project in SVN  I had old build configuration set up in Run Scheme settings  so the steps for me were    Product -  Edit Scheme    Select  Run  project name app    or whatever causes problem  In build configuration combo select that new build configuration from my teammate   And that s all  breakpoints are back again  Hope this helps

User · Answer

Another thing to check is that if you have an  Entitlements  plist file for your debug mode  possibly because you re doing stuff with the Keychain   make sure that plist file has the  get-task-allow    YES row   Without it  debugging and logging will be broken

User · Answer

I believe that a project can also become corrupted in regards to breakpoints   I have a project  for example  that  WILL NOT break on any breakpoints that it remembers from the previous session   I first wrote about this here

User · Answer

I haven t done Xcode in a bit  but I recommend that you disable  Zerolink  and  Load Symbols Lazily   that will fix most problems  Zerolink is an abomination anyway

User · Answer

I was just having this same issue  again   After triple-checking  Load symbols lazily  and stripping and debug info generation flags  I did the following    quit Xcode open a terminal window and cd to the project directory cd into the  xcodeproj directory delete everything except the  pbxproj file  I had frank mode1v3 and frank pbxuser    You can accomplish the same task in finder by right option-clicking on the  xcodeproj bundle and picking  Show Package Contents    When I restarted Xcode  all of my windows had reset to default positions  etc  but breakpoints worked

User · Answer

For Xcode 4      go Product - gt  Debug - gt   Activate Breakpoints

User · Answer

I found the problem  Somehow the  Show Disassembly when debugging  was enabled in my XCode which creates that problem  When I disabled it  all my debugger stopped in my source code   You can find it under  Product- gt Debug Workflow- gt Show Disassembly when debugging

User · Answer

On Xcode 6 4  I needed to reboot my Mac     Tried enabling disabling breakpoints  rebooting iOS device  restarting Xcode  deleting breakpoint files from the workspace package

User · Answer

It has happened the same thing to me in XCode 6 3 1   I managed to fix it by    Going to View- Navigators- Show Debug Navigators Right click in the project root -  Move Breakpoints  If selected the User option   I also Selected the option share breakpoints  even though I m not sure if that necessary     After doing that change I set the Move breakpoints options back to the project  and unselecting the Share breakpoints option  and still works    I don t exactly know why but this get my breakpoints back

User · Answer

In my case  I found out that the breakpoints have been accidentally deactivated  You can reactivate it again via Debug- Activate Breakpoints  Cmd Y   If you notice grey ed out breakpoint markers instead of the usual blue marker  this is likely the case    As it turned out you can always toggle breakpoints activation with Cmd Y keys  you might have hits this combination key not noticing it  This report is based on Xcode 7 2

User · Answer

For this  and also for  Xcode 6 and above make sure that the breakpoint state button is activated  the blue arrow-like button

User · Answer

This had me in Xcode 9 for half a frustrating day  It ended up been a simple debug setting   Go Debug   Debug Workflow and make sure  Always Show Disassembly  is turned off  Simple as that

User · Answer

Deleting my Build folder solved the problem for me

User · Answer

You can check one setting in target setting Apple LLVM Compiler 4 1 Code Generation Section Generate Debug Symbol   YES

User · Answer

I believe that a project can also become corrupted in regards to breakpoints   I have a project  for example  that  WILL NOT break on any breakpoints that it remembers from the previous session   I first wrote about this here

User · Answer

When setting your break point  right click and you should get several options about how the break point is handled  log vars and continue  pause execution  etc   Also make sure the  Load Symbols lazily  is not selected in the debug preferences    Applies to Xcode 3 1  not sure about past future versions

User · Answer

For this  and also for  Xcode 6 and above make sure that the breakpoint state button is activated  the blue arrow-like button

User · Answer

I ve had problems with Xcode losing breakpoints when using the simulator and having the Scheme Launch setting to  wait for executable   Change that to  launch automatically  and breakpoints come back to life

User · Answer

Another reason  Set DeploymentPostprocessing to NO in BuildSettings - details here  In short -      Activating this setting indicates that binaries should be stripped and   file mode  owner  and group information should be set to standard   values   DEPLOYMENT POSTPROCESSING

User · Answer

For Xcode 4 x     Goto Product Debug Workflow and uncheck  Show Disassembly When Debugging    For Xcode 5 x    Goto Debug Debug Workflow and uncheck  Show Disassembly When Debugging

User · Answer

Thing to try     1   restart xcode 2   select another simulator -- which was my case 3   reboot mac   if none of this works  then look at the project settings    which is leeast possible thing

User · Answer

Came to this page with the same problem  C code in Xcode 6 not stopping at breakpoints  and none of the solutions above worked  the project was practically out of the box  settings-wise  so little chance for any of the debugger settings to be set to the wrong value      After wasting quite some time reducing the problem  I finally figured out the culprit  for my code    Xcode   LLVM  does not like Bison-style  line preprocessor commands   Removing them fixed the problem  debugger stopped at my breakpoints

User · Answer

I think the problem could be incompatibility between device versions and Xcode  I have this problem when attempting to debug on my iPhone 4S running iOS 5 0 1  I am still using Xcode 3 2 5  I got the symbols from the handset by selecting  use this device for development  in the Organiser window  This phone refuses to breakpoint however  My old 3GS will breakpoint  same Xcode project  same settings    just different device and it s running iOS 4 0  I guess this is an Xcode bug in 3 2 5  since I have the symbols  Having tried all the solutions posted here so far  I have decided the solution to my problem is to go ahead and upgrade to XCode 4  Perhaps you cannot debug effectively unless your base SDK is at least as high as the system on which to debug  Maybe that s obvious - can anyone confirm   Edit  I will update when I can confirm this is true

User · Answer

I had the similar issue  I re-installed xcode  that solved my problem

User · Answer

If all else fails  instead of a breakpoint  you can call the following function   void BreakPoint void        int i 1       if    OPTIMIZE       printf  Code is waiting  hit pause to see  n        while i        endif     To resume  manually set i to zero  then hit the resume button

User · Answer

I had the similar issue  I re-installed xcode  that solved my problem

User · Answer

If you are using subversion  just revert your project files  only  to the last time you knew the debugger was working

User · Answer

Go to the Xcode Debugging preferences  Make sure that  Load Symbols lazily  is NOT selected

User · Answer

I have Xcode 3 2 3 SDK 4 1 Breakpoints will fail at random  I have found if you clean the build and use the touch command under build they work again

User · Answer

This happens from time to time with an iOS project at least  To fix it  I had to reboot the iOS device  quit Xcode  and rebuild the project

User · Answer

This had me in Xcode 9 for half a frustrating day  It ended up been a simple debug setting   Go Debug   Debug Workflow and make sure  Always Show Disassembly  is turned off  Simple as that

User · Answer

Here s an obscure one I ve run into  if you re working on a shared library  or a plugin   your breakpoints will go yellow on startup  which might cause you to hammer your keyboard in frustration and kill the debug process  Well  don t do that  The symbols won t get loaded until the app loads the library  at which point the breakpoints will become valid  I ran into this problem with a browser plugin    BPs were disabled until I browsed to a page that instantiated my plugin

[xcode] Why aren't Xcode breakpoints functioning?

Examples related to xcode

Examples related to breakpoints