Following the instructions found here as well as around the Developer Forums, I've successfully managed to begin debugging my system extension on a virtual machine. Unfortunately, after archiving my system extension and copying over the .app file to my virtual machine, my .app loses access to the source code (on my host machine) and hitting any beak points via lldb yields me hard-to-read assembly code. How do I also get source code when attaching lldb to a system extension?
Search results for
LLDB crash
29,557 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I facing issues in Xcode 8 while trying to execute the application. I am using Xcode Version 8.3.2 (8E2002) and Swift 3 for creating the project and when i try to run the application it is getting installed in the iPhone simulator but displays an error message in the console window as mentioned below.Warning: Error creating LLDB target at path '/Users/anand/Library/Developer/Xcode/DerivedData/Dicee-gslmyrsjbqfaecdnquedjgmlmxwj/Build/Products/Debug-iphonesimulator/Dicee.app'- using an empty LLDB target which can cause slow memory reads from remote devices. error: failed to launch '53355'Kindly provide solution to the above error.
Hi, I installed command line tools using command xcode-select --install in Catalina. I could not find 'lldb-server' in path /Library/Developer/CommandLineTools in Catalina. I could find lldb-server at below path in Mojave /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/ Please guide me how to install lldb-server in Catalina as I require it for remote debugging. Regards
Looks like a bug, not new....See https://stackoverflow.com/questions/43635522/what-is-lldb-rpc-server-when-does-it-crash-in-xcode-why-it-crashesIf you take the time to file one, be sure to add your report # to your thread for reference, thanks and good luck.Ken
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I am running the most up to date version of Xcode (v10.1 (10B61)) on a High Sierra system (10.13.6 (17G10021)) and find that compiling for macOS will work, but not visually display in the sumulator. I get the LLDB message: unable to attach. Advice online suggested submitting new security certificates, which I have done, but still the simulator will not show up, even though the code compiles.
Signal 6 is SIGABRT, which likely means that something called abort() in your app. When this happens and you get that message in Xcode, you can review the thread backtraces in the debugger to see what aborted. Alternatively, you can enter the LLDB command detach, which will detach the debugger, and allow the app to continue to crash using normal means, resulting in a crash report that you can then review. — Ed Ford, DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
Xcode
I recently had to kernel debug my kext again. It used to have all symbols available while kernel debugging an earlier 10.11 a while ago.I build my kext with dwarf-with-dsym against an 10.9 SDK and I am assuming my build settings are OK, since it used to work.When connecting to the panic'd system, I do (or - more precicly my script does):(lldb) target create /Library/Developer/KDKs/KDK_10.11.3_15D13b.kdk/System/Library/Kernels/kernelwarning: 'kernel' contains a debug script. To run this script in this debug session: command script import /Library/Developer/KDKs/KDK_10.11.3_15D13b.kdk/System/Library/Kernels/kernel.dSYM/Contents/Resources/DWARF/../Python/kernel.pyTo run all discovered debug scripts in this session: settings set target.load-script-from-symbol-file trueCurrent executable set to '/Library/Developer/KDKs/KDK_10.11.3_15D13b.kdk/System/Library/Kernels/kernel' (x86_64).(lldb) settings set target.load-script-from-symbol-file trueLoading kernel debugging from /Library/Developer/KDKs/KDK
I have do this.If I take the name from my storyboard and run the app, crash and sgabrt.If I take the name Main, I becoes this error:2015-08-22 09:47:35.911 Kapitel2[1168:47555] [+] <ViewController: 0x7ba78de0>.writeLog:(lldb)So whats now?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
@DTS Engineer On disabling the signal handler I was able to get a crash report. ... which suggests you have a Mach exception handler that’s active even with your signal handler disabled. Is it possible to disable that? No, the exception handler is crucial to the operation of the product. Remember this is a language. We produce compiled code, catch exceptions on behalf of users, etc. This has been part of the product since the first version, in MacOS 10.0. For example, in Common Lisp, we have an API for virtual multi-threading and that facility uses the exception handler for its operation. That feature cannot be turned off. Our application is not a normal application. We have an entire programming system inside our product, and that includes catching exceptions and dealing with them programmatically. Implementing a Mach exception handler correctly is really hard, We agree. We would be happy to send you the source code for it, but we don't want to post it here. This exception handler is as old as MacOS
Topic:
App & System Services
SubTopic:
Networking
Tags:
Hello. I am currently developing a C++ application for x86_64 using XCode, and I am experiencing the same problem as described in the following link. https://discourse.llvm.org/t/lldb-doesnt-stop-on-sigabrt-assert-with-x86-executable-on-apple-arm/69749/1 Due to this bug, when the application crashes, it is difficult to tell which source code caused the crash, and this is reducing our development efficiency. How can this be fixed? Thank you in advance for your help.
Not sure it's your problem, but the latest beta release notes say this... SwiftUI ...Known Issues ......ProgressView generic type signature has changed, adding the ProgressViewStyleConfiguration.CurrentValueLabel generic parameter. This change does not require any source changes, but will cause apps you compile using an earlier beta SDK to quit unexpectedly. (63580200) You might want to file bugs and wait for next beta/release.
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
I'm using Xcode 12 beta 3. When running my Apple Watch's target on WatchOS 7, I get this error: Warning: Error creating LLDB target at path '/Users/evan/Library/Developer/Xcode/DerivedData/audigo-cneguthkmmoulfgcprsazbryrlrl/Build/Products/Debug-watchsimulator/AudigoWatchApplication.app'- using an empty LLDB target which can cause slow memory reads from remote devices. I know this error use to be when running 32 bit frameworks on 64 bit devices, but I'm not doing that. Is this a bug? Or is there a setting I don't know of that needs to be updated?
OS X v10.11 Developer beta Release notes Known IssuesXcode 6.x has known compatibility issues when run on OS X El Capitan. It is strongly encouraged that you use Xcode 7 when running on OS X El Capitan.Xcode processes may quit unexpectedly if older iOS Simulator runtimes (Xcode 6.x) are present on disk.seems pretty clear to me
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Same here: lldb started crashing with simulator on encountering breakpoints, as of right now it even seems to crash reliably after some time. It seems to work properly on physical device Sequoia 15.4, XCode 16.2, iPhone 16 pro simulator 18.2 If that matters: I use github copilot xcode extension and that one also has issues => chat assistant crashes a lot and forces me to relaunch xcode every couple requests report.txt
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi,I'm just starting to learn Swift and in the Playground area, I have come to a little problem.This is my code:/ import UIKit var str = Hello, playground class Person { init (){ println(A new person has been created) } func sayCheese(){ println(Cheese!) } } var b = Person() b.sayCheese()At line 17. adn 16. it says __lldb_expr_54.Person - I'm not really sure what this means but to my prior coding knowledge, there shoudl't be anything wrong? Unless C is very different to Java.Would really help if you could explain what is wrong and why its wrong!Thanks