I am trying to use the debugger in Xcode, but since I installed version 11.2, it keeps crashing with this message: Message from debugger: The LLDB RPC server has crashed. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log.
The crash log is here: https://drive.google.com/file/d/1HB0mAWHiBgZRtyuDWRvpdZKPeQlMRnKR/view?usp=sharing
Is there any solution/workaround for this?
Related
I am developing an Electron app for Windows and within the past couple weeks the app has begun to crash intermittently without any apparent cause. I downloaded the windows debugging tools to examine the crash dumps and found the error Unable to find system thread 1C10. What does this error mean? How can I proceed?
Im trying to get crash symbolication to work on Xcode 7. My app is already on the Mac App Store and I'm getting crash reports. The problem is that they are not symbolized. When uploading to itunesconnect I did check the option to upload the DSYM files.
If you notice on the screenshot below, the first 2 lines are indeed symbolized, but they belong to one of my frameworks not the main application. The main application is giving me a 0X10093d000 symbol repeatedly.
What could be the problem?
[Update: Still don't have all crashes symbolicated in 7.3, but for each crash condition, we can usually page to an individual crash report which is symbolicated]
Try XCode 7.3
For reasons unknown, we can only reliably symbolicate our latest production release with XCode 7.3, even though we didn't use it to create the release.
7.3 introduced some new errors and warnings, so if you do download it, I recommend you download it from Developer Center and install in a seperate directory which does not overwrite your current XCode 7.x install.
I have problem with Delphi Mac OS X development. I get debug assertion failure error when I try to debug program. My application is just simple form where is few TLabel and TEdit component. Also there is two TImage components where is two images included. And there is also one TProgressBar component on my form. Connection between mac and my pc works ok. It tries to start application when I run it but it disappiers and Windows 7 and Delphi shows error debug assertion failure.
At first there was problem with deployment and my project file was corrupted so I created new project and then I added my old form to new project. After that compiling application works ok but now I get error message debug assertion failure.
I have Delphi XE5 and Windows 7 64-bit.
Mac computer is macbook pro.
PAServer on OSX is a bit buggy and it sometimes crashes with these assertion failures. It's not your application that raises the assertion failure.
If PAServer crashes with an Assertion when trying to start your application, then I'd suggest the following:
1. Close Delphi and PAServer
2. Wait until both have completely shut down
3. Start Delphi and PAserver again
Sometimes this already solves the problem.
If this does not help, try starting your application from OSX from the Terminal and see what happens. Chances are you see an access violation or similar printed to the terminal window. If that is the case you might have a bug in the initialization part of a unit. PAServer likes to crash with an assertion failure if that happens. You'll have to debug the start-up process of your application using F7 and F8. You might be able to speed this up by setting breakpoints in the initialization of some units.
Agree with Sebastian. PAServer is not stable at this stage. There are MANY reports about this:
PAServer can't load dyld: Library
Delphi XE5 PAServer Unauthorized user
How can i debug my DLL project with Delphi's PAServer
Delphi XE4 iOS can't connect to PAServer
https://stackoverflow.com/questions/28115855/paserver-crashes-on-win64
Delphi Mac OS X
Solution: wait until they release something stable. (You will have to pay again, of course)
This question involves Unity3d, but it's not specifically about it.
I'm building a Unity project for OSX; as a result, I get complete .app that I can run — without xcode project in between, as on iOS. Everything goes OK, but my app hangs up from time to time, forcing me to kill it.
What OS X tools can I use to help with debugging such a situation? May be there's something in xcode instruments that can help me?
You'll want to get the crashlogs, which will give you the callstack, and therefore the location in the code of the crash.
Here's some info on how to find the crash logs:
http://serato.com/scratchlive/support/6600/how-to-get-a-crash-log-in-mac-osx
And here's some info about what to do with them once you have them:
How to symbolicate Mac OSX crash reports issued by Apple?
Sometimes when I try and build a project in Xcode, roughly 1 in 10 times, it crashes and quits. I then get an error box which says: "Xcode quit unexpectedly while using the libclang.dylib plug-in". Xcode will also sometimes crash randomly with no error report. I have never heard of libclang before, what should I do?
try installing latest Xcode 4.0.2 version