Until two days ago, Xcode and simulators were working perfectly fine. I turned the computer off and some software updates got installed, including macOS Catalina). I am now unable to launch Simulator. It's for any device, it simply doesn't open the application. All I see is simulator quit uenxpectedlyI've also noticed that Simulator and processors keep themselves alive no matter how many times I quit them or kill them from command line:com.apple.CoreSimulator.CoreSimulatorServiceSimulatorI found similar posts, but they are at least three years old and got a /DeviceTypes folder withing /Developer which I don't.I have tried different approaches, including:Deleting DerivedData folderDeleting /Library/Developer/Xcode folderUpdating Xcode to 11.1Usinng Xcode 10.3, where the command line tools are actually incompatible with Catalina OS.Reinstalling Xcode, restarting my machine at every step of the deletion and reinstallationDeleting CoreSimulator folderThe following commands in terminal: sudo killall -9 com.apple.C
Search results for
LLDB crash
29,554 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
This is what I am getting every time I close the app. Please suggest alternatives for Xcode 13 dyld4 config: DYLD_ROOT_PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/sarthaks/Library/Developer/Xcode/DerivedData/Dicee-iOS13-bwfmsdtnysirovgrfszwvnzssntm/Build/Products/Debug-iphonesimulator:/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libBacktraceRecording.dylib:/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRo
OK I somehow managed to break lldb loading KDKs, and my best guess is it picks the wrong python framework.lldb /Library/Developer/KDKs/KDK_10.14_18A336e.kdk/System/Library/Kernels/kernel (lldb) target create /Library/Developer/KDKs/KDK_10.14_18A336e.kdk/System/Library/Kernels/kernel unable to load scripting data for module kernel - error reported was Missing parentheses in call to 'print'. Did you mean print(Loading kernel debugging from %s % __file__)? (kernel.py, line 69) File temp.py, line 1, in# which lldb/usr/bin/lldb# which python/usr/bin/pythonClearing PATH and PYTHONPATH, or setting thing appears to make no changes.Any clues?
If you run the tool outside of LLDB, the crash should generate a crash report. Please post that here. For advice on how to do that, see Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I've been using lldb in quite a set way, generally just ^R search backwards and paste in the load address;However, I find it no longer works with xcode8.(lldb) addkext -F module/zfs/zfs.kext/Contents/MacOS/zfs 0xffffff7f9051b000 target modules add module/zfs/zfs.kext/Contents/MacOS/zfs target modules load --file module/zfs/zfs.kext/Contents/MacOS/zfs --slide 0xffffff7f9051b000 ERROR:error: no object file for module 'module/zfs/zfs.kext/Contents/MacOS/zfs' error: either the --file <module> or the --uuid <uuid> option must be specified.[1]+ Stopped lldb /Library/Developer/KDKs/KDK_10.11.6_15G1004.kdk/System/Library/Kernels/kernel # ls -l module/zfs/zfs.kext/Contents/MacOS/zfs -rwxr-xr-x 1 lundman admin 2858792 Sep 21 16:15 module/zfs/zfs.kext/Contents/MacOS/zfsSo I guess the pwd has now changed or something, odd, but I can live with that. I lets try supplying the full path instead;(lldb) addkext -F /Users/lundman/src/zfs/osx.zfs/x/zfs/module/zfs/zfs.kext/Contents/
Thanks for that. On disabling the signal handler I was able to get a crash report. However, the contents of that crash report are quite weird, and that leads me to another question about your runtime. In my crash report I see this: Thread 1: 0 libsystem_kernel.dylib … mach_msg2_trap + 8 1 libsystem_kernel.dylib … mach_msg2_internal + 80 2 libsystem_kernel.dylib … mach_msg_overwrite + 480 3 libsystem_kernel.dylib … mach_msg + 24 4 libacli11029t6.dylib … lisp_exception_watcher + 348 5 libsystem_pthread.dylib … _pthread_start + 136 6 libsystem_pthread.dylib … thread_start + 8 which suggests you have a Mach exception handler that’s active even with your signal handler disabled. Is it possible to disable that? Implementing a Mach exception handler correctly is really hard, so I’m hoping that I can disable this in order to increase my trust level of the crash report. Also, I suspect that disabling this exception handler will help with the LLDB issue [1]. Share and Enjoy
Topic:
App & System Services
SubTopic:
Networking
Tags:
I have both installed and it's still happening...How long does it take to go away, presuming you have both apps?Edit: Nevermind, the exact thing I was trying to do is brokenNew Issues • Settings might unexpectedly quit when attempting to view or select a voice in Speech settings. (42859905)
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I've never ever had so many issues with my Mac. Software developers blame Apple! I've wearied them troubleshooting issues, but it is clearly Apple. Apple's own apps lag and crash! Anything big lags and crashes! All my professional software, DEVONThink 3, Tinderbox 8, Curio, Affinity Photo, or DeVinci Resolve crash in Big Sur. I start up the software and it's a crapshoot as to when I get the app has Quit unexpectedly and it's affecting my productivity at work. Sadly this is on an my new M1 so I have no idea of knowing if it's this is Apple's silicon or Big Sur??? 🤨. I really do not have the time to troubleshoot all these issues, so I'm just left feeling very soured with my M1 purchase. 😠 MacBook Pro (13-inch, M1, 2020) MacOS Big Sur: 11.2.3 (20D91)
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I get the error mentioned in the title when I Build and Run from Xcode 7.3 beta 2 to an iOS 9.3 beta 2 simulator. Running on OS X El Capitan 10.11.3. Submitted bug # 24352291 with the generated error report.
It's possible that your runtimes are in a different directory, but many have resolved your issue by removing them. In the latest 10.11 Release Notes it is explained that:Xcode processes may quit unexpectedly if older iOS Simulator runtimes (Xcode 6.x) are present on disk.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Interesting feedback, thanks, just be sure to file reports via the link below, adding your #s to your thread for reference.1. Release notes say this about that:3rd Party AppsNew IssuesSkype might unexpectedly quit after logging in. (39666451)
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I've had long-standing problems getting lldb to see local variables in many situations. For example, in this CBPeripheral delegate method,func peripheral(peripheral: CBPeripheral, didDiscoverCharacteristicsForService service: CBService, error: NSError?) { if case let .DiscoverCharacteristics(periph) = btState { if periph == peripheral { btState = .Connected(service) } } connectPeer() }the debugger doesn't see self or self.btState or even peripheral or periph. It doesn't matter if you try to access them through the Xcode UI or through the lldb command line. The specific error is use of unresolved identifier '***'.Is there any way around this situation? It's getting pretty frustrating. (This is Xcode 7 beta 3, btw.)
Known Issues Safari might quit unexpectedly when opening the Start Page if Frequently Visited Sites are visible as thumbnails. (63945984) Workaround: Make the window wider, hide the sidebar, or Control-click on Frequently Visited Sites and choose View as Icons.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
The same happening to me as well. Working fine on iOS 17.5 but not on iOS 18. Refer the below screen shot for iOS 18, whenever i try to hit the local in iOS 18 i gets the error popup saying - Webkit.Networking quit unexpectedly.
Topic:
Safari & Web
SubTopic:
General
Tags:
This issue is happened with me with MacBook Pro OS Sonoma 14.1.1 and 14.0. When I open the Apple Store and it's selected Discover, close the window, but its not happen for others options. Can you check it Apple?