Re: XCode debug env & Attach process...
Re: XCode debug env & Attach process...
- Subject: Re: XCode debug env & Attach process...
- From: Thomas Engelmeier <email@hidden>
- Date: Wed, 2 Jun 2010 10:48:18 +0200
Am 23.05.2010 um 00:15 schrieb Christian Martin:
> To make things worse; most compilation of the UNIX-like application is done thru a large set of make files. It is somewhat tedious to rebuild the whole environment in XCode; so to cut it short, I added -g3 flag in the compilation command in the make file. Then I created an XCode environment with only of the files of the UNIX-like program (...actually my main.cpp); Added all the .o file to the project and libraries. I am able to create a executable (if we may say) that runs fine.
Does your build process leave the symbols in the executable or produce a dSym file? that is required in order to debug. Optimisations will also screw debugging.
for nice integration
- Xcode needs to be aware of the executable created, usually by linking it itself
- The debug options "Wait for launch" in my experience helps. Make sure your Carbon app launches the Xcode provided app, not some other version (Executable settings, debugging). The setup is a. open your helper proj. in xcode, hit "debug" b. launch your UI app c. ui app launches helper, gdb breaks upon launch
- Make sure your TARGET has the same name as the EXECUTABLE. gdb attaches to the TARGET name and not to the EXECUTABLE name B-(((
> My problem is that when I set breakpoints, they do not seem to be recognized. I get a message saying : No location found for SomeFile123.cpp.
>
> Am I missing something ?
Sounds like you have the Carbon app project open in Xcode or no symbols. With an open app the global symbol browser gives a good hint which binaries gdb recognized as loaded...
Regards,
Thomas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden