Search results for

“LLDB crash”

30,536 results found

Post

Replies

Boosts

Views

Activity

Reply to error: Error reading commands from file lldbinit - file not found.
LLDB is the debugger underlying the Xcode debugger. The .lldbinit file is read by the debugger when it starts up. You can use it to customise the debugger. For example: % cat .lldbinit command alias btall thread backtrace all % lldb (lldb) help btall … 'btall' is an abbreviation for 'thread backtrace all' To learn more about how this works, see the lldb man page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: General Tags:
Sep ’24
Reply to lldb: argument starting with hash disappears.
I generally run a command with arguments using r: % lldb Test773781 (lldb) target create Test773781 ; (lldb) r arg1 #arg2 arg3 ; 0 …/Test773781 1 arg1 The interesting thing here is that LLDB has the right arguments: (lldb) settings show target.run-args target.run-args (arguments) = [0]: arg1 [1]: #arg2 [2]: arg3 It’s just not applying them at launch. Notably, the r command is an alias for process launch: (lldb) help r Launch the executable in the debugger. Syntax: r [] r [] 'r' is an abbreviation for 'process launch -X true --' Note that -X option. Its long name is --shell-expand-args. If you set it to false, it resolves this issue: (lldb) process launch -X false … 0 …/Test773781 1 arg1 2 #arg2 3 arg3 So it seems that LLDB’s shell-like argument expansion is interpreting the # as a comment. Fun times! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: General Tags:
Feb ’25
Reply to Debug Failed in Xcode Simulator
Thanks for the post, it seems like you are running a beta version of macOS. Can you please post the crash report from lldb? With that file, may I ask you to submit a bug? 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:
Feb ’25
Reply to dyld: Library not loaded: @rpath/libswiftCore.dylib
I am experiencing this exact issue too, and have tried almost all the suggested in the OP post to no avail.I have tried resintalling the WWDR cert and that does not help. I have also tried installing all the intermediate certs from Apple at http://www.apple.com/certificateauthority/Keychain Access evaluation of my developer cert for code signing passes.Performing the step- Set Embedded Content Contains Swift to YES (http://stackoverflow.com/questions/24002836/dyld-library-not-loaded-rpath-libswift-stdlib-core-dylib) does change the nature of the crash. After doing that, the crash output is just a non-informative (lldb) -- but typing bt after it yields:(lldb) bt* thread #1, stop reason = signal SIGABRT * frame #0: 0x0000000104e66f1c dyld`__abort_with_payload + 8 frame #1: 0x0000000104e666f4 dyld`abort_with_payload_wrapper_internal + 100 frame #2: 0x0000000104e66720 dyld`abort_with_payload + 12 frame #3: 0x0000000104e3c498 dyld`dyld::halt(char const*) + 312 frame #4: 0x000000
Topic: Programming Languages SubTopic: Swift Tags:
Oct ’17
Reply to Can not open a bundle signed for mac app distribution
I tested my app via TestFlight, and it does not open, so I'm not very optimistic Just to be clear, the TestFlight release of your app is not launching? If so, that’s something I can help you debug. Moreover, it’s important to debug this because it’s very likely that your final App Store release will behave exactly like your TestFlight release (if it doesn’t, that’s a bug on Apple’s part). When you try to launch your TestFlight release from the Finder, what happens? Does it start at all? Does it display a “you do not have permission to open” alert? Or a “quit unexpectedly” alert? Or does it hang on launch, bouncing forever in the Dock? Or start launching but then simple quit with no alerts? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App Store Distribution & Marketing SubTopic: General Tags:
Mar ’22
Reply to XProtect makes app hang when running an AppleScript
[quote='880167022, parker9, /thread/810258?answerId=880167022#880167022, /profile/parker9'] GitHub has the actual source for that version in Releases [/quote] OK. I downloaded the app, the .dSYM, and the source code and took a look. First, the crash report has this: Binary Images: 0x102c6c000 - 0x102c9ffff DIM arm64 <3e247524da7930099f63cd12ace4ab0e> …/DIM I used dwarfdump to confirm that I have the right .dSYM: % dwarfdump --uuid DIM.app/Contents/MacOS/DIM UUID: 7A4DAC69-55A2-3D1B-B9E0-6A14AB2D5EEA (x86_64) DIM.app/Contents/MacOS/DIM UUID: 3E247524-DA79-3009-9F63-CD12ACE4AB0E (arm64) DIM.app/Contents/MacOS/DIM I then symbolicated those frames: % atos -l 0x102c6c000 -o DIM.app.dSYM 0x102c799bc 0x102c8b4d4 closure #1 in ViewController.restore(_:) (in DIM) (ViewController.swift:207) thunk for @escaping @callee_guaranteed () -> () (in DIM) + 28 Plugging that into the backtrace, I get this: Thread 1 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 DIM … 0x102c6c000 + 55740 closure
Topic: Privacy & Security SubTopic: General Tags:
2w
System Information - Manage Storage Crash
Hi.Is anyone else experiencing crashes when attempting to manage storage through About This Mac > Storage > Manage?Every time I go into it the app attempts to collect/analyze data but never completes the Documents and System and ultimately crashes and I receive the standard, System Information Quit Unexpectedly message. Any feedback is appreciated.Thanks.
Topic: App & System Services SubTopic: Core OS Tags:
2
0
1.4k
Jul ’16
help lldb breakpoints not hit
I have a 2 machine setup with the target machine configred as followsnvram boot-args set to debug=0x814e kdp_match_name=firewire fwkdp=0x8000csrutil disabledThe debug versions of the kexts are transferred to the target machine, loaded and kextcache rebuiltsudo kextcache -system-prelinked-kernelOn the host machinefwkdp is runningFrom fwkpfv, the debug versions of the kexts are loaded as the added print statements are shown in the logsIn another terminal windowlldb /Library/Developer/KDKs/<KDK Version>/System/Library/Kernels/kernelkdp-remote localhost, drop the target machine into the debugger and connection is made.target modules add <kext_contents>target modules load --file <name> __TEXT <known_address_the_kext_uses>br set --name <method_name_to_break>br list shows that the breakpoint is resolvedcThe kext loads, executes and the breakpoint is not hit. Any ideas?ThanksDavid
Topic: App & System Services SubTopic: Core OS Tags:
1
0
987
Dec ’15
Help needed with lldb - attach to Mac after a kernel panic
I am trying to debug a kernel panic in our kext. I can attach to the target Mac over ethernet if I: cause an NMI using add an IOPanic call to my kext and cause it to be executed use Dtrace to invoke a panic However if I reproduce the kernel panic which I am investigating, the Mac just restarts. How can I make the Mac wait for me to attach with lldb rather than restarting? My target configuration is: Mac is 2021 M1 Pro 14 MacBook Pro macOS 14.2 (23C64) Network: Apple Thunderbolt 3 <-> Thunderbolt 3 adapter + Apple Thunderbolt 2 to ethernet adapters Boot-args = debug=0x44 wdt=-1 kdp_match_name=en8 (I have also tried debug=0x104C0C)
Topic: App & System Services SubTopic: Drivers Tags:
2
0
1k
Dec ’23
Reply to Please Help!!! My app crash at [UITableViewCellContentView dealloc]
I can locate the crash object, but I do not know why , do not know how to fix.it crash at :* frame #0: 0x0000000180eb9b90 libobjc.A.dylib`objc_msgSend + 16 frame #1: 0x00000001821f5934 Foundation`empty + 72 frame #2: 0x0000000182150cf8 Foundation`-[NSConcreteMapTable dealloc] + 60 frame #3: 0x0000000182198888 Foundation`-[NSISEngine dealloc] + 104 frame #4: 0x00000001869886dc UIKit`-[UIView dealloc] + 624 frame #5: 0x0000000186a8c4c0 UIKit`-[UITableViewCellContentView dealloc] + 80i print UITableViewCellContentView address and view:(lldb) register readGeneral Purpose Registers: x1 = 0x0000000187391ccc countByEnumeratingWithState:objects:count: x19 = 0x0000000128928270 x20 = 0x0000000126800048 x21 = 0x0000000126800010 x22 = 0x0000000126800000 x23 = 0x00000001a01d90e0 libsystem_pthread.dylib`_thread + 224 x24 = 0x0000000126800000 x25 = 0x00000000a1a1a1a1 x26 = 0x6000489658fc9aa6 x27 = 0x00000001a01d90e0 libsystem_pthread.dylib`_thread + 224 x28 = 0xa3a3a3a3a3a3a3a3 fp = 0x000000016fd6
Topic: Programming Languages SubTopic: General Tags:
Apr ’16
LLDB not loading all .dSYM's
I have a large application and do not have .dSYM's for all .dylibs. We have a critical component in which I have all of the .dSYM's, but I can not get XCode to load some (about 25% load) of the .dSYM's. I can manually load one .dSYM at a time using add-dsym, but that would take considerable time. I am using XCode 8.2.1 on Sierra.For example one of my .dylibs that where its .dSYM is not loaded had the following uuid : 7CB9B955-FC91-3E7C-BE63-F956F8D57D55:In terminal when I type mdfind and dwarfdump you can see that the uuid's match:mdfind com_apple_xcode_dsym_uuids == 7CB9B955-FC91-3E7C-BE63-F956F8D57D55/Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYMdlsept:~ dlsept$ xcrun dwarfdump --uuid /Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYMUUID: 7CB9B955-FC91-3E7C-BE63-F956F8D57D55 (x86_64) /Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYM/Contents/Resources
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
1.1k
Jun ’17
Reply to Crash reports downloaded by Xcode contain impossible call hierarchy
Would you mind opening an enhancement request for this, with both the crash log you have from the system and the one expanded by LLDB attached? (And please post the FB number here.) I'd like to treat this as a chance for improvement in the display of your crash log so that it was more intuitive to you what has happening. Speaking broadly and not specifically to your examples, backtraces in optimized builds sometimes are surprising because of the optimizations. That's not to say that the crash report is wrong — it is correct to the actual instructions addresses that the system called in backtrace order to the crash — but that it may have either more or fewer frames than you expect from the source code because of what the optimizations added or removed. That's why I want to be specific that the above enhancement request regards displaying the optimization info that you needed to understand what happened, and not that what the crash report recorded the wrong
Topic: Developer Tools & Services SubTopic: General Tags:
Mar ’25
Reply to crash report _NSThreadPerformPerform
In my little test app based on your crashing test code, I was able to successfully reproduce printing out the string pointed to by the x1 register.Cool. To quote Obi-Wan, “You’ve taken your first step into a larger world.”As an aside, I also tried printing out the SEL receiver object, which is supposedly stored in register x0 at the time of the crash.That won’t work, because the receiving object is allocated from the heap and thus is found at an (essentially) random place on each run of the app.Well now what? This is in UIKit.Right, but that shouldn’t stop you (-: To start, you can explore this by modifying your test app to use a UIKit selector. For example:@interface Hack : NSObject - (void)applicationWillTerminate:(id)sender; @end @implementation Hack - (void)applicationWillTerminate:(id)sender { NSLog(@well terminate request from %@, sender); } @end Hack * h = [[Hack alloc] init]; [h performSelector:@selector(applicationWillTerminate:) withObject:self afterDelay:0.1]; [h release]; [h release];A crash
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Nov ’16
Reply to error: Error reading commands from file lldbinit - file not found.
LLDB is the debugger underlying the Xcode debugger. The .lldbinit file is read by the debugger when it starts up. You can use it to customise the debugger. For example: % cat .lldbinit command alias btall thread backtrace all % lldb (lldb) help btall … 'btall' is an abbreviation for 'thread backtrace all' To learn more about how this works, see the lldb man page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’24
Reply to lldb: argument starting with hash disappears.
I generally run a command with arguments using r: % lldb Test773781 (lldb) target create Test773781 ; (lldb) r arg1 #arg2 arg3 ; 0 …/Test773781 1 arg1 The interesting thing here is that LLDB has the right arguments: (lldb) settings show target.run-args target.run-args (arguments) = [0]: arg1 [1]: #arg2 [2]: arg3 It’s just not applying them at launch. Notably, the r command is an alias for process launch: (lldb) help r Launch the executable in the debugger. Syntax: r [] r [] 'r' is an abbreviation for 'process launch -X true --' Note that -X option. Its long name is --shell-expand-args. If you set it to false, it resolves this issue: (lldb) process launch -X false … 0 …/Test773781 1 arg1 2 #arg2 3 arg3 So it seems that LLDB’s shell-like argument expansion is interpreting the # as a comment. Fun times! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Feb ’25
Photoshop 2021 crash after upgrading to Monterey
After i upgraded to the latest macOS i.e. Monterey, the Photoshop app started crashing and quits unexpectedly and this is happening every time I'm opening PS. Can anyone help me??
Topic: App & System Services SubTopic: Core OS Tags:
Replies
2
Boosts
0
Views
1.3k
Activity
Nov ’21
Reply to Debug Failed in Xcode Simulator
Thanks for the post, it seems like you are running a beta version of macOS. Can you please post the crash report from lldb? With that file, may I ask you to submit a bug? 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:
Replies
Boosts
Views
Activity
Feb ’25
Reply to dyld: Library not loaded: @rpath/libswiftCore.dylib
I am experiencing this exact issue too, and have tried almost all the suggested in the OP post to no avail.I have tried resintalling the WWDR cert and that does not help. I have also tried installing all the intermediate certs from Apple at http://www.apple.com/certificateauthority/Keychain Access evaluation of my developer cert for code signing passes.Performing the step- Set Embedded Content Contains Swift to YES (http://stackoverflow.com/questions/24002836/dyld-library-not-loaded-rpath-libswift-stdlib-core-dylib) does change the nature of the crash. After doing that, the crash output is just a non-informative (lldb) -- but typing bt after it yields:(lldb) bt* thread #1, stop reason = signal SIGABRT * frame #0: 0x0000000104e66f1c dyld`__abort_with_payload + 8 frame #1: 0x0000000104e666f4 dyld`abort_with_payload_wrapper_internal + 100 frame #2: 0x0000000104e66720 dyld`abort_with_payload + 12 frame #3: 0x0000000104e3c498 dyld`dyld::halt(char const*) + 312 frame #4: 0x000000
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Oct ’17
Reply to Can not open a bundle signed for mac app distribution
I tested my app via TestFlight, and it does not open, so I'm not very optimistic Just to be clear, the TestFlight release of your app is not launching? If so, that’s something I can help you debug. Moreover, it’s important to debug this because it’s very likely that your final App Store release will behave exactly like your TestFlight release (if it doesn’t, that’s a bug on Apple’s part). When you try to launch your TestFlight release from the Finder, what happens? Does it start at all? Does it display a “you do not have permission to open” alert? Or a “quit unexpectedly” alert? Or does it hang on launch, bouncing forever in the Dock? Or start launching but then simple quit with no alerts? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App Store Distribution & Marketing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’22
Reply to XProtect makes app hang when running an AppleScript
[quote='880167022, parker9, /thread/810258?answerId=880167022#880167022, /profile/parker9'] GitHub has the actual source for that version in Releases [/quote] OK. I downloaded the app, the .dSYM, and the source code and took a look. First, the crash report has this: Binary Images: 0x102c6c000 - 0x102c9ffff DIM arm64 <3e247524da7930099f63cd12ace4ab0e> …/DIM I used dwarfdump to confirm that I have the right .dSYM: % dwarfdump --uuid DIM.app/Contents/MacOS/DIM UUID: 7A4DAC69-55A2-3D1B-B9E0-6A14AB2D5EEA (x86_64) DIM.app/Contents/MacOS/DIM UUID: 3E247524-DA79-3009-9F63-CD12ACE4AB0E (arm64) DIM.app/Contents/MacOS/DIM I then symbolicated those frames: % atos -l 0x102c6c000 -o DIM.app.dSYM 0x102c799bc 0x102c8b4d4 closure #1 in ViewController.restore(_:) (in DIM) (ViewController.swift:207) thunk for @escaping @callee_guaranteed () -> () (in DIM) + 28 Plugging that into the backtrace, I get this: Thread 1 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 DIM … 0x102c6c000 + 55740 closure
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
System Information - Manage Storage Crash
Hi.Is anyone else experiencing crashes when attempting to manage storage through About This Mac > Storage > Manage?Every time I go into it the app attempts to collect/analyze data but never completes the Documents and System and ultimately crashes and I receive the standard, System Information Quit Unexpectedly message. Any feedback is appreciated.Thanks.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
2
Boosts
0
Views
1.4k
Activity
Jul ’16
help lldb breakpoints not hit
I have a 2 machine setup with the target machine configred as followsnvram boot-args set to debug=0x814e kdp_match_name=firewire fwkdp=0x8000csrutil disabledThe debug versions of the kexts are transferred to the target machine, loaded and kextcache rebuiltsudo kextcache -system-prelinked-kernelOn the host machinefwkdp is runningFrom fwkpfv, the debug versions of the kexts are loaded as the added print statements are shown in the logsIn another terminal windowlldb /Library/Developer/KDKs/<KDK Version>/System/Library/Kernels/kernelkdp-remote localhost, drop the target machine into the debugger and connection is made.target modules add <kext_contents>target modules load --file <name> __TEXT <known_address_the_kext_uses>br set --name <method_name_to_break>br list shows that the breakpoint is resolvedcThe kext loads, executes and the breakpoint is not hit. Any ideas?ThanksDavid
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
987
Activity
Dec ’15
Reply to iOS 10 device console not printing my app logs
if you attach to a process, the lldb not link the stderr and stdout, and the stdout stderr to link system logs db. you need close the tty stderr and stdout, then open a lldb tty
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
May ’20
Help needed with lldb - attach to Mac after a kernel panic
I am trying to debug a kernel panic in our kext. I can attach to the target Mac over ethernet if I: cause an NMI using add an IOPanic call to my kext and cause it to be executed use Dtrace to invoke a panic However if I reproduce the kernel panic which I am investigating, the Mac just restarts. How can I make the Mac wait for me to attach with lldb rather than restarting? My target configuration is: Mac is 2021 M1 Pro 14 MacBook Pro macOS 14.2 (23C64) Network: Apple Thunderbolt 3 <-> Thunderbolt 3 adapter + Apple Thunderbolt 2 to ethernet adapters Boot-args = debug=0x44 wdt=-1 kdp_match_name=en8 (I have also tried debug=0x104C0C)
Topic: App & System Services SubTopic: Drivers Tags:
Replies
2
Boosts
0
Views
1k
Activity
Dec ’23
Reply to Please Help!!! My app crash at [UITableViewCellContentView dealloc]
I can locate the crash object, but I do not know why , do not know how to fix.it crash at :* frame #0: 0x0000000180eb9b90 libobjc.A.dylib`objc_msgSend + 16 frame #1: 0x00000001821f5934 Foundation`empty + 72 frame #2: 0x0000000182150cf8 Foundation`-[NSConcreteMapTable dealloc] + 60 frame #3: 0x0000000182198888 Foundation`-[NSISEngine dealloc] + 104 frame #4: 0x00000001869886dc UIKit`-[UIView dealloc] + 624 frame #5: 0x0000000186a8c4c0 UIKit`-[UITableViewCellContentView dealloc] + 80i print UITableViewCellContentView address and view:(lldb) register readGeneral Purpose Registers: x1 = 0x0000000187391ccc countByEnumeratingWithState:objects:count: x19 = 0x0000000128928270 x20 = 0x0000000126800048 x21 = 0x0000000126800010 x22 = 0x0000000126800000 x23 = 0x00000001a01d90e0 libsystem_pthread.dylib`_thread + 224 x24 = 0x0000000126800000 x25 = 0x00000000a1a1a1a1 x26 = 0x6000489658fc9aa6 x27 = 0x00000001a01d90e0 libsystem_pthread.dylib`_thread + 224 x28 = 0xa3a3a3a3a3a3a3a3 fp = 0x000000016fd6
Topic: Programming Languages SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’16
LLDB not loading all .dSYM's
I have a large application and do not have .dSYM's for all .dylibs. We have a critical component in which I have all of the .dSYM's, but I can not get XCode to load some (about 25% load) of the .dSYM's. I can manually load one .dSYM at a time using add-dsym, but that would take considerable time. I am using XCode 8.2.1 on Sierra.For example one of my .dylibs that where its .dSYM is not loaded had the following uuid : 7CB9B955-FC91-3E7C-BE63-F956F8D57D55:In terminal when I type mdfind and dwarfdump you can see that the uuid's match:mdfind com_apple_xcode_dsym_uuids == 7CB9B955-FC91-3E7C-BE63-F956F8D57D55/Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYMdlsept:~ dlsept$ xcrun dwarfdump --uuid /Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYMUUID: 7CB9B955-FC91-3E7C-BE63-F956F8D57D55 (x86_64) /Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYM/Contents/Resources
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
0
Boosts
0
Views
1.1k
Activity
Jun ’17
Reply to Crash reports downloaded by Xcode contain impossible call hierarchy
Would you mind opening an enhancement request for this, with both the crash log you have from the system and the one expanded by LLDB attached? (And please post the FB number here.) I'd like to treat this as a chance for improvement in the display of your crash log so that it was more intuitive to you what has happening. Speaking broadly and not specifically to your examples, backtraces in optimized builds sometimes are surprising because of the optimizations. That's not to say that the crash report is wrong — it is correct to the actual instructions addresses that the system called in backtrace order to the crash — but that it may have either more or fewer frames than you expect from the source code because of what the optimizations added or removed. That's why I want to be specific that the above enhancement request regards displaying the optimization info that you needed to understand what happened, and not that what the crash report recorded the wrong
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’25
Reply to crash report _NSThreadPerformPerform
In my little test app based on your crashing test code, I was able to successfully reproduce printing out the string pointed to by the x1 register.Cool. To quote Obi-Wan, “You’ve taken your first step into a larger world.”As an aside, I also tried printing out the SEL receiver object, which is supposedly stored in register x0 at the time of the crash.That won’t work, because the receiving object is allocated from the heap and thus is found at an (essentially) random place on each run of the app.Well now what? This is in UIKit.Right, but that shouldn’t stop you (-: To start, you can explore this by modifying your test app to use a UIKit selector. For example:@interface Hack : NSObject - (void)applicationWillTerminate:(id)sender; @end @implementation Hack - (void)applicationWillTerminate:(id)sender { NSLog(@well terminate request from %@, sender); } @end Hack * h = [[Hack alloc] init]; [h performSelector:@selector(applicationWillTerminate:) withObject:self afterDelay:0.1]; [h release]; [h release];A crash
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Nov ’16