I'm seeing some truly bizarre behaviour from lldb in one of my projects. When I stop execution at a breakpoint and enter anything at all in the debugging console, there is no response:
I'm running a debug build here. The issue does not occur in other projects, where I can debug without issue.
This is a real head-scratcher. Has anybody run into this before?
I solved the issue, but in an unsatisfying manner; by getting a fresh clone from git.
I suppose one of the files in the standard Xcode .gitignore got weird and caused this behaviour.
Related
When I run my UITests they sometimes fail with a weird cause upload-symbols crashed in <external symbol>. The only work around I found is to restart Xcode, which helps most of the times, but I'm already tired of doing this.
The UITests scheme is setup correctly and I am able debug the main target during the execution of UITests, so I suppose dsym info is available. The main app doesn't crash and doesn't catch any exception breakpoints when test fails.
The failure happens at random moments of time and during execution of random tests. I haven't seen it happening on CI, which launches UITests from terminal via fastlane.
I appreciate any advice.
Xcode 10.3, I'm not sure this was happening on 10.2
MacOS 10.14.6
I'm not sure, but I faced with same error:
crashed in <external symbol>
I run ui-tests at CI and cause of my error:
Other pipeline delete and reset my current running simulator.
Also, try find out how to fix this trouble.
I use fastlane-plugin-test_center
This is definitely an Xcode bug. I realized, that this crash happens way less likely if I run all tests rather than a specific testcase/test. So I end up disabling all of the tests in the target while developing, except the one I work on and just run them with CMD+U.
I started having peculiar problems when using XCode.
Whenever I try to write test with swift, XCode shows an internal error and all the code turns white.
This happens even if I remove the #testable annotation from the code.
I tried reinstalling XCode, but this did not help.
The code builds just fine so I don't have a clue where the problem might lie.
I'm unable to properly develop tests this way, my modules are not recognised, I have no error checking or code completion.
Here is a screenshot of how the problem looks:
Would love to get any guidance on this issue...
So I guess for now there is no good solution to this problem.
It seems to be caused by crashes of SourceKit.
Fortunately the problem is not solved (partially) on my end.
I decided to make this answer a compilation of different things to try when experiencing this:
Restart - try restarting both Xcode and the PC
Clean the project (shift-command-K)
Build your code, I noticed that sometimes it occurs when you just have unrelated build errors somewhere in your project - make sure it builds
Delete the DerivedData folder rm -Rf ~/Library/Developer/Xcode/DerivedData/, but you can also delete it from Xcode
Delete the cache rm -Rf ~/Library/Caches/com.apple.dt.Xcode - Currently this seems to help the most
I will edit and add more solutions if I find any
I should mention that I originally posted this as an issue on Neovim's tracker, but it hasn't been getting a ton of traction there lately and I'm beginning to suspect that it's more an issue with my setup rather than Neovim itself.
Essentially, I had stopped building neovim nightlies for a few months. Having heard that it's getting integrated terminal support I decided to rebuild using the latest source, only to get a persistent, odd error. No matter what my build settings are, it always boils down to make hitting an error when it has to compile a file called loop.so. I hadn't noticed this issue with any other software I try to build, but I suspect it could be an issue with my environment.
Does anyone here know what this file's role is, and why the compilation could be failing at that point?
You might need to install the full Xcode app and not just the command line. This fixed the issue for me.
The issue turned out to be a bad typedef in a libuv header, object.h.
I just recently upgraded to xcode 4.6 and strange things are happening to the debugger. "po" command ceases to work some times. Also step by step debugging sometimes does not work. Is anybody else having the same issues
I have found the issue with this. I checked the Optimization Level for your Apple LLVM Compiler code compilation in target settings, changed it to None and now the debugging works as it should
Just try to clean up everything from Project menu, delete derived data folder from organizer. Exit and restart XCode. It may clean up some garbage memory and set things up. I have experienced that it improves po a bit.
MyProject has triggered breakpoint
without any brakepoints in my project (i have made sure using Debug/Delete all BP)
I do not really post some code, because project is really big and it is also impossible to make some minimal sample.
Where sould I look when getting this error?
TY
I had a similar problem recently, where it was stopping on a breakpoint that no longer existed, and my Code Coverage highlighting was reflecting an older run, somehow. Not sure why, but things were out of sync between what was current state and what it was previously. For my instance, I was able to do a Clean Solution, then shutdown and restart VS 2010 and the problem went away.
Has only happened to me the one time, so I am not sure what I could have done to cause it. Didn't see anything similar logged on Connect, either.
Your debugger might be set to break when an exception is thrown.
Go to Debug -> Exceptions... -> make sure all the boxes are unchecked.
Without any more info I can't help...