Search results for

LLDB crash

29,559 results found

Post

Replies

Boosts

Views

Activity

Reply to What is required to register for CoreWLAN events?
Sorry I was printing the localizedDescription of the error which isn't helpful at all. 😟So, this is what I Catch:(lldb) po errorError Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.airportd was invalidated. UserInfo={NSDebugDescription=The connection to service named com.apple.airportd was invalidated.}(lldb) po error.localizedDescriptionCouldn’t communicate with a helper application.
Topic: App & System Services SubTopic: Networking Tags:
Apr ’18
CFNetwork crash in iOS 11
We have an app that is working just fine in iOS 10, but crashes in iOS 11.I am currently trying to trace the problem, but the first crash is here; CFDataRef bodyData = CFHTTPMessageCopyBody( message ); CFHTTPMessageSetBody( newMessage, bodyData ); CFRelease( bodyData ); bodyData = NULL;It seems that I get a nil value from the CFHTTPMessageCopyBody in iOS 11, but not in iOS 10;From debugger;iOS 11(lldb) po message<CFHTTPMessageRef 0x1c417fbc0(0x1c417fbd0)> { GET request, url /873769144/sec/ENCRYPTED_Television*******_240516_1.mp4 -- http:/ (lldb) po bodyData<nil>(lldb) po newMessage<CFHTTPMessageRef 0x1c4360840(0x1c4360850)> { GET request, url http:/ ****iOS 10(lldb) po message<CFHTTPMessageRef 0x170173a40(0x170173a50)> { GET request, url /771278348/sec/ENCRYPTED_Television_**********_240516_1.mp4 -- http:/ (lldb) po bodyData<>(lldb) po newMessage<CFHTTPMessageRef 0x170173b00(0x170173b10)> { GET request,
Topic: App & System Services SubTopic: Networking Tags:
1
0
2.6k
Oct ’17
Reply to Impossible to use $R* variables after `continue` command
Edit: (lldb) b -[NSView hitTest:] Breakpoint 1: where = AppKit`-[NSView hitTest:], address = 0x0000000183857e18 (lldb) process launch -e /dev/null -- Process 4125 launched: '/System/Applications/Notes.app/Contents/MacOS/Notes' (arm64e) Process 4125 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1 frame #0: 0x000000018c093e18 AppKit` -[NSView hitTest:] AppKit`-[NSView hitTest:]: -> 0x18c093e18 <+0>: pacibsp 0x18c093e1c <+4>: sub sp, sp, #0x70 0x18c093e20 <+8>: stp x24, x23, [sp, #0x30] 0x18c093e24 <+12>: stp x22, x21, [sp, #0x40] 0x18c093e28 <+16>: stp x20, x19, [sp, #0x50] 0x18c093e2c <+20>: stp x29, x30, [sp, #0x60] 0x18c093e30 <+24>: add x29, sp, #0x60 0x18c093e34 <+28>: mov x19, x0 Target 0: (Notes) stopped. (lldb) p $arg1 (unsigned long) $2 = 4312972736 (lldb) po $2 (lldb) c Process 4125 resuming -- later Process 4125 stopped * thread #1, queue = 'com.apple.main-thread', stop
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jul ’23
Simulator SMS crash when testing sticker pack
BBuilt my first sticker pack following Apple Developer guidelines. Works fine on my physical iPhone, I can send any of my sticker designs via iMessage and the recepient sees them. If I use simulator of any iPhone model the iMessage app crashes as soon as my sticker pack loads and I receive and error that SMS unexpectedly quit. Any and all possible solutions or suggestions of what I should be looking for as a culprit much appreciated.
Topic: App & System Services SubTopic: General Tags:
1
0
705
Oct ’17
Calling `assetWriter.startWriting()` blocks all Threads for 3 seconds in debug (LLDB hang?)
’m using the AVFoundation Swift APIs to record a Video (CMSampleBuffers) and Audio (CMSampleBuffers) to a file using AVAssetWriter. Initializing the AVAssetWriter happens quite quickly, but calling assetWriter.startWriting() fully blocks the entire application AND ALL THREADS for 3 seconds. This only happens in Debug builds, not in Release. Since it blocks all Threads and only happens in Debug, I’m lead to believe that this is an Xcode/Debugger/LLDB hang issue that I’m seeing. Does anyone experience something similar? Here’s how I set all of that up: startRecording(...) And here’s the line that makes it hang for 3+ seconds: assetWriter.startWriting(...)
Topic: Media Technologies SubTopic: Photos & Camera Tags:
2
0
1k
Nov ’23
Reply to How to export debugging information for another developer
For an OS X app you can use the lldb.macosx.crashlog package, as described in Symbolicating with LLDB. I don’t know if this works in the iOS Simulator but it’s worth a try. Even if it doesn’t work, the package is written in LLDB’s scripting language, Python, so you can crib it for ideas as to how to move forward. If Xcode is installed in the default place, the path is /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/Python/lldb/macosx/. 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:
Dec ’15
Reply to Project Not Building- Xcode 10.1
Apparently I had set the data incorrectly. It builds now, reading:guard let userId = authResult?.user else { return } let userData: [String: Any] = [ firstName : , User ID : userId, dateCreated : FieldValue.serverTimestamp(), ] let db = Firestore.firestore() db.collection(users).document(one).setData(userData) { err in if let err = err { print(Error writing document: (err)) } else { print(Document successfully written!) } } } } }But, it crashes and gives a runtime error:@UIApplicationMain class AppDelegate: UIResponder, UIApplicationDelegate { //error: //libc++abi.dylib: terminating with uncaught exception of type NSException //(lldb) //3 comments above all one lineDo you know what this crash means?
Topic: Developer Tools & Services SubTopic: General Tags:
Nov ’18
Reply to LLDB Output less Helpful in Xcode 12.5
Is it worth filing a bug report without a sample project? I talked with the LLDB team about this and the answer was an emphatic “Yes!” So please file the bug with whatever info you have available. One thing you can do to help out here is enable LLDB’s logging and attach a log file to your bug report. First add this to your .lldbinit file: % cat ~/.lldbinit log enable -f /tmp/lldb.log lldb types expr I’m using /tmp/lldb.log but use whatever path works for you. If you’re using Xcode, make sure that lldb-rpc-server picks up this change. The easiest way to do that is to quit and relaunch Xcode. Finally, reproduce the problem and, once your done, gather up the log and attach it to your bug. Thanks in advance! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: Xcode Tags:
May ’21
Reply to 'XCUIElement' is not a member type of 'XCTest'
I had a very similar issue only when I try to print test related objects at the debugger prompt(but it works normally If I just run the test and don't breakpoint with the debugger)(I'm using Xcode 8.2.1)for example:I set a breakpoint just after this line: let app = XCUIApplication()and then try(lldb) po appexpression produced error: error: /var/folders/y0/1ghrk5gn4911s6kwq6n1ny8w0000gn/T/./lldb/2506/expr33.swift:1:72: error: 'XCUIApplication' is not a member type of 'XCTest'Swift._DebuggerSupport.stringForPrintObject(Swift.UnsafePointer<XCTest.XCUIApplication>(bitPattern: 0x1214213b0)!.pointee) ~~~~~~ ^but when I check debugDescription, it works(lldb) po app.debugDescriptionAttributes: Application 0x608000176500: {{0.0, 0.0},..then surprisingly, the same command that failed above works now successfully!(lldb) po appAttributes: Application 0x608000176500: {{0.0, 0.0}, {375.0, 667.0}}..I don't understand why, but it seems a workaround.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jan ’17
Reply to lldb KDK vs python
It seems rather determined to run python3:# /usr/bin/lldb -P/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python3# /usr/bin/lldb --versionlldb-1100.0.30.12Apple Swift version 5.1.3 (swiftlang-1100.0.282.1 clang-1100.0.33.15)However:# /Library/Developer/CommandLineTools/usr/bin/lldb -P/Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Resources/Python# /Library/Developer/CommandLineTools/usr/bin/lldb --versionlldb-1001.0.13.3 Swift-5.0# /Library/Developer/CommandLineTools/usr/bin/lldb /Library/Developer/KDKs/KDK_10.14.6_18G2016.kdk/System/Library/Kernels/kernel(lldb) target create /Library/Developer/KDKs/KDK_10.14.6_18G2016.kdk/System/Library/Kernels/kernelLoading kernel debugging from /Library/Developer/KDKs/KDK_10.14.6_18G2016.kdk/System/Library/Kernels/kernel.dSYM/Contents/Resources/Python/kernel.pyLLDB version lldb-1001.0.13.3 Swift-5.0settings set target.process.python-os-plugin-path /Libr
Topic: App & System Services SubTopic: Core OS Tags:
May ’20
popen() crash
I have a multithreaded application that uses popen() for system calls. Here is the snippet. I crashes in popen() (line 2 below). 1 fp = NULL; 2 if ((fp = popen(dnsCommand, r)) == NULL) { 3 logPrint(errno, *executeDNS: popen failed. Exiting...); 4 exitProcess(__func__, __LINE__); } I caught this under xcode debug and under cli lldb. To replicate it I have to let it run for several hours, and this functions is called repeatedly during that time. I can't really tell the exact conditions that cause the crash. The error messages is Thread 43: EXC_BAD_ACCESS (code=1, address=0x3010000080e) In this case dnsCommand is dnsCommand char [200] /Applications/NetBeez/bin/dig +noall +search +stats +comments xfinity.com 2>/dev/null Here is the backtrace (lldb) bt * thread #43, stop reason = EXC_BAD_ACCESS (code=1, address=0x3010000080e) * frame #0: 0x00007ff803997d22 libsystem_c.dylib`popen + 478 frame #1: 0x000000010004b53e nbagentgdb`executeDNS(param=0x0000000128900000) at executeDNS.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
11
0
1.6k
Mar ’23