I set a breakpoint but when I run my program it looks like it disables itself. Any ideas what's going on? The breakpoint arrow is dark blue before I run the program, and upon execution changes to light blue.
Breakpoints in Xcode can be fickle...most of the gotchas are detailed in this SO thread:
Why Aren't My Breakpoints Working in Xcode
Related
I've had the macOS Mojave turned to dark mode and back a couple time. I'm seeing a weird bug where most of the time my breakpoint debugging no longer highlights the line currently being executed. I get a green bubble saying "Breakpoint" to the right, but the line itself is not highlighted.
How do I restore Xcode 10.2 not highlighting the lines stepped through while debugging with breakpoints?
Toggling between different stack trace levels at the "thread" restores highlighting when switching between levels, but within the same level, I lose highlighting as soon as I select anything else, and I don't get the highlighting restored when I click on the breakpoint within the same level.
I would expect to see a faint gray highlight to appear on the same line as the debug bubble (same as cursor at the bottom of the image).
I would expect to see every time I click on breakpoint
After activating a debug session, the program started running. At this time, I tried to create a breakpoint. Unfortunately, it said "Unverified Breakpoint" and the color turned into dark black, different from the other pre-defined one (which was red). You can see more clearly on the image below. The debugger would never stop at the line of the breakpoint.
Did I miss any steps?
After I open a certain page of my app, it crashes on the simulator, and shows an error "Thread 1: breakpoint 7.3" in Xcode. When I open this page, it won't even call the viewDidLoad() method... My best guess is that the problem arises from the storyboard because I was trying to implement a search bar before I screwed things over and all the code was working fine. Any suggestions would be helpful
You must have set the breakpoint by mistake.
Breakpoints are useful for debugging. But if you dont require it, you can do one of the follwing
1) you can hit Cmd + Y and rerun project, this will deactivate your breakpoints but won't delete it.
2) Or you can go to project navigator, and click breakpoint navigator and delete all breakpoints
3) You can also see the blue mark on the left side of your code (main editor), that is a breakpoint itself, you can click (two finger click) on the blue breakpoint and delete it.
I've just encountered a really bizarre scenario and can't find any info on this elsewhere. When Xcode breaks at my breakpoints, all keyboard entry for the whole system is unresponsive. I can switch to another app but no key strokes are recorded. Xcode itself is unresponsive to keyboard input.
Anybody else seen this?
I'm running 10.10.1 and Xcode 6.1.
Based on the comments above it would seem that this issue has to do with behind the scenes details of Powerbox. To explain further: my app is sandboxed and calls NSOpenPanel. When breaking (Xcode breakpoint) in the completion block of NSOpenPanel I experience system-wide keyboard input loss.
Keyboard entry behaves normally in breakpoints outside of the call to NSOpenPanel. After working past this area of code I observed that my subsequent operations (queued in the background from the completion bock) often finish before the NSOpenPanel is completely torn down (disappears from the screen). My assumption is that until NSOpenPanel is removed from the screen (and maybe further after), Powerbox won't release control of the keyboard.
Much of this is assumption since I don't have the actual Powerbox code and can't step into it but it seems to fit.
I worked around my debugging issues by utilizing print statements and stepping through code with the variable inspector open. Mouse input continues to function so you can right-click (if you have a two-button mouse) on the variable and print its description at least.
Thanks for the help Ken.
UPDATE
I am now delaying execution of any of my post-NSOpenPanel actions using dispatch_after. On my system a delay of 1 second is doing the trick. I really don't like adding arbitrary delays but this seems to work.
Every time I set a breakpoint, Xcode 3.2.5 throws in a big blue message bubble taking up two lines of code and disrupting my code structure. It is so annoying. I always have to click on the breakpoint and choose "Hide message bubble".
Is this a bug or can I do a preference somewhere to avoid them?
Yes I know there is Xcode 4. I want to use Xcode 3.2.5 for this project I am working on.
To do this, just open the Debugger window by pressing Command+Shift+Y.
Right click anywhere in the code window and go to Message Bubbles > Hide Breakpoints.
Image is attached. :)