Xcode downloaded client crash report at libsecinit_appsandbox.c

Question

Created 2w

Replies 2

Boosts 0

Participants 2

Among the newest crash reports downloaded by Xcode for my App Store app there is one that contains a single thread, crashed at libsecinit_appsandbox.c, without any trace of my app name. What could possibly cause such a crash? Is this something related with app signing? The app has been on the App Store for a long time and this never happened to me.

Thread 0 Crashed:
0   libsystem_secinit.dylib       	0x00000001941dcfcc _libsecinit_appsandbox.cold.12 + 60 (libsecinit_appsandbox.c:454)
1   libsystem_secinit.dylib       	0x00000001941dbf94 _libsecinit_appsandbox + 1764 (libsecinit_appsandbox.c:454)
2   libsystem_trace.dylib         	0x00000001872be598 _os_activity_initiate_impl + 64 (activity.c:131)
3   libsystem_secinit.dylib       	0x00000001941db85c _libsecinit_initializer + 80 (libsecinit_initializer.c:17)
4   libSystem.B.dylib             	0x00000001941f2664 libSystem_initializer + 280 (init.c:338)
5   dyld                          	0x00000001871fe608 invocation function for block in dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const::$_0::operator()() const + 168 (Loader.cpp:2198)
6   dyld                          	0x000000018723cd6c invocation function for block in dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const + 340 (MachOAnalyzer.cpp:2481)
7   dyld                          	0x0000000187230400 invocation function for block in dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const + 496 (MachOFile.cpp:1669)
8   dyld                          	0x00000001871df2fc dyld3::MachOFile::forEachLoadCommand(Diagnostics&, void (load_command const*, bool&) block_pointer) const + 300 (MachOFile.cpp:1185)
9   dyld                          	0x000000018722f394 dyld3::MachOFile::forEachSection(void (dyld3::MachOFile::SectionInfo const&, bool, bool&) block_pointer) const + 192 (MachOFile.cpp:1628)
10  dyld                          	0x000000018723c880 dyld3::MachOAnalyzer::forEachInitializer(Diagnostics&, dyld3::MachOAnalyzer::VMAddrConverter const&, void (unsigned int) block_pointer, void const*) const + 516 (MachOAnalyzer.cpp:2448)
11  dyld                          	0x00000001871fa53c dyld4::Loader::findAndRunAllInitializers(dyld4::RuntimeState&) const + 564 (Loader.cpp:2189)
12  dyld                          	0x00000001872042d4 dyld4::PrebuiltLoader::runInitializers(dyld4::RuntimeState&) const + 44 (PrebuiltLoader.cpp:818)
13  dyld                          	0x000000018721dcc0 dyld4::APIs::runAllInitializersForMain() + 84 (DyldAPIs.cpp:3889)
14  dyld                          	0x00000001871e4010 dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 3156 (dyldMain.cpp:891)
15  dyld                          	0x00000001871e2ef4 start + 1868 (dyldMain.cpp:1265)

Crash report

Boost

Answer 1

DTS Engineer OP

Apple

2w

I talk about this crash extensively in Resolving App Sandbox Inheritance Problems, part of the Resolving Trusted Execution Problems sequence.

Such problems are usually 100% reproducible for any given signing setup [1]. Given that there’s just one instance of this, I suspect it’s something to do with that specific user’s Mac. If you’re in touch with the affected user, you could dig into this further. If not, I think it’s fine to let this slide unless you see additional reports.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] That is, you might see difference between debug and release signed products, but for a particular product the problem will happen either always or never.

0

Answer 2

Nickkk OP

2w

Given that there’s just one instance of this, I suspect it’s something to do with that specific user’s Mac.

Thanks, that's what I suspected. It's not always easy to find information about crashes that apparently have nothing to do with your own code.

0