Search results for

LLDB crash

29,548 results found

Post

Replies

Boosts

Views

Activity

Reply to Stuck and memory issue in iOS9 simulator
The crashes you're seeing in Xcode 7 beta 4 could be caused by the presence of old runtimes as mentioned in the most recent Release Notes:Xcode processes may quit unexpectedly if older iOS Simulator runtimes (Xcode 6.x) are present on diskTo see if that's the case (or to rule it out as a cause), delete all (old) runtimes from /Library/Developer/CoreSimulator/Profiles/Runtimes.
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’15
"XCBBuildService quit unexpectedly" occurs %100 of the time with XCode 16 RC
I have a project which when I attempt to build with XCode 16 RC fails with the message XCBBuildService quit unexpectedly. This occurs 100% of the time, thus I am unable to build the project. It first occurred in Xcode 16 beta 1 and has been present ever since, ever present in every beta; and now as its still present in the RC its highly unlikely it'll be fixed when the RC release becomes the final release. I submitted a ticket for this many weeks ago (FB14062261), but its not been looked at/updated. This is a problem in the short term because my app needs updating to use some iOS 18 specific features, in the longer term, it won't be possible to submit the app to the App Store if it continues to only be buildable with Xcode 15. As its impossible to build the app, I attempted to create a support ticket to get assistance. However I am unable to create a support ticket because the web page won't permit me to proceed raising a ticket unless there is a test Xcode project that recreates the issue.
0
0
872
Sep ’24
Reply to Xcode problem
Also, the crashes you're seeing in Xcode 7 beta 4 could be caused by the presence of old runtimes as mentioned in the most recent Release Notes:Xcode processes may quit unexpectedly if older iOS Simulator runtimes (Xcode 6.x) are present on diskTo see if that's the case (or to rule it out as a cause), delete all (old) runtimes from /Library/Developer/CoreSimulator/Profiles/Runtimes.
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’15
LLDB RPC Server Crash Playground File XCode 16.0
When running the code below in a playground file, it crashes with an LLDB RPC Server crash. The crash log is attached. If I put the code into a project, it runs fine. lldb-rpc-server-2024-10-04-110747.txt import Foundation @objc protocol Speaker { func speak() @objc optional func tellJoke() } class Deb: Speaker { func speak() { print(Hello, I'm Deb!) } func tellJoke() { print(What did Sushi A say to Sushi B?) } } class Bryan: Speaker { func speak() { print(Yo, I'm Bryan!) } func tellJoke() { print(What is the object oriented way to become wealthy?) } func writeTutorial() { print(I'm on it!) } } class Animal {} class Dog: Animal, Speaker { func speak() { print(Woof!) } } var speaker: Speaker = Bryan() if speaker is Bryan { print(Hi, I'm a Bryan) } speaker.speak() //speaker.writeTutorial() //won't compile (speaker as! Bryan).writeTutorial() speaker = Deb() speaker.speak() speaker.tellJoke?() speaker = Dog() speaker.tellJoke?() //return nil protocol MtgSimulatorDelega
3
0
1.7k
Oct ’24
Reply to Debug Failed in Xcode Simulator
I have the same issue, Xcode : Version 16.2 (16C5032a) Simulator : 18.3 Message from debugger: The LLDB RPC server has crashed. You may need to manually terminate your process. 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.
Apr ’25
"suggestd quit unexpectedly." continually when I use iOS 11 Simulator
For several Xcode 9 betas, I've been getting this error when I try to simulate under iOS 11Path: /Volumes/VOLUME//Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/CoreSuggestions.framework/suggestdshows it is a Simulator crash.I can run in iOS 9 just fine, but would prefer to also be testing under iOS 11. Is there a workaround? (I'm now running Xcode 9b4.)
2
0
1.4k
Jul ’17
MacOs 16 - Xcode 16 beta - XCBBuildService quit unexpectedly
Translated Report (Full Report Below) Process: XCBBuildService [19515] Path: /Applications/Xcode.app/Contents/SharedFrameworks/XCBuild.framework/Versions/A/PlugIns/XCBBuildService.bundle/Contents/MacOS/XCBBuildService Identifier: com.apple.dt.XCBBuildService Version: 16.0 (23000.0.209.4) Build Info: XCBuild-23000000209004000~20 (16A5171c) Code Type: ARM-64 (Native) Parent Process: Xcode [1187] Responsible: Xcode [1187] User ID: 501 Date/Time: 2024-06-13 18:52:42.9964 -0300 OS Version: macOS 15.0 (24A5264n) Report Version: 12 Anonymous UUID: E79CA726-937A-A4A4-9B42-9DF9455F3181 Time Awake Since Boot: 1300 seconds System Integrity Protection: enabled Crashed Thread: 15 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: XCBBuildService [19515] Application Specific Information: abort() called Kernel Triage: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM
7
0
2.5k
Jun ’24
WindowServer quit unexpectedly, Ventura 13.0.1 when connected to external Dell Display.
Process: WindowServer [63374] Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer Identifier: WindowServer Version: ??? Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 88 Date/Time: 2022-12-09 16:30:33.1035 +0530 OS Version: macOS 13.0.1 (22A400) Report Version: 12 Anonymous UUID: 9B161DC0-3070-30AA-F990-43E7B1155941 Sleep/Wake UUID: 6802AED2-E132-488C-BB3B-C90C13543676 Time Awake Since Boot: 140000 seconds Time Since Wake: 6122 seconds System Integrity Protection: enabled Crashed Thread: 15 Dispatch queue: FUSkyBridge Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: abort() called
0
0
631
Dec ’22
lldb framework error after re-signing lldb code
On a MacBook Pro, OSX El Capitan release, using lldb on the command lineSummary: Keep getting a 'cannot open client port' error when using lldb command line mode. Recreated new lldb_codesign certificate but to no avail. Still getting the error.Here are the steps I took.( all work is in a separate tree off of /Users/Jeff )1. Removed all old lldb binaries/libraries2. Removed lldb_codesign certificate3. Reboot4. Re-create new lldb_codesign cert. per instructions below5. Rebuilt lldb from source ( make -B lldb )6. Reboot7. run newly built lldb on lldb ( % ./lldb ./lldb )8. still get 'unable to open client port'Any Help on this wouild be appreciated.Updating codesign============================================- Launch /Applications/Utilities/Keychain Access.app- In Keychain Access select the login keychain in the Keychains list in the upper left hand corner of the window.- Select the following menu item: keychain Access->Certificat
0
0
448
Oct ’16
help me please, Xcode 6.3.2 quits unexpectedly when submitting to iTunes Stores
Xcode 6.3.2 quits unexpectedly when submitting to iTunes StoresHello,It seems that everytime I submit to the app store, Xcode quits unexpectedly.Here's a screenshot of the Xcode Report Problem:So I have a valid distribution profile. I was able to archive. When I click the validate button, the archive was validated. But when I actually submit to the app store, Xcode just quits unexpectedly right when it starts Uploading ArchiveIs there anything I need to do before I make an archive in Xcode? Is it an Xcode 6.3.2 problem?Process: Xcode [3276] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 6.3.2 (7718) Build Info: IDEFrameworks-7718000000000000~2 App Item ID: 497799835 App External ID: 812404257 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Xcode [3276] User ID: 501 Date/Time: 2015-06-19 15:13:34.165 +0700 OS Version: Mac OS X 10.10.3 (14D136) Report Version: 11 Anonymous UUID: 7712FAC3-808B-7650-2B59-856F7
1
0
974
Jun ’15
Reply to CommonCrypto swift module error in App
Thanks Quinn, Seeking to discard any other cause, I isolate the code that uses CommonCrypto in a separated app and run it. Same behavior. In my computer run perfectly well, but when trying to use the very same app in another Mac (in this case a MacBook air M2) it crashes immediately with the message ...quit unexpectedly (Attached the crash log it offered just after the failure). So, I'm pretty sure this is somehow caused by CommonCrypto. I even tried using the package CryptoSwift but fails exactly the same way. Any help will be highly appreciated. Thanks TestLic_quitUnexp_March1-2024.txt
Topic: Privacy & Security SubTopic: General Tags:
Mar ’24