Real-Time Debugging with Xcode Attach to Process for iOS Apps

In order to improve development efficiency for a large Swift‑based iOS app, the team designed a real‑time debugging solution based on Xcode’s “Attach to Process” feature.

The solution allows engineers to attach the debugger to a running test build without recompiling, set breakpoints, and inspect variables directly.

Attach to Process is a menu item in Xcode’s Debug menu that lets the debugger connect to a running process. Once attached, normal debugging tools (breakpoints, view hierarchy, variable inspection) work as if the app had been launched from Xcode.

Environment restoration is required because the source code version used to build the test package must match the binary being debugged. The team records repository information during CI/CD, then restores the exact commit locally before attaching.

Typical steps for restoration:

Record repository info when the test package is built.

Ensure each test package has a corresponding repo reference.

Provide a tool that switches the local workspace to the recorded commit.

Real‑time debugging exploration revealed three conditions for a breakpoint to be hit:

The line of code must be compiled.

Debug symbols must be present (no stripping).

The library containing the code must be loaded.

To satisfy these, the team used LLDB commands such as:

(lldb) image list DuAttachProcess

(lldb) image lookup -rn ViewController.log DuAttachProcess

Path mapping is performed with LLDB’s settings set target.source-map command, e.g.:

(lldb) settings set target.source-map "build‑machine/source/path" "attach‑project/source/path"

Because the project is Swift, the Swift optimization level must be disabled ( -Onone ) in the relevant Build Settings configuration to keep symbols.

For component‑based projects managed with CocoaPods, the same mapping and optimization adjustments are applied to each pod target. A sample post_install hook is:

post_install do |installer|
  installer.pods_project.build_configurations.each do |podConfig|
    if podConfig.name == 'debug' # or release, internal, etc.
      podConfig.build_settings["SWIFT_OPTIMIZATION_LEVEL"] = "-Onone"
    end
  end
end

When debugging binary pods, an additional source‑map from the binary‑creation path to the local source path is required:

(lldb) settings set target.source-map "binary/component/path" "attach‑project/component/path"

After applying these configurations, breakpoints become active, variables can be inspected with po , and the team can debug test builds without recompilation.

Conclusion : By restoring the exact build environment and ensuring that debug symbols and source mappings are correct, the team achieved a fast, compilation‑free debugging workflow for large iOS applications.