hello everybody, someone can help me pleaseim making a timer app, and i wanted to add a sound (bip) but i have an error and i cant resolves it : http://rvo.li/OUHSGE2
Search results for
LLDB crash
29,559 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
//Set Up Search Bar let searchBar = resultSearchController!.searchBar searchBar.sizeToFit() searchBar.placeholder = Search For Locations And Places navigationItem.titleView = resultSearchController?.searchBar //UISearchController Set UpI'm fairly new to coding, so I'm not exactly sure what the issue is. I'm getting the error on the first line of code whenever I run my app. I thought it was the ? in the last line of code was the problem causing this, but when I replaced it with ! like the first line, it still didn't work. I tried replacing the ! with a ? and it didn't work either. I'm not sure how to solve this. I feel like it may have something to do with the first and last line though. Can anybody maybe explain this to me and help me solve to understand better?Thanks so much.-Deb
Xcode comes with its own version of Python, including a copy of six, for the benefit of LLDB and others. For Xcode 11.3 this is at /Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/site-packages/six.py. I’m not sure why lldb isn’t picking up that version. What version of macOS are you running? And what version of Xcode? Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
For me the code is in the app. (lldb) po rv error: expression failed to parse: error: :3:1: error: cannot find 'rv' in scope rv ^~ (lldb) fr v rv (WhatSize.SideBarItemReducer.State) rv = // the code I'm trying to debug let rv = SideBarItemReducer.State.init(item: item) .preserveUIState(sideBarItemState) return rv What's not so funny is that rv has the proper data in the Variables View, but I love command line short cuts. Not a show stopper but a huge annoyance. Xcode 14.3.1 (14E300c) Thanks.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Thanks so much for the post. When running swift-healthcheck in lldb, does it display any errors such as “Missing Swift module or Clang module found”? Ensure that you do not have any missing modules for lldb to function properly. If swift-healthcheck returns without any errors, it may indicate a bug that we need to investigate. In such a case, would you be so kind as to file a bug report? Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
Worldwide Developer Relations.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
crashReport.txt Can you help with determining what is cause of the crash in this crash report
Furthermore, we have devised another approach to addressing the LLDB problem. We have crafted a script that momentarily alters the mach_type of all frameworks to dynamic (where it's possible) for the purpose of debugging.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi JohannesIf you pause your app (in the debugger) after dismissing the modal view controller and run the command `(lldb) po [[[UIApplication sharedApplication] keyWindow] recursiveDescription]`, what is the output?
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
I see very similar error messages when I try to get symbols for a kernel crash. I have the gut feeling that it is related to the fact that my host machine is an Intel one and the target is an Apple Silicon or maybe because my host OS is Catalina. % lldb /Library/Developer/KDKs/KDK_11.2.3_20D91.kdk/System/Library/Kernels/kernel (lldb) target create /Library/Developer/KDKs/KDK_11.2.3_20D91.kdk/System/Library/Kernels/kernel Loading kernel debugging from /Library/Developer/KDKs/KDK_11.2.3_20D91.kdk/System/Library/Kernels/kernel.dSYM/Contents/Resources/Python/kernel.py LLDB version lldb-1200.0.44.2 Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1200.0.32.28) settings set target.process.python-os-plugin-path /Library/Developer/KDKs/KDK_11.2.3_20D91.kdk/System/Library/Kernels/kernel.dSYM/Contents/Resources/Python/lldbmacros/core/operating_system.py settings set target.trap-handler-names hndl_allintrs hndl_alltraps trap_from_kernel hndl_double_fault hndl_machine_chec
Topic:
App & System Services
SubTopic:
Drivers
Tags:
I submitted a bug report for this, but posting here as well hoping for some answers. There is a regression in macOS 11 in which TCC automatically denies privacy access by default when an executable is run from the lldb debugger, if the executable needs privacy access for folders like Desktop. Expected behavior: In macOS 10.15, building an executable that lives in the Desktop folder and running it in the debugger causes a privacy dialog to appear, prompting for access to the Desktop folder This is expected because hash is regenerated with every build Actual behavior: However, in macOS 11, the behavior has changed - instead of a privacy dialog appearing, no dialog appears, and privacy access is immediately denied by default. When run from the Desktop, the executable fails to run with the error “file system sandbox blocked open()”. However, if the executable is compiled and run from the /tmp directory, the executable runs normally without error, although we don’t get a privacy dialog like we do in macOS
Then I used Xcode 15.4 to built and generated .ipa again. There are .symbols files inside Symbols folder in ipa(.zip) as before, but MyApp.xcarchive/dSYMs is also empty. I'm surprised by this. Can you check the value of the DEBUG_INFORMATION_FORMAT build setting, and see if it's set to DWARF with dSYM File for your Release build. That's the standard set up for Release builds, while Debug builds default to DWARF, so there is no dSYM file. One other thing to look at is if your Archive action in Xcode is set to use your Release configuration, or if it's set to a Debug configuration. That configuration detail is found in your scheme configuration, under Archive. Additionally, could you also please kindly tell me why are there two kinds of files for generating crash reports? (.symbols files and dSYM file), do they have different aims? The dSYM file contains extremely detailed information in DWARF that enables debugging your app in minute detail, thus powering the experience of everything you can do with LLDB
Topic:
Developer Tools & Services
SubTopic:
Xcode
Yes, I am using LLDB. So, to be clear, you’re running a program in Xcode and thus using Xcode’s built-in LLDB to debug it? Right? As opposed to running the program using the lldb command line tool? Assuming that, you’re correct that Xcode’s console panel does not map ^C to SIGINT. I have a bunch of hints and tips on this front. The traditional BSD approach for this is to use SIGINFO rather than SIGINT. You can generate that in Terminal using ^T. Of course, Xcode’s console panel doesn’t support that either (-: To get around this, run your program with its standard I/O channels connect to a Terminal window. To do this, go to Product > Scheme > Edit Scheme > Run > Options and change Console from Use Xcode to Use Terminal. You’ll also need to disable SIGINFO handling in LLDB: (lldb) process handle -p true -s false -n false SIGINFO When SIGINT is received by the program, I want to print out a simple string. Example: Your example is not safe because it calls
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Receiving this message after waiting a while: warning: libobjc.A.dylib is being read from process memory. This indicates that LLDB could not find the on-disk shared cache for this device. This will likely reduce debugging performance.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Sorrry, that was wrong.Now I write there Main, without storyboard.And I become this error:2015-08-22 10:37:15.331 Kapitel2[1352:62128] [+] <ViewController: 0x79c22120>.writeLog:(lldb)
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Also, if you try to use the NSDiffableDataSourceSnapshotReference that is passed to your delegate in controller(_, didChangeContentWith:), you get all sorts of type errors which seem to indicate a problem with how this type is imported into Swift:(lldb) po snapshot.sectionIdentifiers Precondition failed: NSArray element failed to match the Swift Array Element type Expected NSManagedObjectID but found __NSCFConstantString: … (lldb) po snapshot.itemIdentifiers Precondition failed: NSArray element failed to match the Swift Array Element type Expected NSString but found NSTemporaryObjectID_0: …This lets me think that NSDiffableDataSourceSnapshotReference<NSManagedObjectID, NSString> should probably be NSDiffableDataSourceSnapshotReference<NSString, NSManagedObjectID>.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags: