LLDB crash

You mean this:2015-08-22 13:33:34.040 Kapitel2[1461:81250] [+] <ViewController: 0x7a726d00>.writeLog:(lldb)

Is it possible to configure Xcode, so the the lldb always does the process handle SIGTERM --stop false --pass true? When launching the app inside Xcode? instead of always having to type in the process handle SIGTERM --stop false --pass true everytime (it's getting a bit tedious to re-type this everytime you CMD+R the app, when you are testing that it's handling the signals correctly ....) Would be nice if there was a setting in inside Xcode, that you could configure the lldb with what you want it to do each time.

The same issue for me, I'm trying to debug the net core application on mac and see error: (lldb) process attach -p 3304 error: attach failed: attach failed (Not allowed to attach to process. Look in the console messages (Console.app), near the debugserver entries when the attached failed. The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.) Running lldb with sudo not helping to me.

The program might be using a deprecated API, such as NSCountWindows which can cause that os_log message to appear in the console. Try compiling with -Wdeprecated-declarations enabled, and clean up the code that is using deprecated APIs. Alternatively, in your lldb, you can set a breakpoint (lldb) b libsystem_trace.dylib``_os_log_error_impl (only one backtick; concession to the forum formatting) and when that gets hit you can look up the callstack to figure out what in your code triggered the os_log message.

[quote='788982022, vojta.bohm, /thread/756097?answerId=788982022#788982022, /profile/vojta.bohm'] Right now it seems I have a remnant. [/quote] Yeah, this is tricky on macOS because app extensions are embedded in apps and apps can be placed anywhere on the system. Sometimes you can fix things using the lsregister tool to tell the system where the app is and the pluginkit tool to manipulate the appex database. [quote='788977022, vojta.bohm, /thread/756097?answerId=788977022#788977022, /profile/vojta.bohm'] crash upon stepping over or upon usage of lldb. [/quote] If you choose Process > Detach, does it crash? And do you get a crash report? Hmmm, another way I’ve found of dealing with this is to create a dummy ‘appex host’ app target in my appex project. I then target that rather than the Finder. The app is development signed, and thus avoids all the attachment drama associated with the Finder. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let

That's exactly what I did, and it fixed the compilation problems. But to make sure what I'm fixing for iOS15 doesn't break iOS14, I installed iOS14.5 runtime in Xcode 13, and that's where the problem occurs. I can successfully compile the app, but at runtime, the 14.5 simulator crashes with: dyld: Library not loaded: /System/Library/Frameworks/_CoreData_CloudKit.framework/_CoreData_CloudKit Referenced from: /Users/andrei/Library/Developer/CoreSimulator/Devices/8554B734-4894-4DD0-A8FA-6C20983F3A49/data/Containers/Bundle/Application/29E251FD-B330-4B30-B3B8-22A86C2961A8/***.app/*** Reason: image not found (lldb)

I couldn't find the NSInvalidArgumentException that you refer to on Frame 2? To determine this I did the following:I built a simple test app and ran it on a device with the same OS version installed.To confirm that I was looking at exactly the right code, I compared the UUID from Binary Images section of the full crash report to the result of the LLDB image list command.I disassembled the frame 2 method, -[UIViewController _presentViewController:withAnimationController:completion:], focusing on the code at offset 4936, to determine what exception it threw.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

After hours and days of attempting to narrow down the cause, after I remove all zsh customizations (in dotfiles) on an account, the LLDB Swift debugging finally works again. Swift structure state can be inspected, and po symbol works. (the lldb startup error Cannot create Swift scratch context (couldn't create a ClangImporter) is gone too) I haven't isolated the specific root cause of why this is, but that is the general case.

Thanks for the tip, although I guess this isn't particularly helpful:(lldb) po [_moveArea _whyIsThisViewNotFocusable]ISSUE: This view returns NO from -canBecomeFocused.

Also, is there a better way of getting the line number from the address than using lldb or objdump to disassemble with lines? ;) It's hit and miss, unfortunately.

Hello Quinn, Thank you for your reply. In the interim, others have contributed, and my questions have largely been addressed. We do not have a specific issue or use case at the moment; rather, we were seeking clarification on the behavior as it was not entirely clear to us. It is crucial for us to understand the intended behavior of TCC. Following your suggestion to wriker, I ran the above test program in LLDB from the command line. Interestingly, the program can open the file successfully if the binary has FDA, despite neither LLDB nor Terminal having FDA.

Hi Wen,I'm experiencing the same problem with iOS 10 in both the Beta 1 and 2. I would suggest filing a Radar to get Apple's attention on this because ot seems to be an issue with the Javascript evaluation. I had the same problem trying to get any Javascript response with UIWebView. Ran inside the webViewDidFinishLoad:(lldb) po [webview stringByEvaluatingJavaScriptFromString:@window;] <object returned empty description>(lldb) po [webview stringByEvaluatingJavaScriptFromString:@window.body] <object returned empty description>(lldb) po [webview stringByEvaluatingJavaScriptFromString:@window.document.getElementById('body').offsetHeight;] <object returned empty description>However, I have noticed that the following JavaScriptFromString works: NSString *webViewHeight = [webView stringByEvaluatingJavaScriptFromString:@document.body.scrollHeight;]; //then convert it to a floatValue self.webViewHeight = [webViewHeight floatValue];I hope this helps.Adam Govan