Geek Answers Handbook

Xcode breakpoints only hit during tuning during debugging

Im porting C ++ sdk from Windows to Mac OSX 10.5. I have a problem in Xcode where my breakpoints in certain files will hit only if I set them during debugging. If I stop debugging and then restart, the breakpoints will no longer hit. If I add them without debugging them, they won’t hit. It is only in certain files, and my breakpoints are always dark blue. that is, I can’t tell the difference between a breakpoint that will hit and one that won't.

In particular, my sdk consists of various dynamic libraries. They are created using Perforce jam, which calls various compilation and link executables depending on my OS and compiler version (such as Visual Studios cl.exe and link.exe). I have a simple (unit testing) command line application that references these dynamic libraries and calls the code in them. This Windows application is a Visual Studio project in which I set breakpoints on library code and expect them to be deleted.

Ive created the same C ++ command line command-line application in Xcode 3.1.2 that references sdk dylibs and calls the code in them. Some of the checkpoints work fine. I can set breakpoints in the code that is called from the problem code, and get into the nasty code, which I can then execute through a fine. The compiled code is compiled into the same dylib as the code that works fine. Its also long enough and complicated to not be a candidate for investment.

Ive tried the following:

  • Disable download symbols.
  • Compile both gcc 4.0 and gcc 4.2.
  • Do a full cleanup and shutdown.
  • Delete custom xcodeproj package files.
  • Rename files so that they cannot collide with system files.
  • Clear everything from the Breakpoints window.
  • Create a new Xcode project.

My application is compiled in DWARF format, and my libraries are built with the -g flag (along with -v, -arch i386 and -fvisibility-inlines-hidden).

Help would be greatly appreciated. Thanks.

Update : Sorry for not updating this project, my Mac port project has been delayed. I never allowed it, but found that this only happens in the constructor bodies. I will change my mind when and when I remove the problem again.

+4
source share
2 answers

Have you tried this? Why are my checkpoints not working?

+1
source

Not quite the answer: you have to report a bug in the official Apple bugtracker. The chances are high that you get an answer sooner or later there - or perhaps this is really a mistake.

+1
source

More articles:


All Articles