While using the debugger in Xcode, I got the following error:
"Execution was interrupted, reason: breakpoint 6.3"
So, I'd like to remove breakpoint 6.3. How can I figure out which one has the number 6.3? I have looked in the breakpoint summary panel, tried right clicking on each one, but I don't see any way to identify each these number.
There seems no way to identify the breakpoints by number in the Xcode Breakpoint Navigator.
However, you can easily remove the breakpoint in the debugger console. In your case "6" is the breakpoint number and "3" is one of the breakpoint locations.
breakpoint list
shows all breakpoints.
breakpoint delete 6
deletes breakpoint 6 (with all locations).
breakpoint disable 6.3
disables only location 3 of breakpoint 6.
Related
I'm using spyder 3.3.6 and, since a week ago or so, the debugger has suddenly start ignoring any breakpoints I define by placing a red dot with a double click on the corresponding line. Once I start debugging pressing Ctrl+5 the debugger stops at the first line of the code, even if there isn't a breakpoint. Then when I press Ctrl+12 to move to the next breakpoints the debugger just ignores them and terminates the process without showing any error message.
Have a look at the screenshot to get a better idea of the problem:
Any suggestion to fix this?
Thanks.
I have just updated to Xcode 11 and going crazy with the debugger. I am trying to simple thing of stopping at a breakpoint and stepping trough my code.
I can add the breakpoint without problem, but when the debugger stops there, is shows me a file with HEX code only. I can inspect variables, but cannot step trough the code. See screen
shot. Do I have something wrong in my settings?
Xcode > Debug > Debug Workflow > always show disassembly (non check)
reference site
Xcode Debugger: Why is it only showing me assembler?
I want to remove several breakpoints along my program execution path. XCode stops at each breakpoint and I want to clear it immediately. In contrast to all other tools that I used to, Xcode does not put cursor on the line it stopped. Therefore, "toggle breakpoint" shortcut instead of clearing current breakpoint, puts breakpoint somewhere out of sight.
To clear current breakpoint I need to grab mouse or press extra shortcut before actually clearing breakpoint. It gets very annoying for several breakpoints in row.
Maybe there's workaround?
You can click inside the topmost thread in the Debug Navigator ⌘+6 to see where you stopped.
If you want to automatically skip a breakpoint or perform other actions when it's triggered you can Right-Click or Control+Click the breakpoint, choose Edit Breakpoint... then check Automatically continue after evaluating actions.
Since upgrading to Xcode 4 my app stops at what I think are non existent break points. When it breaks there is no breakpoint showing in the breakpoint navigator and the editor says:
Thread:1 Stopped at breakpoint 17
Anyone else seeing this? Is this something new, maybe?
Maybe it's an Xcode bug but I still have a solution.
You can use LLDB to see and manipulate all the actual breakpoints.
Just type the following commands in the lldb window:
(lldb) is the prompt.
(lldb) help -> for help
(lldb) help breakpoint -> for breakpoint subcommand's help
(lldb) breakpoint list -> list all the breakpoints.
(lldb) breakpoint delete -> Delete the specified breakpoint(s). If no breakpoints are
specified, delete them all.
(lldb) breakpoint delete 7.1 -> delete breanpoint 7.1
and, you can use this command to continue the program:
(lldb) c
user278859's answer is basically really a true answer, as this seems to be a bug in Xcode 4. I just had the same problem. I set a breakpoint at one place in a UIWebView delegate's shoudlStartLoadWithRequest-method (no other active breakpoints in the project) and the debugger stops in another method (in this case repeatedly webViewDidFinishLoad:) of the same object.
So I'd say this is an Xcode bug. Found no way of fixing this btw., other than removing the above breakpoint ... Screenshot:
Press Command + alt + B to see all breakpoints.
Select the breakpoint that you want to remove and press delete.
Ok, I deleted the only breakpoint in the offending class which was no where near the line where the debugger was breaking and the problem went away.
Fasttracks, thanks for the suggestion. I am using xCode 4 and command+alt+b no longer works. There is now a Breakpoint Navigator where all the brekpoints are listed. There was no breakpoint in the list that corresponded to the line where the break was happening.
I have the same problem before, I think its an Xcode bug. You may check if there any unwanted breakpoints created by Xcode in Breakpoint Navigator (cmd 6), delete them and it should be fine.
Xcode 4 introduced an Exception breakpoint which seems to be on by default.
i.e. when there's an exception it breaks.
This will catch an exception even if you haven't clicked the Breakpoints button.
You can check via the Debug Navigator whether it's been triggered - you'll see an "objc_exception_throw".
Open the Breakpoints view: alt+shift+5 and then right click in the empty space and hit "delete all". It will actually remove the not existent breakpoints.
I found one additional case when such breakpoint is activated:
If you set breakpoint on the code, which is actually is not compiled for selected target this part of code is not highlighted or marked, and breakpoint is set actually elsewhere in this file where debugger consider is as close as it can.
So you need to be sure that code, where breakpoint is set is compiled :-)
Not knowing what exactly Swift error breakpoint is...I had enabled it by doing such:
Guess what happens?!
It will act like a breakpoint on errors thrown by your own code, i.e. wherever you use a throw statement.
For more see here and here
I'm just starting out with Cocoa development in Xcode, doing the hello world example. I'm up to step 6 of the section "runtime debugging", which is
Using the Step Over button in the debugger toolbar, begin stepping through the code. As each line of code executes, you can examine the program’s state. The value of a variable is sometimes drawn in red to indicate that the value was modified in the last step.
Notice that the debugger pauses before executing the indicated line. After each pause, you can add additional breakpoints or choose Debug > Restart to terminate the application and start a new debugging session.
now what I've been pulling my hair out for over the last hour is the fact that this debugger will only show me assembly code. I can manually select my source code file, but as soon as I click "Step over" I'm right back in assembler view. I can't for the life of me figure out how to turn the assembler off, and make it show me my source code!
I know this article is a hundred years old, but in case anyone is wondering how to address this issue in more recent Xcode versions (as opposed to Xcode 3), you'll find the appropriate setting labeled Always Show Disassembly under Debug>Debug Workflow in Xcode 6 and up. Ensure the option is NOT checked.
In Xcode 5, the option was labeled Show Disassembly When Debugging under Debug>Debug Workflow. Ensure that "Show Disassembly When Debugging" is unchecked.
Back in Xcode 4, the Show Disassembly When Debugging setting was found under Product>Debug Workflow. Again, ensure that the option remains unchecked.
This was driving me crazy, too.
NOTE: The information above is still valid for Xcode 14+. I've applied updates to this answer as new versions of Xcode have been released. Fortunately, the option has remained unchanged since Xcode 6 (so far).
There are two other things to make sure of:
That you're looking at one of your own functions/methods. If the stack frame you're looking at is a function or method from one of the frameworks, you're going to see assembly no matter how you have Xcode configured.
That you are running a Debug build. Strip debug symbols (as in a Release build), and you'll be looking at assembly even for your own code, no matter what.
I actually figured this out before I posted, but I wanted to save others potential future headaches, (and also in case I forget later) as I could not find the answer to this by searching stack overflow, but I did find that I'm not alone.
From the run menu, select "Debugger Display" > "Source Only", or "Debugger Display" > "Source and Disassembly"