LLDB crash

I want to do source level debugging of an external environment using Xcode's graphical debugger. I have an External Build System project with local source files that builds libraries/executables (not macOS or iOS) and creates their dSYM symbol files (also stored locally). I have a script that I can run from Xcode that starts the library/executables (in an external environment), and gets their slide addresses so their symbols can be loaded into lldb. The script also returns a gdb-remote url that I can use with lldb to begin debugging. Is there a way for Xcode to use the lldb info gathered by my script to start its graphical debugger? If this feature doesn't exist, then I see two simple ways that this feature could be implemented: a) In the Run Action, there's a Run Script action in the Pre-actions to start the remote environment and gather the debug info to create a lldb script that has the gdb-remote command, and commands to add the target modules, and to load the target mo

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

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?

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/

Hey! I am writing type formatting scripts in Python for lldb, as described in https://lldb.llvm.org/use/variable.html#python-scripting. I'm trying to pass an environment variable to lldb from Xcode to determine the path to the scripts in the project root, so the project is not bound to some predetermined path. I am having trouble doing this in Xcode. What I have tried: lldbinit file Create a .lldbinit file in $(SRCROOT) with the following content: platform shell echo $SRCROOT. Set the path to the .lldbinit file in Edit Scheme... > Info > LLDB Init File ($(SRCROOT)/.lldbinit). Set the SRCROOT environment variable to $(SRCROOT) in Edit Scheme... > Arguments > Environment Variables. entry-point breakpoint Add a breakpoint to the entry-point of the application. Set the Automatically continue after evaluating actions option. Add the action platform shell $(SRCROOT) or platform shell $SRCROOT. Set the SRCROOT environment variable to $(SRCROOT) in Edit Scheme... > Arguments

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 'xxx'.Is there any way around this situation? It's getting pretty frustrating. (This is Xcode 7 beta 3, btw.)

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.