ArgumentNullException reading PDB symbols

Extracted from issue https://github.com/xamarin/xamarin-macios/issues/12306

The exception occurs when processing System.Void Abp.Auditing.AuditingInterceptor/<InternalInterceptAsynchronous>d__61::MoveNext()`

This is not something the SDK can “catch-and-continue”.

It’s possible this is a corrupted PDB but it happened on more than one version (6.4 and 6.3.1) of the ABP package.

It also happens without Xamarin.iOS using Cecil 0.11.4 (have not tried any older version, or main branch).

An unhandled exception of type 'System.ArgumentNullException' occurred in Mono.Cecil.dll: 'Value cannot be null.'
   at Mono.Cecil.Cil.SequencePoint..ctor(Int32 offset, Document document)
   at Mono.Cecil.SignatureReader.ReadSequencePoints(Document document)
   at Mono.Cecil.MetadataReader.ReadSequencePoints(MethodDefinition method)
   at Mono.Cecil.Cil.PortablePdbReader.ReadSequencePoints(MethodDebugInformation method_info)
   at Mono.Cecil.Cil.PortablePdbReader.Read(MethodDefinition method)
   at Mono.Cecil.Cil.CodeReader.ReadMethodBody()
   at Mono.Cecil.Cil.CodeReader.ReadMethodBody(MethodDefinition method)
   at Mono.Cecil.MetadataReader.ReadMethodBody(MethodDefinition method)
   at Mono.Cecil.MethodDefinition.<>c.<get_Body>b__41_0(MethodDefinition method, MetadataReader reader)
   at Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TRet& variable, TItem item, Func`3 read)
   at Mono.Cecil.MethodDefinition.get_Body()
   at <Program>$.<<Main>$>g__Process|0_0(TypeDefinition type) in /Users/poupou/git/spouliot/dotnet-tools/cecil-pdb-check/Program.cs:line 29
   at <Program>$.<<Main>$>g__Process|0_0(TypeDefinition type) in /Users/poupou/git/spouliot/dotnet-tools/cecil-pdb-check/Program.cs:line 25
   at <Program>$.<Main>$(String[] args) in /Users/poupou/git/spouliot/dotnet-tools/cecil-pdb-check/Program.cs:line 17

Abp.zip

[jbevain]

Thanks for filing this and for the repro, I’ll have a look pronto. Merci!

[spouliot]

https://github.com/icsharpcode/ILSpy/issues/2823 , while a different issue (and stack trace) that happens after ILSpy reprocessed the .pdb file, leads to the same issue.

A bit tragic considering that the app is not actually linked (but reuse the linker pipeline) so the PDB should not even be loaded…