debugging c++ under XCode 2.2

Hi,

I'm debugging a project written in C++. It comprises six dylibs and an
executable. The dylibs are not loaded dynamically, they are linked to
at compile time, and hence alll loaded everytime the executable is
debugged.

I can run into code in these dylibs ok. My breakpoints are hit
correctly, but "step over" and "step into" do not behave as expected.
Step over often just behaves like "Continue", instead of stepping to
the next line of code. Step into often does the same, but not in any
kind of consistent way.

I have switched Optimization to "None" in the project settings
(incidentally, I can only find build settings for the project as a
whole, not for individual targets, e.g. mylib2.dylib...?). This does
not help.

Is there some setting in XCode I am missing, or is this behaviour
typical for GDB stepping in and out of separate targets. Has anybody
seen this behaviour before?

Thanks in advance for any help! =)

-scott

scott wrote:
> Hi,
>
> I'm debugging a project written in C++. It comprises six dylibs and an
> executable. The dylibs are not loaded dynamically, they are linked to
> at compile time, and hence alll loaded everytime the executable is
> debugged.
>
> I can run into code in these dylibs ok. My breakpoints are hit
> correctly, but "step over" and "step into" do not behave as expected.
> Step over often just behaves like "Continue", instead of stepping to
> the next line of code. Step into often does the same, but not in any
> kind of consistent way.
>
> I have switched Optimization to "None" in the project settings
> (incidentally, I can only find build settings for the project as a
> whole, not for individual targets, e.g. mylib2.dylib...?). This does
> not help.
>
> Is there some setting in XCode I am missing, or is this behaviour
> typical for GDB stepping in and out of separate targets. Has anybody
> seen this behaviour before?f
>
> Thanks in advance for any help! =)
>
> -scott

for the benefit of any new XCode users searching this group:

I found target specific settings. Select a target in the main XCode
project browser, then choose Project/Edit Active Target. Switching off
optimisation in there, for each target, fixes the random debugger
behaviour. I find it off that debug builds dont have optimisation
switched off by default, but there you go.