Error indexing symbol PDB for .NET CLI builds

When using the dotnet CLI to build my projects, if I add the .pdb from the build to an artifact, my builds will bombs when indexing symbols.

It happens on any dotnet CLI build. Here is the error it shows:

[13:00:27] Indexing sources appeared in file C:\Path\To\Build\Agent\work\bbf3b6247c4755da\bin\Release\netstandard2.0\pdb_prob.pdb
[13:00:27] No source information found in pdb file C:\Path\To\Build\Agent\work\bbf3b6247c4755da\bin\Release\netstandard2.0\pdb_prob.pdb
[13:00:27] Running command C:\Path\To\Build\Agent\plugins\symbol-server\bin\JetBrains.CommandLine.Symbols.exe dumpSymbolSign /o=C:\Path\To\Build\Agent\temp\buildTmp\symbol-signature-local-7827415357241066277.xml /i=C:\Path\To\Build\Agent\temp\globalTmp\dumpSymbolSign5120566798333481555.input
[13:00:27] Stdout: Dumped 1 signature entries to the file C:\Path\To\Build\Agent\temp\buildTmp\symbol-signature-local-7827415357241066277.xml
[13:00:27] Error occurred while processing symbols file C:\Path\To\Build\Agent\work\bbf3b6247c4755da\bin\Release\netstandard2.0\pdb_prob.pdb
[13:00:27] Error message is logged
[13:00:27] java.lang.NullPointerException
at jetbrains.buildServer.symbols.PdbSignatureIndexUtil.extractGuid(PdbSignatureIndexUtil.java:54)
at jetbrains.buildServer.symbols.PdbSignatureIndexUtil.read(PdbSignatureIndexUtil.java:32)
at jetbrains.buildServer.symbols.SymbolsIndexer.getPdbSignature(SymbolsIndexer.java:233)
at jetbrains.buildServer.symbols.SymbolsIndexer.processPdbArtifacts(SymbolsIndexer.java:197)
at jetbrains.buildServer.symbols.SymbolsIndexer.afterCollectingFiles(SymbolsIndexer.java:177)
at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at jetbrains.buildServer.util.EventDispatcher$3.run(EventDispatcher.java:126)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:71)
at jetbrains.buildServer.util.EventDispatcher.dispatch(EventDispatcher.java:120)
at jetbrains.buildServer.util.EventDispatcher$2.invoke(EventDispatcher.java:70)
at com.sun.proxy.$Proxy36.afterCollectingFiles(Unknown Source)
at jetbrains.buildServer.agent.impl.artifacts.ArtifactsBuilder.processArtifacts(ArtifactsBuilder.java:67)
at jetbrains.buildServer.agent.impl.artifacts.ArtifactsBuilder.build(ArtifactsBuilder.java:54)
at jetbrains.buildServer.agent.impl.artifacts.ArtifactProcessor.processArtifacts(ArtifactProcessor.java:136)
at jetbrains.buildServer.agent.impl.artifacts.ArtifactProcessor.addNewArtifactsPath(ArtifactProcessor.java:100)
at jetbrains.buildServer.agent.impl.buildStages.finishStages.PublishArtifactsFStage.doFinishStage(PublishArtifactsFStage.java:54)
at jetbrains.buildServer.agent.impl.buildStages.BuildFinishStagesExecutor.runFinishStage(BuildFinishStagesExecutor.java:28)
at jetbrains.buildServer.agent.impl.buildStages.BuildFinishStagesExecutor.doBuildFinishStages(BuildFinishStagesExecutor.java:20)
at jetbrains.buildServer.agent.impl.BuildRunActionImpl.runBuild(BuildRunActionImpl.java:63)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.doActualBuild(BuildAgentImpl.java:295)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.access$100(BuildAgentImpl.java:53)
at jetbrains.buildServer.agent.impl.BuildAgentImpl$1.run(BuildAgentImpl.java:259)
at java.lang.Thread.run(Thread.java:745)
[13:00:27] Symbols weren't found in artifacts to be published.
[13:00:27] Publishing collected binary files signatures.

 

I do have the build fail when `an error message is logged by build runner`, and I'd rather not disable that.

0
2 comments
Avatar
Permanently deleted user

Also, we're running TeamCity Enterprise 2017.2.1 (build 50732). The Symbol Server plugin version is 2017.1.4. Also, this problem occurs even when the symbol files indexer build feature is not on the build.

0
Avatar
Permanently deleted user

The following command line parameters on the build step seem to have solved our problems: `/p:DebugSymbols=true /p:DebugType=pdbonly`

0

Please sign in to leave a comment.