Re: Xcode 3.0 and debugging plug-ins
Re: Xcode 3.0 and debugging plug-ins
- Subject: Re: Xcode 3.0 and debugging plug-ins
- From: Jake Traynham <email@hidden>
- Date: Wed, 23 Jan 2008 14:37:20 -0600
Hello,
Thanks for responding. I didn't think to try different Debug
Information Formats. I was using DWARF, so I switched to Stabs to see
if it made a difference. Unfortunately, it didn't. Since this is a PPC
machine, I can't use "DWARF with dSYM" or I would try that as well. So,
I'm still stuck with debugging not working correctly on PPC but working
fine on i386. The breakpoints are apparently just not matching up with
the actual code points or something. It pretty much makes debugging
with Xcode 3 on PPC useless ... at least with "plug-ins" like I'm
dealing with.
*sigh*
Jake
Jaime Rios wrote:
Hi Jake,
I've been using Xcode 3.0 on projects that were built in 2.4 and I have
been able to successfully debug them on a PPC laptop. I'm assuming that
you have already tried cleaning the project builds and rebuilding them,
so I won't ask. However, have you tried *toggling* your debugger output?
Say from *STABS to dSYM*, build, then switch back to STABS and build
again? Rarely, when I debugger problems that I can't figure out, I do
this and usually my GDB oddity goes away.
Hope this helps.
--
-Jaime
http://www.jaimerios.com
On Jan 8, 2008 10:15 AM, Jake Traynham < email@hidden
<mailto:email@hidden>> wrote:
Hello,
I develop FileMaker Pro plug-ins and since upgrading to Xcode 3.0, I'm
having difficulty debugging them from Xcode. I fought with the problem
for several hours yesterday on my PPC laptop until on a whim I tested it
on my Intel mini where it seems to be working fine. This is what I've
observed:
On the Intel mini, Xcode 3.0 compiles the plug-in, runs the host
executable (FileMaker Pro), and stops correctly on any breakpoint I have
set in my plug-in code. All seems fine there.
On the PPC laptop, Xcode 3.0 compiles the plug-in and runs the host
executable fine, but stopping on a breakpoint I have set is seemingly
worthless. At first, I couldn't get it to stop on a breakpoint at all
and after doing some googling, came across maybe turning off "Load
symbols lazily". This seemed to help at one point, but I was trying
several things at once and now I think turning this option off didn't
make a difference. (I was testing again this morning before sending
this
email and the Intel mini was working fine with this option turned on. I
turned it back on on the PPC laptop and am still getting the oddness I
describe below, so this option apparently has no bearing.)
I figured out through luck (if you want to call it luck) that if I
set a
breakpoint several hundred lines after the point in the code that I
actually wanted to break in, that the debugger would pause and let me
step through the code, but this is worthless as well. In the Debugger
window, the call stack pane shows the correct function that I'm trying
to debug. The Variables pane shows me the variables for the correct
function I'm trying to debug. But the code source pane on the bottom
shows the instruction pointer in the point in the code where I had to
place the break point several hundred lines below where I'm actually
trying to debug. If I try to step through the code from that point,
the
Variables pane seems to update with the correct values from the correct
function, but the instruction pointer in the code source pane jumps
around weird as if it were showing me the correct source code. It's
thoroughly useless to actually debug the code, not to mention
frustrating.
Is there anything I can do about this, or anyway I can "debug" the
situation further to find a way around this?
Thanks,
Jake
--
Jake Traynham
Owner, CNS Plug-ins
http://www.cnsplug-ins.com/
<mailto:email@hidden>
--
Jake Traynham
Owner, CNS Plug-ins
http://www.cnsplug-ins.com/
_______________________________________________
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