I have been playing around with this for a while but am still
stuck. I used
all the advice that was given me but am still unable to debug an
application
build with an external makefile in XCode.
This is, where I currently am:
1) Because I was was unable to get the main application to
work in
the XCode
debugger, I'm now using a very simple "Hello World" style
application and
would like to track my problem down in this simplified
environment.
2) To make things even more complicate I'm now able to debug this
sample
project on one Mac and it does not work on another Mac.
3) When trying to debug the application I simply open one of the
source
files and set a breakpoint. When then running the application
in the
debugger it breaks on one Mac and does not on the other one.
Is there any way to track down why the debugger does not break
when hipping
a (properly set) breakpoint?
4) One mac is a G5 based system and the other one is an Intel
based system.
The application itself has been build as a PowerPC application
and
I'm able
to debug on the G5 but not on the Intel one. This would all point
to "some"
problem with the different architecture but unfortunately main
main
applications cannot be debugged on any of the two systems.
Are there any significant restrictions when debugging a PowerPC
application
on an Intel mac and vice versa?
5) The only difference in the configuration (I can notice) is as
follows:
A breakpoint is set in the files main.cpp and sub.cpp (e.g. main
() - Line
10). The application generates a binary named hello.
On the PowerPC (where it is working) the list of breakpoints
(Debug>Breakpoints) are shown with a Location = "main.cpp -
hello".
On the Intel Mac the same projects shows a list of breakpoints
where the
Location = "english" or main.cpp but without the "- hello"
appendix
This all seems to indicate that the XCode debugger does not
"know"
about the
right location of the source files but I'm unable to track down
the source
of the problem.
Any help is really appreciated,
Dieter
On Jul 31, 2007, at 12:29 AM, Chris Espinosa wrote:
On Jul 30, 2007, at 2:19 PM, Jeffrey Oleander wrote:
Hmmm, my knee-jerk reaction to the question was in another
direction.
Isn't the debugger that Xcode uses gdb? "Xcode debugger
without Xcode" sounds like gdb to me.
gdb is a command line interface.
Xcode Debugger is a GUI that sits on top of gdb.
What the OP wants is a GUI debugger on a makefile project,
without
having to
build the project in Xcode. And Xcode can do that; the hack is
you have to
a) create a null project beforehand (you don't have to build the
sources in
Xcode), and b) you have to manually point the debugger at the
process and
your sources.
But once you have that, it does work, and believe me, it's much
nicer than
's s s s s' in the Terminal.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40qualiant.at
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden