Friday, May 30, 2008

In Xcode, an orange breakpoint means GDB couldn't resolve your symbol

Xcode Orange BreakpointIf you see a breakpoint in Xcode that is orange, or I actually think of it as semi-filled orange, that turns out to mean GDB could not resolve your symbol, and that breakpoint will not be hit. This condition seems to mysteriously appear, but it could turn out to be a bug in Xcode or something I mangled in my project file (I had a bad target rename experience, *shudder*). The only thing that seems to solve the problem concretely is to disable Load Symbols Lazily in Xcode Preferences Debugging tab. When I turn it off, I don't notice a performance hit, but I don't have a lot of source files or a large application, but your mileage may vary.

14 comments:

Anonymous said...

thanks!

sri varadarajan said...

Thank you for this tip! Saved me lots of head-scratching.

João Reis said...

yes, that was it, xcode had an internal reference wrong.

The beakpoint turned orange, it didn't even compile.

I delete the file from xcode and added again and this fixed everything.

Thanks.

James said...

Thanks, worked for me too!

Hemicube said...

Thanks man!!! This was buggin the hell out of me :)

brian.brackeen said...

worked for me!

Anonymous said...

Thank you very much!

Kind regards
Mike

metric152 said...

I was able to fix this error by running Build->Clean All Targets

Dave Murdock said...

@metric152 I wish that had fixed the issue for me, but it always returned, so leaving off Load Symbols Lazily seemed like the best option. Perhaps I will turn it back on and try again.

thofil said...

Sometimes, "clean all targets" helped in my case, but switching off "load symbols lazily" seems to fix the issue always.
Thanks for the hint.

Ryan said...

Thank you so much for this!! I had tried everything I could think of and nothing worked (Clean all, deleting the Breakpoint and making new ones). Finally can debug my app again, hooray!

Anonymous said...

Thank you.

I've been having this problem for days.

It's August 2009 and I'm using iPhone SDK / 3.1 Beta 3 with XCode 3.1 Beta 3 and this STILL isn't fixed.

Anonymous said...

Removing the .m/.h files from the project (not the actual file system) and then adding them again fixed the issue for me, at least for now!

Celso_ said...

\o/ just saved my life!

Thank you for sharing this!