I'm using Xcode4 and the debugger keeps jumping into .asm code when I select jump over. I don't know .asm and just want the next line of ObjC code. Is there some setting to have it not show the .asm code?
Thanks!
Which debugger you are using? LLVM or GDB. (You can find out at the menu product->edit scheme as shown figure below).
If the debugger is LLDB, try to switch it back to GDB and see that fix your problem.
Related
When I try to debug with breakpoint, it jump to assembly view like this no matter which line of code. I want the highlight of current source line back!!
How can I config it??
This is a useful feature sometimes, but is easy to turn off:
Debug > Debug Workflow > Always Show Disassembly
In older versions of Xcode (<6.1):
Product > Debug Workflow > Show Disassembly When Debugging
I'm having the same issue in Xcode 6.1 and solved it by doing the following:
Debug -> Debug Workflow -> UNCHECK Always Show Disassembly
Make sure "Always Show Disassembly" is unchecked
You can try this
Product > Debug > Create Symbolic Breakpoint
I agree with humphriesj regarding "Always Show Disassembly" in Xcode 6.1, and it did work for awhile.
But for me it seems to have turned itself back on, even though it was still unchecked in the menu. I turned it on and then back off, and finally I can see the source code again.
I remember using turbo c++ compiler where I could do line by line code debugging technique, and was a great tool for both learning and debugging. Is there the similar way to do in Xcode. Are there any other way rather that putting break points??
From Product->Debug menu (Xcode 4.+), try the following options (they provide quite a similar functionality ):
Step Over (F6)
Step Into (F7)
Step Out (F8)
Manual : Debugging with Xcode
For some reason my Xcode debugger shows assembly code when debugging an iPhone app code. I'd like to see only Objective-C code, not assembly. This used to work OK but now something has changed. How to get back to "normal" debugging? Is there a setting in Xcode somewhere?
#AlexR: To see the source code in Xcode 4.4, switch off Show Disassembly When Debugging over here: Product -> Debug Workflow -> Show Disassembly When Debugging
In Xcode 3.x: Run -> Debugger Display -> Source Only
In Xcode 8.2.1:
Click Menu item "Debug"
Select "Debug Workflow"
Click the "Always Show Disassembly", so that no checkmark appears.
I'm having the same problem despite having unchecked the "Always show disassembly" option. Contacted Apple and they said
"This is usally a permissions problem or an issue with dSYMs not being found by the debugger due to a bad .lldbinit file."
Everywhere there are pretty pictures of failing tests shown inline in the code editor, like in Peepcodes Objective-C for Rubyist screencast and in apples own technical documentation:
(source: apple.com)
When I build my test-target, all I get is a little red icon down in the right corner, stating something went wrong. When clicking on it, I get the Build Results, where I can start to hunt for test results.
Do anyone have a clue on what´s wrong?
Have a look at your Xcode preferences. Under the Building tab you want to change your settings for Message Bubbles.
This works for Xcode 3.1 which it looks like the image you've shown. Xcode 3.2 has a different style of bubble and doesn't have this preference.
Press "Cmd =" to travel between build results, you should see a warning.
Also, that specific warning seems like it's from the static analyzer - you turn that on by going to project preferences and checkmarking "run static analyzer" or by using the "Build and Analyze" option.
Try Cmd-Shift-H to show all message bubbles.
I'm trying to watch a variable with Xcode. I'm following the instructions in here by pausing at a breakpoint, selecting Run > Variables View > .... but with the exception of "Enable Data Formatters" the rest of the options are all greyed out. Any ideas?
I'm using Xcode version 3.1.3.
I haven't gotten watchpoints created from the Run menu to work for me either, unfortunately. One thing to be aware of is that when a variable goes out of scope, the watchpoint may become invalid.
If you don't mind getting a little more in-depth, you can use some low-level gdb commands to set a watchpoint for the address of the memory itself. For example, in the guide you linked to, they show how to watch the variable path which is a pointer with the value 0xbfffeb70. To manually set a watchpoint for that address, click in the debugger console (where the debugging output is printed) after the "(gdb)" prompt and type something like this:
watch *((int*)0xbfffeb70)
The cryptic syntax is necessary because gdb expects inputs as C expressions. For a little more detail, visit this link and jump to the section titled "Using hardware watchpoints". (I'm testing on an Intel machine, not sure how PowerPC handles it.) When you set watchpoints this way, Xcode will alert you with a drop-down sheet when a watchpoint is reached and tell you how the value was changed, and gdb will print the same info in the console.
I just ran into this problem. Here is a solution: right click on the variable name and select "View variable in window" from the menu which appears. It should be near the bottom.
Add a breakpoint. Right click in the watch list of the debug area and choose "Add expression..."
If you are getting a different menu, you have to click off of the currently highlighted variable so that nothing is highlighted when you right click.
The Answers given here only work if you use the gdb compiler. For those of you who are looking for an option to set a watchpoint with the lldb compiler I have bad news:
It's not working jet (XCode 4.3.2 with lldb 3.1) even though the lldb docs say you can.
Check out this Email. The lldb commands compared to the gdbs can be found here
I was trying to figure this out in XCode 5. I finally found a "Variables view" button at the bottom right of the output console. It's the little rectangle that will be gray on the left, white on the right if it's not enabled. I'm not sure if this is in XCode 3, but I expect most people have upgraded anyway.