One is not able to run the po command in LLDB when linked to recent versions of mParticle.
Environment
- Xcode 14.2.0
- mParticle-Apple-SDK 8.14.1
Steps to reproduce
- Integrate mParticle 8.14.1 via SPM in your project (8.13.0 and above should be affected as well)
- Add a breakpoint somewhere
- Launch your project in an iOS simulator
- Make sure it reaches the breakpoint
- Use the
po command in the debugger. For example po foo to print the description of foo
Actual Result:
The debugger command fails:
(lldb) po foo
error: expression failed to parse:
error: virtual filesystem overlay file '/Users/runner/Library/Developer/Xcode/DerivedData/mParticle-Apple-SDK-bqixaejagpemcucwbbovvcavmgpa/Build/Intermediates.noindex/ArchiveIntermediates/mParticle-Apple-SDK/IntermediateBuildFilesPath/mParticle-Apple-SDK.build/Release-iphonesimulator/mParticle-Apple-SDK.build/all-product-headers.yaml' not found
error: virtual filesystem overlay file '/Users/runner/Library/Developer/Xcode/DerivedData/mParticle-Apple-SDK-bqixaejagpemcucwbbovvcavmgpa/Build/Intermediates.noindex/ArchiveIntermediates/mParticle-Apple-SDK/IntermediateBuildFilesPath/mParticle-Apple-SDK.build/Release-iphonesimulator/mParticle-Apple-SDK.build/all-product-headers.yaml' not found
error: couldn't IRGen expression. Please check the above error messages for possible root causes.
Expected result
The debugger command should be executed without any error.
Sample project
mParticleAbsolutePathDemo.zip
- Add a breakpoint in
mParticleAbsolutePathDemoTests.testExample()
- Run the test in an iOS simulator
- Run
po foo in the debugger
Notes
One is not able to run the
pocommand in LLDB when linked to recent versions of mParticle.Environment
Steps to reproduce
pocommand in the debugger. For examplepo footo print the description offooActual Result:
The debugger command fails:
Expected result
The debugger command should be executed without any error.
Sample project
mParticleAbsolutePathDemo.zip
mParticleAbsolutePathDemoTests.testExample()po fooin the debuggerNotes
-no-serialize-debugging-optionscould resolve this issue.