Xcode 11.4: Invalid debug info found, debug info will be stripped

Developer Tools & Services General
staninprague OP
Created Mar ’20
Replies 37
Boosts 0
Views 18k
Participants 28

I have a new warning per every target after upgrading to Xcode 11.4:


Invalid debug info found, debug info will be stripped


This has never been the case for my code base before. Anything I can do to resolve these warning? Am I safe to release to the AppStore with these warnings?


For one of the targets detailed info is:


mismatched subprogram between llvm.dbg.label label and !dbg attachment
  call void @llvm.dbg.label(metadata !137) #2, !dbg !203
label %138
double (i8*)* @"\01__hidden#1918_"
!137 = !DILabel(scope: !138, name: "zulu_time", file: !10, line: 196)
!138 = distinct !DISubprogram(name: "parseTimezone", scope: !10, file: !10, line: 161, type: !139, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !196)
!203 = !DILocation(line: 196, column: 1, scope: !100, inlinedAt: !101)
!100 = distinct !DISubprogram(name: "__hidden#1928_", scope: !10, file: !10, line: 161, type: !11, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6)
mismatched subprogram between llvm.dbg.label label and !dbg attachment
  call void @llvm.dbg.label(metadata !347), !dbg !371
label %55
i32 (i8*, ...)* @"\01__hidden#1920_"
!347 = !DILabel(scope: !348, name: "end_getDigits", file: !10, line: 140)
!348 = distinct !DISubprogram(name: "getDigits", scope: !10, file: !10, line: 109, type: !349, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !351)
!371 = !DILocation(line: 140, column: 1, scope: !315)
!315 = distinct !DISubprogram(name: "__hidden#1922_", scope: !10, file: !10, line: 109, type: !11, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6)
DICompileUnit not listed in llvm.dbg.cu
!171 = distinct !DICompileUnit(language: DW_LANG_C99, file: !7, producer: "Apple clang version 11.0.3 (clang-1103.0.32.29)", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug, enums: !12, retainedTypes: !172, imports: !180, nameTableKind: None)
ld: warning: Invalid debug info found, debug info will be stripped
!dbg attachment points at wrong subprogram for function
!126 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, s: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11)
double (%0*, i8*, %0*, i32)* @"\01__hidden#2776_"
  br i1 %41, label %42, label %90, !dbg !152, !llvm.loop !155
!156 = !DILocation(line: 283, column: 3, scope: !157)
!157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158)
!157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158)
ld: warning: Invalid debug info found, debug info will be stripped
mismatched subprogram between llvm.dbg.label label and !dbg attachment
Replies  37
Boosts  0
Views  18k
Participants  28
Universalis OP
May ’20

I have now distributed two apps with this warning, and they are working well with no evil consequences.

0
jasonmarr OP
May ’20

We're still seeing this error in our project when building with Xcode 11.5 GM. We're not able to provide the source code, but is there any way for us to determine what code is triggering this?


!dbg attachment points at wrong subprogram for function
!51 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11)
void (%3*, %0*, %0*, %0*, i32, %2*)* @"\01__hidden#6361_"
  br i1 %213, label %446, label %119, !dbg !83, !llvm.loop !276
!277 = !DILocation(line: 249, column: 2, scope: !278)
!278 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !279)
!278 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !279)
ld: warning: Invalid debug info found, debug info will be stripped
0
mstr OP
May ’20

I can share (its obj c), please contact me via my email.

0
Wizfinger OP
May ’20

Same here, also using Google Mobile Ads Framework.


However, the problem started AFTER I used the Product -> Analyze function. Before, no warnings, at all. After the analyze build, numerous "Invalid debug info" warnings appeared. Even after cleaning the build folder and the derived data folder, these warnings keep appearing.

0
lmDeveloper1 OP
Jun ’20

still occuring on archive in 11.5 , has anyone had a chance to see if its fixed in 11.6 beta?

2
TheHouseOfCode OP
Jun ’20
same issue here - GoogleCastSDK-ios-4.4.7 via CocoaPods!
0
keith OP
Jun ’20
I filed FB7746173 with a repro case
0
Developer Tools Engineer OP
Apple
Jun ’20
Xcode 12 Beta 1 includes fixes for these two issues:
You will need to recompile all of the code statically linked into your app to fix the "ld: invalid debug info found" error, including code statically linked from 3rd party libraries.



3
ovilla675 OP
Jul ’20
Is there any update? The XCode 11.6 still has the same behavior?
0
DTS Engineer OP
Apple
Jul ’20
@ovilla675, please see an earlier answer from a colleague -- the issue is addressed in the Xcode 12 betas.
0
dessa OP
May ’21
I'm getting this errors in 12.5 (M1) but not in 12.2 (Intel) , both stuck in "processing" on AppStoreConnect submit during thinning stage.
Adhoc export doesn't fail in 12.2 but fails in 12.5, but 12.2 does not help.

I'm stuck for a week now with no way to submit App with bitcode enabled( required for tvOS).
No external/third party frameworks are in the project.


_DICompileUnit not listed in llvm.dbg.cu

!143 = distinct !DICompileUnit(language: DW_LANG_C_plus_plus_11, file: !5, producer: "_hidden#39", isOptimized: true, runtimeVersion: 0, emissionKind: NoDebug, enums: !10, nameTableKind: None, sysroot: "_hidden#40", sdk: "_hidden#41")

ld: warning: Invalid debug info found, debug info will be stripped

DICompileUnit not listed in llvm.dbg.cu

!1429 = distinct !DICompileUnit(language: DW_LANG_C_plus_plus_11, file: !5, producer: "_hidden#39", isOptimized: true, runtimeVersion: 0, emissionKind: NoDebug, enums: !10, nameTableKind: None, sysroot: "_hidden#40", sdk: "_hidden#41")

ld: warning: Invalid debug info found, debug info will be stripped

DICompileUnit not listed in llvm.dbg.cu_

0
dessa OP
May ’21
The issue (DICompileUnit not listed in llvm.dbg.cu) was caused by Clang's

  • Rpass=loop-vectorize

option. I'm not clear why it would cause bitcode process to fail, since all appleTVs should support Neon instruction.
removing loop-vectorize has addressed it, but not optimal.
0
Xcode 11.4: Invalid debug info found, debug info will be stripped
First post date Last post date
 
 
Q