Search results for

LLDB crash

29,557 results found

Post

Replies

Boosts

Views

Activity

Very slow initial expression evaluation in LLDB
In our project (~ 40.000 LOC) we experience a very slow initial expression evaluation when using commands like po myVariable in LLDB or breakpoint actions using @expr@: It often takes more than 20 seconds for initial evaluation, further evaulations then take only a fraction of a second.We think this is due to the unwinding of the app context and doing a expression -L swift -O -- myVariable in the background, as commands like frame variable myVariable are much faster also on first call (~ 100 ms).However, because of that using breakpoint actions is no fun, and as the codebase is not that big: Is there any way to determine the cause of these slow initial evaluations, e.g.- caused by embedded (Objective-)C(++) libraries- Access of specific frameworks like AVFoundation- ...Any help is appreciated.
0
0
1.6k
Aug ’17
Can't Simulate BgTaskScheduler to run the tasks in LLDB
` func submitBackgroundTasks() { // Declared at the Permitted background task scheduler identifiers in info.plist let backgroundAppRefreshTaskSchedulerIdentifier = com.FeedX.backgroundAlerts let timeDelay = 10.0 do { let backgroundAppRefreshTaskRequest = BGAppRefreshTaskRequest(identifier: backgroundAppRefreshTaskSchedulerIdentifier) backgroundAppRefreshTaskRequest.earliestBeginDate = Date(timeIntervalSinceNow: timeDelay) try BGTaskScheduler.shared.submit(backgroundAppRefreshTaskRequest) print(Submitted task request) } catch { print(Failed to submit BGTask) } } I am able to submit the task and hit the breakpoint but in the LLDB i try to simulate the task using the command e -l objc -- (void)[[BGTaskScheduler sharedScheduler] _simulateExpirationForTaskWithIdentifier:@com.FeedX.backgroundAlerts] But i get the following error : error: Error [IRForTarget]: Rewriting an Objective-C constant string requires CFStringCreateWithBytes Any idea on how to solve this or run the task using a different way? Thanks.
1
0
2.2k
Jan ’23
Reply to XCode 15: simple execv program exits with code 5 in the console.
Oh, you’re doing an exec* without a fork. That, and its reverse, presents unique challenges on macOS. If you run your test and then look in Console you’ll see that ls generated a crash report: Exception Type: EXC_CRASH (SIGTRAP) However, this doesn’t really tell you what’s gone wrong. My best guess si that this is related to the debugger. ls is a platform binary, and thus can’t be debugged: % lldb /bin/ls (lldb) target create /bin/ls Current executable set to '/bin/ls' (x86_64). (lldb) r error: process exited with status -1 … You’re trying to get to the same destination via a different route, and the system is blocking that as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Oct ’23
lldb fails to launch process: "Not allowed to attach to process"
Xcode 12.4 on Big Sur, a very basic attempt to launch and debug a process. Little-Net:host-osx minfrin$ lldb ./tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing (lldb) target create ./tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing Current executable set to '/Users/minfrin/src/redwax/open-eid/chrome-token-signing-trunk/host-osx/tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing' (x86_64). (lldb) process launch -i cert.native error: process exited with status -1 (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.)) Why would lldb, running as my local user, be unable
6
0
9.8k
Mar ’21
Reply to Application won't run GetDYLDEntryPointWithImage error
Hi Ben,Looks like you may still have old Xcode 6 runtimes on your system. You probably need to remove them from:~/Library/Developer/CoreSimulator/Profiles/RuntimesIn the 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.It's possible that your runtimes are in a different directory, but similar issues have been resolved by removing them.Max.
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’15
Can React Native's Metro and Xcode's LLDB interfere with each other
Trying to run a React Native app via Xcode can be very very very slow. Excruciatingly so. I often see messages saying things like Launching app is taking longer than expected. LLDB is likely reading from device memory to resolve symbols. But I see this all the time, if that's what it's doing it never finishes, and does it every time. This isn't just with one phone, its with several. Is it possible there some fundamental conflict between Xcode and LLDB and React Native Metro trying to communicate / load / debug / whatever that slows things down to a standstill?
2
0
916
Feb ’24
Reply to XCode 11.5 LLDB crashes on break point (reproducible)
Be aware that when debugging Swift apps, all the components with swift code need to be rebuilt locally. So make sure that when you are developing Pods, you don't download binaries but rather build all your Pods locally with the version of Xcode whose debugger you are using. If that doesn't fix the issue, can you file a report with the Apple Feedback system, including the example project that is crashing for you and the crash report for lldb-rpc-server? Thanks!
Jun ’20
LLDB Cannot Load ODBC Driver Due to Sandbox Restrictions - How to Debug
I'm developing a macOS console application that uses ODBC to connect to PostgreSQL. The application works fine when run normally, but fails to load the ODBC driver when debugging with LLDB(under root works fine as well). Error Details When running the application through LLDB, I get this sandbox denial in the system log (via log stream): Error 0x0 0 0 kernel: (Sandbox) Sandbox: logd_helper(587) deny(1) file-read-data /opt/homebrew/lib/psqlodbcw.so The application cannot access the PostgreSQL ODBC driver located at /opt/homebrew/lib/psqlodbcw.so(also tried copy to /usr/local/lib/...). Environment macOS Version: Latest Sequoia LLDB: Using LLDB from Xcode 16.3 (/Applications/Xcode16.3.app/Contents/Developer/usr/bin/lldb) ODBC Driver: PostgreSQL ODBC driver installed via Homebrew Code Signing: Application is signed with Apple Development certificate What is the recommended approach for debugging applications that need to load dynamic libraries? Are there specific entit
1
0
145
6d
Reply to I set AVVideoCodecTypeAppleProRes4444 and I get a AVVideoCodecTypeH264 movie
I have just discovered the cause of the trouble. If I added a soundtrack to the movie, the 4444ProRes codec unexpectedly turned into an H.264 codec. So, I have just replaced [[AVAssetExportSession alloc] initWithAsset:videoAudioComposition presetName:AVAssetExportPresetHighestQuality]; with [[AVAssetExportSession alloc] initWithAsset:videoAudioComposition presetName:AVAssetExportPresetAppleProRes4444LPCM]; and now it works well. I can quite get a movie with 4444 ProRes codec and the audio tracks. The only point I miss now is that the AVAssetExportPresetAppleProRes4444LPCM is available on macOS 10.15+. Which preset could I use on macOS 10.13 ?
Topic: Media Technologies SubTopic: Video Tags:
Jan ’21
Reply to SwiftUI Tutorial Application Alleged Incompatibility with macOS
Thanks for taking a look. It was Section 2, Step 4, having typed in the 'struct LandmarkRow_Previews ...' code that the problem occurred. I have re-opened the project and selected LandmarkRow view. The preview canvas states 'Preview paused'. Clicking the refresh arrow again throws the error Landmarks quit unexpectedly. Upon clicking 'Reopen', get You can't use this version of the application Landmarks with this version of macOS. I think I'd better try the tutorial again from scratch.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Sep ’22
Reply to [Resolved] App crashes when launched from dock, doesn't crash when run from terminal
Comically, my app does not crash when run from lldb or even when attached to lldb. Curious. This rules out most environmental issues. If you launch the app from Finder (or Dock, those are equivalent) it runs in the standard environment, and attaching with LLDB doesn’t change that.Two things:Please post a full crash report. Use the <> button to format it as code.Can you get a core dump? macOS does not enable core dumps by default but you can enable them from your app by running the following code at startup:struct rlimit limit; BOOL success = getrlimit(RLIMIT_CORE, &limit) >= 0; assert(success); limit.rlim_cur = limit.rlim_max; success = setrlimit(RLIMIT_CORE, &limit) >= 0; assert(success); Note It seems that, out of the box, 10.15 sets the permissions on /cores/ to drwxr-xr-x. For an app (not running as root) to generate a core this must be drwxrwxrwt. You can change this as follows: % sudo chmod 1777 /cores Don’t forget to change it back when y
Jan ’20
Multiple crash reports when running new app on Xcode 12 simulator
I create a new app in Xcode 12 and when I simulate the app on iphone Sim, Xcode doesn't crash but these are the errors I get each time I run the simulator... CalendarWidgetAppExtension quit unexpectedly. parsecd quit unexpectedly. healthappd quit unexpectedly. NewsTag quit unexpectedly. NewsToday2 quit unexpectedly. bulletindistributord quit unexpectedly. ProtectedCloudKeySyncing quit unexpectedly. ...all in succession. Anybody know how to fix this? Thanks in advanced...
3
0
3.2k
Oct ’20