No Debugger Setup For Mac

• How To Debug Mac Computer

1. GDB, and set the GDB debugger field to /usr/local/bin/gdb. If there is no GDB section in the C/C++ Debug subtree, close the preferences window, and try to first start a debugging session for any project that you can already run without problems.
2. 13.12 for Mac codeblocks.org. DE for C++ that includes the MinGW compiler. Latest version. The Code Blocks’ debugger supports the applying of breakpoints on the source code or on the data that the program operates, as well as the establishing of conditions.

How To Debug Mac Computer

Debugger Setup. From Free Pascal wiki. Make sure that the option 'GNU debugger ' is selected. The path to gdb.exe may differ: On Linux/Unix based systems it may be something like '/usr/bin/gdb' On Windows it should be in a folder called 'mingw bin ' under the directory in which Lazarus is installed.

Trying to debug an application written in Qt on mac (10.6.8). Qt 4.8.6, QtCreator 3.2.0, I set up the debugger System GDB at /usr/bin/gdb and compiler gcc-4.2 I want to debug the code. I get in the application output window Debugging starts Debugging has failed Debugging has finished (and no breakpoints were hit, nothing has started in code) I opened the debug log window, and the only suspicious things I saw were. 111^error,msg='Undefined command: 'python '. Try 'help. NOTE: ENGINE SETUP FAILED State Changed From EngineSetupRequested(1) to EngineSetupFailed(2) HANDLE RUNCONTROL FINISHED. On the left, some of the commands had 109-interpreter-exec console 'python sys.path.insert(1, '/Volumes/QtCreator/.'

110-interpreter-exec console 'python sys.path.append('/usr/bin/data-directory/ python)' 111-interpreter-exec console 'python from gdbbridge import.' I checked that python is installed.

I can type python from anywhere and get its command prompt so it is on system path. I read something about having to sign a fsf debugger but the one I am using is not a fsf debugger? What can I do to debug my apps in macx? Edit: Tried gdb from command line, with the app as argument GNU gdb 6.3.5 (Apple version gdb-1518) (Sat Feb 12 02:52:12 UTC 2011). This GDB was configured as 'x8664-apple-darwin'. Warning: Unable to read symbols for QtSvg.framework/Versions/4/QtSvg (file not found). Warning: Unable to read symbols from 'QtSvg' (not yet mapped into memory).

Warning: Unable to read symbols for QtGui.framework/Versions/4/QtGui (file not found). Warning: Unable to read symbols from 'QtGui' (not yet mapped into memory). Warning: Unable to read symbols for QtCore.framework/Versions/4/QtCore (file not found). Warning: Unable to read symbols from 'QtCore' (not yet mapped into memory). Warning: Unable to read symbols for QtNetwork.framework/Versions/4/QtNetwork (file not found).

Warning: Unable to read symbols from 'QtNetwork' (not yet mapped into memory). Reading symbols for shared libraries. Some warnings that.o is more recent than.dylib in dependent libs. But that I don't have to step into so I don't care. Warning: Could not find object file '/usr/llvm-gcc-4.2/bin/./lib/gcc/i686-apple-darwin11/4.2.1/x8664/crt3.o' - no debug information available for 'darwin-crt3.c'. Done So I type run Program received signal EXCBADACCESS, Could not access memory. Reason: KERNINVALIDADDRESS at address: 0x000000 0x00007fff83872c00 in strlen I don't know where that is (I do but really can't see it) or if it is an actual string pointer or something else.

I don't know where the breakpoints would be, the entire source is very long and contains lots and lots of files so I really don't know how I can do it with gdb from command line. But it seems that it did get started, without complains about python?

The warnings at start - could that mean that there is still hope, that it is possible to somehow configure gdb to run with Qt if it learns about its libraries? Searching for the missing libraries. I have tried to replace my debugger (in Qt) using lldb and qmake - in both cases I got an error 'Unable to create a debugger engine of the type 'No engine' Edit: Another suggestion I read about is to recompile Qt Creator Binaries to add debug symbols. I hope that is not what I have to do because 'Note: With Qt Creator 3.2 we drop support for OS X 10.6 (Snow Leopard). The technical reason for this is that Apple does not support any kind of C11 on that OS version. Of course that does not affect on which platforms you can run your Qt applications on. But it is not possible to run the Qt Creator 3.2 binaries on 10.6, and it also is not possible to compile Qt Creator 3.2 on 10.6 with the tool chains provided by Apple.'

(from release notes) Update: I was able to find the cause of the error above (the KERNINVALIDADDRESS) by placing a zillion qDebug statements. Though that was not what I am trying to accomplish, one error out of many. I still have lots of errors. Attaching a debugger would be wonderful. I have listed the required libs for the program - they seem to exist.

Not sure if they are 'debug' or 'release' libraries. But I am not trying to step through the Qt sources, so why would it matter if I have debug symbols for them? And if they were 'release' type libs, then my whole program, build in 'debug', would not execute or even fail to build? Since I am building my code in 'Debug' mode and it executes, the libraries must be correct, right? So confusing.