I have been looking around for quite a while trying to figure out how to switch from lldb to gdb and could not find anything on how to switch between the 2 in Xcode 6.1. I am trying to debug my app and I might be able to figure it out if I use gdb instead of lldb but I don't know if it will help me.
Any suggestions on which type of debugging is better and how to switch between the 2. Any input would be greatly appreciated.
Thanks in advance.
The debugger for Xcode 6 is lldb, there is no switching to gdb.
There is no reason to need gdb. What is your problem with lldb, most of the commands are the same.
See: LLDB to GDB Command Map and The LLDB Debugger.
When I use LLDB on Xcode 4.6 to debug my program ,the app will be no responding and when I use GDB it is OK,
but In the new Xcode 5 there is only LLDB can be used
who can tell me how can I fix my LLDB or reinstall it?
thx
Please try this procedure
Remove old versions of Xcode
Upgrade to Xcode 5.0.1
NOTE: GDB is no longer supported. LLDB will be installed automatically.
Please use a compatible version of OSX (10.9, Mavericks).
If this answer helps please click the checkmark to accept the answer.
Apple Xcode is unable to display any Fortran Module Variables. Module variables can be viewed by going to the Run Menu -> Show -> Global Variables
The mangling of module variables with their variable name is clear.
But when listing the value of the global variable at a breakpoint, what is shown is simply:
<unknown type>
I've encountered this error in XCode and DDD (also using apple's GDB). This is for module variables which are as simple as just integers - these are not derived data types.
I am on 10.6.8 using Apple's GDB GNU gdb 6.3.50-20050815 and XCode 3.2.6.
At the very least, can anyone see if Fortan module variables are accessible with later versions of XCode?
(although I see that Apple remains at GDB 6.3 even into XCode 4)
Fink offers gdb 7.4, that should support Fortran well, but probably you will have to use dd. I don't know if you can use it in Xcode. Apple will probably not deliver a newer version in the future, because of licence change to GPLv3.
When I build and test on the device, the Xcode console automatically goes into gdb mode, which makes it much easier to do stack traces. However, when I test on the simulator the console does not use gdb. I've looked everywhere for a preference setting but can't find anything.
How can you use gdb when using the simulator?
Figured it out - must be in debug mode.
Ok, this seems like a dumb question because MonoDevelop is getting more mature, so I'm sure I'm just missing it, but I looked around and all the questions about this subject seem to be about remote debugging or debugging on a Mac.
I'm using Ubuntu 10.04 Lucid Lynx, and I just installed MonoDevelop 2.2.1 from the software center.
I created a GTk# 2.0 project, added some widgets and code and everything seems to run fine. Then I added a breakpoint, and it shows up in my breakpoints window, and it says it's active, but the breakpoint never actually hits(stops execution and pulls me into the debugger).
I'm in Debug x86 mode, so I can't figure out what's going on.
Anyone have this happening/know what to do about it?
I'm having the same problem (also on Ubuntu 10.04) and found kind of a hack that is working for me. Instead of setting a breakpoint in the IDE (by clicking on the side or hitting F9), make a call to the System.Diagnostics.Debugger.Break() method in your code where you want the execution to break. After doing that, I am able to step through the code, use the immediate window, etc. Obviously, it's not a very good solution, but at least it's something.
To check whether you have a debugger installed, simply check whether the "Run" menu contains a "Debug" command.
You should be aware that Ubuntu ships a rather old version of Mono (2.4) which has no built-in "sdb" debugger, and its version of MonoDevelop 2.2 is patched to remove the sdb interface. To get semi-functional debugging, install the old "mdb" debugger - the mono-debugger and monodevelop-debugger-mdb packages, IIRC.
To get the best debugging experience (sdb), you need Mono 2.6+ and an unmodified MonoDevelop 2.2+. If you decide to build Mono from source, please read this and this first. Alternatively, you could use openSUSE, which has up-to-date Mono and MonoDevelop packages available.
What versions of Mono runtime and debugger are installed? I tried it with monodevelop 2.2 + mono 2.6 + debugger 0.0.0 under Windows and it works just like expected. Here is a quotation from mono's website, which may be helpful:
Mono comes with two Mono-specific debuggers: a hard debugger and a soft debugger, additionally, you can use the Unix GDB debugger with Mono to debug low level problems
...
Soft Debugger:
...
Moonlight, ASP.NET, Gtk#, iPhone and remote debugging supported
Maybe the problem is in a code? What do you mean by:
... (stops execution and pulls me into the debugger).