symbol-server

Issue pushing symbol packages to Symbol Server

拥有回忆 提交于 2020-01-13 19:11:45
问题 I installed a Symbol Server (following this post: http://www.xavierdecoster.com/setting-up-your-own-symbolsource-server-step-by-step) and push symbol packages to that server. It has been worked so far. But then when I upgraded my machine to Windows 10 & Visual Studio 2015 Enterprise Edition, I can't push my symbol packages (build with VS2015) to symbol server any more. I've tried to search around but don't see any solution fit with my issue This is the issue when I've tried to run push

WinDbg, display Symbol Server paths of loaded modules (even if the symbols did not load)?

给你一囗甜甜゛ 提交于 2020-01-04 09:27:53
问题 Is there a way from WinDbg, without using the DbgEng API, to display the symbol server paths (i.e. PdbSig70 and PdbAge) for all loaded modules? I know that lml does this for the modules whose symbols have loaded. I would like to know these paths for the symbols that did not load so as to diagnose the problem. Anyone know if this is possible without having to utilize the DbgEng API? edited: I also realize that you can use !sym noisy to get error messages about symbols loading. While this does

WinDbg, display Symbol Server paths of loaded modules (even if the symbols did not load)?

懵懂的女人 提交于 2020-01-04 09:27:36
问题 Is there a way from WinDbg, without using the DbgEng API, to display the symbol server paths (i.e. PdbSig70 and PdbAge) for all loaded modules? I know that lml does this for the modules whose symbols have loaded. I would like to know these paths for the symbols that did not load so as to diagnose the problem. Anyone know if this is possible without having to utilize the DbgEng API? edited: I also realize that you can use !sym noisy to get error messages about symbols loading. While this does

Azure DevOps SourceLink and Symbol Server with Release DLL in Nuget package

有些话、适合烂在心里 提交于 2019-12-24 03:37:14
问题 I have a .NET Standard 2.0 TestSouceLink project with the following configuration in the .csproj : <PropertyGroup> <TargetFramework>netstandard2.0</TargetFramework> <RestoreProjectStyle>PackageReference</RestoreProjectStyle> <Authors>Jérôme MEVEL</Authors> <Description>Just a test package for SourceLink</Description> <Version>1.1.1</Version> <PublishRepositoryUrl>true</PublishRepositoryUrl> <EmbedUntrackedSources>true</EmbedUntrackedSources> </PropertyGroup> <PropertyGroup Condition="'$

Windows Debugging Symbols - Not Loading

二次信任 提交于 2019-12-22 05:16:13
问题 I am having Windows 7 x64 SP1. I have downloaded symbols from: http://msdn.microsoft.com/en-us/windows/hardware/gg463028 I have downloaded and installed x64 RTM and x64 SP1 symbols for Windows 7 x64 SP1. Installed on T:\Symbols folder. But When I debug a 64-bit native C++ application, the symbols would not load at all. For ntdll.dll , for instance, the PDBs are located in: T:\Symbols\ntdll.pdb\6192BFDB9F04442995FFCB0BE95172E12 T:\Symbols\ntdll.pdb\CFF40300FD804691B73E12CF2A150EE02 But Visual

How to debug into my nuget package deployed from TeamCity?

旧时模样 提交于 2019-12-17 08:05:18
问题 I have put a library that my team uses into a nuget package that is deployed from TeamCity into a network folder. I cannot debug into this code though! SymbolSource is one solution I have read about but I would much rather find some way to have access to the .pdb/source files directly from Teamcity. Does anyone know how to do this? Edit. When I check 'Include Symbols and Source' in the Nuget Pack build step TeamCity creates a .Symbol.nupkg in addition to the .nupkg file in the network folder.

Why is VS giving me Disassembly when I have the .Net debug symbols?

别说谁变了你拦得住时间么 提交于 2019-12-13 06:14:15
问题 I'm trying to get to the bottom of an annoying problem with EventViewer, so I've hooked up an instance of VS (2013) to mmc.exe and breaking on exceptions. VS only gives me the disassembly, even though it's pointing at System.IO.Path.CheckInvalidPathChars(string) , and the Modules window says that mscorlib.dll (2.0) is loaded with the symbol file (twice, as it happens, once in DefaultDomain, and once in EventViewer domain). Failing that, could anyone help me work out what the offending Path is

What is the difference in TFS 2010 between a source server and symbol server?

痴心易碎 提交于 2019-12-11 06:05:55
问题 I have read a couple of posts for instance... http://blogs.msdn.com/b/adamroot/archive/2009/06/17/source-server-and-symbol-server-features-in-team-foundation-server-2010-beta-1.aspx http://blogs.msdn.com/b/jimlamb/archive/2009/06/15/symbol-and-source-server-in-tfs-2010.aspx From what I have read these are both useful server applications to setup for better debugging support when dealing with older versions of applications that require analysis. In the first link the msdn blogger mentions that

Are the VS2015 64-bit MFC symbols on the Microsoft Symbol Server?

时光怂恿深爱的人放手 提交于 2019-12-08 06:52:50
问题 I'm trying to debug a crash/minidump from a customer who was running 64-bit software. The symbols for mfc140u.dll are not loading even though I'm downloading from the "Microsoft Symbols Servers" in Symbol Settings. Looking at the symbol cache, the PDBs for mfc140u.i386 are available. Is there any way to confirm these symbols are available from that server? Are there instructions to get them from somewhere else that I need to find? In C:\Windows\System32 the mfc140u.dll is version 14.0.23918.0

Are the VS2015 64-bit MFC symbols on the Microsoft Symbol Server?

夙愿已清 提交于 2019-12-07 04:11:27
I'm trying to debug a crash/minidump from a customer who was running 64-bit software. The symbols for mfc140u.dll are not loading even though I'm downloading from the "Microsoft Symbols Servers" in Symbol Settings. Looking at the symbol cache, the PDBs for mfc140u.i386 are available. Is there any way to confirm these symbols are available from that server? Are there instructions to get them from somewhere else that I need to find? In C:\Windows\System32 the mfc140u.dll is version 14.0.23918.0. The dump file is looking for version 14.00.23506.0. The symbols for these DLLs are also not loading: