@bitwitch

Thank you so much!  I have spent hours in the past searching for a way to use xcode purely as a debugger. I've wasted time trying things to no avail, which is part of the reason I have no desire to use a big annoying IDE in the first place. I use vim as my editor and a simple build script or makefile. I just wanted to use a graphical debugger every now and then. You have saved me, thanks my dude.

@loryon

I have been waiting for this!

@andii1701

Enjoying this series!

@andrewmerkley1425

So having followed this one, I did find GPU Frame Capture in the options of my Run scheme in Xcode. Enabling/disabling it doesn't seem to make much of a difference, and honestly I'm not sure if there was a problem in the first place. I did notice that running the executable in Xcode seems to use about 50% more memory than running it without Xcode, which is interesting. Looking forward to the rest of this series!

@asrdoc

Hey Ted, really appreciate the work you've put into documenting all of this! I'm having a bit of trouble with using xcode as the debugger. I've went over the steps multiple times and (I think) I have everything set up exactly as it is in the video (other than using a slightly older version of xcode, 9.2). Sadly, no matter what I do Xcode ignores any breakpoints set in the main file. I can run and then pause the debugger, and step into the code fine from that point. I can also set a breakpoint with lldb in the console while paused, un-pause, and that all works fine too. But any breakpoints set in the actual file in Xcode are ignored. Is there anywhere you would suggest looking to try and figure this out?