Search results for

LLDB crash

29,559 results found

Post

Replies

Boosts

Views

Activity

Reply to Under stress tests, our Network Extension crashed due to QOS?
Anything I should look for or do, other than telling lldb to attach to the correct pid, and wait for a crash? That’s the obvious place to start. If you want to write more code you could: Investigate core dumps. Install a SIGABRT signal handler than stops the process to allow you to attach. Disable SIP and start messing around with DTrace. We might get to that point, but they all see like overkill right now. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Feb ’24
Reply to URL in scene openURLContexts does not exist
Thanks for pointing out my error. Unfortunately I'm still getting the same results with the correct separator: (lldb) po FileManager.default.fileExists(atPath: /private/var/mobile/Library/Mobile Documents/) true (lldb) po FileManager.default.fileExists(atPath: /private/var/mobile/Library/Mobile Documents/com~apple~CloudDocs) false (lldb) po FileManager.default.fileExists(atPath: url.path) false To try to determine that this wasn't just a LLDB issue, I updated my code slightly: func scene(_ scene: UIScene, openURLContexts URLContexts: Set) { guard let url = URLContexts.first?.url else { os_log(URL in %@ is nil, #function) return } let fileExists = FileManager.default.fileExists(atPath: url.path) fileExists is false after AirDropping a file. And of course this is happening within the method where openURLContexts is passed as an argument, and therefore the URL should be valid. So I'm still stuck at the same place.
Topic: UI Frameworks SubTopic: UIKit Tags:
Jul ’25
How to get my extension’s process ID of the dext for debugging with lldb
I've asked this question in Stackoverflow, but no response, so I ask for help in here. I follow this guide Debugging and testing system extensions, and try to debug my dext code. In the Attach the debugger to your system extension, it said After your system extension launches, run the ps command-line tool and note your extension’s process ID. This is the current output for my dext status % systemextensionsctl list 1 extension(s) --- com.apple.system_extension.driver_extension enabled active teamID bundleID (version) name [state] * * K3TDMD9Y6B com.accusys.scsidriver (1.0/1) com.accusys.scsidriver [activated enabled] and I used the ps command but nothing happen, I can not get my extension’s process ID. ps aux | grep com.accusys.scsidriver or ps -ef | grep com.accusys.scsidriver How to do that? Any suggestion is appreciated.
1
0
623
Dec ’24
Reply to error: type for self cannot be reconstructed: type for typename
I also have a lot of logs like this when app becomes paused by lldb: /Users/egormerkushev/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/23S4HX6OW8E8S/MyModule-2XYB5G9W7D2Z.pcm is out-of-date (hash mismatch). Type information from this module may be incomplete or inconsistent with the rest of the program. Rebuilding the project will regenerate the needed module files. When I try print something I get it: (lldb) po self 0x000000015d9de300 (lldb) po self.dismissGestureRecognizer error: type for self cannot be reconstructed: type for typename $s5MyModule31FullscreenContentViewControllerCD was not found (cached) error: Couldn't realize Swift AST type of self. Hint: using `v` to directly inspect variables and fields may still work.
Oct ’24
LLDB bug in macOS 10.15 where privacy access dialog appears while debugging executables
I submitted a bug report for this, but posting here as well hoping for some answers. There is a bug in macOS 10.15 (specifically, I am using 10.15.5) in which a privacy access dialog appears when debugging an executable in lldb. Expected behavior: When debugging an app that lives in the Desktop folder, the process runs as expected without any privacy dialogs appearing. Therefore, we expect the same behavior when debugging regular (non-app) C++ executables; i.e. when debugging the executable, no privacy dialogs should appear Actual behavior: When debugging a plain C++ executable that lives in the Desktop folder, a privacy dialog to appear appears when the process starts, prompting for access to the Desktop folder This is unexpected and frustrating because it also prevents us from being able to debug executables through ssh (reported in FB7778150)
1
0
629
Jul ’20
iTunes 12.2.2 crashes after launch
I've been having real issues with iTunes since upgrading to iTunes 12.2 and OS X El Capitan 10.11 Beta.I can launch iTunes and it will then attempt to connect to iTunes Store. iTunes will then crash and ask to send a report. Afterwards, if I try to launch iTunes again it crashes immediately. I have updated iTunes to the 12.2.2 release and I am having the same issues as before.The crash report says iTunes quit unexpectedly while using the libgnsdk_dsp.3.06.1.dylib plug-in.My library is stored an external SSD card permanently connected to my MacBook. Before upgrading to both iTunes 12.2 and OS X El Capitan 10.11 Beta I had no issues with iTunes.I have tried reinstalling iTunes but this has not solved the problem. I can't try and restore from a back-up as the latest back up I have is to old.Any suggestions??
4
0
2.9k
Aug ’15
Reply to forking lldb to get a complete backtrace
I gave up on running lldb as a sub-process (even after giving it permissions to attach, it causes lldb, debugserver, and Activity Monitor to hang with 100% CPU). Instead I use something like the above with /usr/bin/sample to get a backtrace when an assertion fails in my debug builds. (spindump must be run as root, so it is useless here)
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’22
Reply to Impossible to use $R* variables after `continue` command
This is working for me. Consider tiny command-line tool program: import Foundation class Main { func run() { print(Hello Cruel World!) } } func main() { let m = Main() m.run() withExtendedLifetime(m) { dispatchMain() } } main() I set a breakpoint on the first line of run(). I then ran the program and printed self: (lldb) p self (xxst.Main) $R0 = 0x0000600000008030 {} (lldb) p $R0 (xxst.Main) $R1 = 0x0000600000008030 {} I continued and, after a second, paused the program again. This command fails: (lldb) p $R0 error: expression failed to parse: error: :1:1: use of undeclared identifier '$R0' $R0 ^ because the language is wrong. But this command works: (lldb) expression --language swift -- $R0 (xxst.Main) $R2 = 0x0000600000008030 {} macOS: 13.4.1 (22F82) Xcode Version 14.3.1 Ditto. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Jul ’23
Reply to iOS - uninvoked signal handlers
Thanks for your response.I totally thought lldb would pass on signals to my process! Thank you for pointing out this isn't the case - asking lldb to do so fixed everything. Feel foolish now.As for your earlier question, I'm using signals to notify me when my aio_read() completes. I know there are other options, but from my understanding, this API has the lowest overhead. Building game engine, and this is part of the platform-side of the asset system.
Jul ’16
Reply to CoreML Instrument Requires get-task-allow Entitlement
Not entirely sure what should happen, but I get this: ❯ lldb env/bin/python (lldb) target create env/bin/python Current executable set to '/path/to/env/bin/python' (arm64). (lldb) r Process 33134 launched: '/path/to/env/bin/python' (arm64) Process 33134 stopped * thread #2, stop reason = exec frame #0: 0x0000000100014a40 dyld`_dyld_start dyld`: -> 0x100014a40 <+0>: mov x0, sp 0x100014a44 <+4>: and sp, x0, #0xfffffffffffffff0 0x100014a48 <+8>: mov x29, #0x0 0x100014a4c <+12>: mov x30, #0x0 Target 0: (Python) stopped. (lldb) Separately, I tried signing my python binary like this: ❯ cat entitlements.xml com.apple.security.get-task-allow ❯ codesign -f -s - env/bin/python --entitlements entitlements.xml env/bin/python: replacing existing signature ❯ codesign -d -vv env/bin/python --entitlements - Executable=/opt/homebrew/Cellar/python@3.10/3.10.12_1/Frameworks/Python.framework/Versions/3.10/bin/python3.10 Identifier=python3-555549447295e55955d43a
Topic: Code Signing SubTopic: Entitlements Tags:
Oct ’23