Timer Profiler Best Practices

Hey JUCE peeps.

I’ve been attempting to do some optimization tests but since the recent update to the Mac OS it seems like running a release build with debugging symbols flipped on and stripping turned off, I’m still having some trouble getting meaningful stack traces out of the timer profiler tool.

I’m wondering how others are setting up builds for optimization research.

Do you guys setup a custom scheme specific for a release type of optimization but with a way of viewing the stack trace? Do you run timer profiler against a debug build?

I’ve had to resort to using the debug build over the past couple days and it doesn’t feel right – just curious what others out there may be doing.