debug-symbols | 易学教程

Using nuget & Symbols servers

阅读更多关于 Using nuget & Symbols servers

问题 I must be doing it wrong. I am using VS2012, c#. I am using nuget to manage my packages. Previously I always created an 'External References' directory and managed packages myself. I decided to now follow the new way of package management. Anyway, nuget is working a treat. I have it setup so that packages are not included in svn (code repository) and that missing packages get downloaded if required. All works, for all developers on my team and also on our Team City box. Problem comes when I

Serialize execution of symstore via Powershell or BATCH

阅读更多关于 Serialize execution of symstore via Powershell or BATCH

问题 We are working to integrate a step into our continuous integration (CI) server (CruiseControl.NET). We want to register the debug symbols *.pdb generated from our build process into a Microsoft Symbol Server. As implemented by Microsoft, a symbol server is a directory structure Visual Studio uses to find the *.pdb debug symbols for C++/C# executables. Microsoft provides a command symstore that takes debug symbols in one directory and populates the central symbol store directory as appropriate

How to get a Windows symbol server set up

阅读更多关于 How to get a Windows symbol server set up

问题 I have a spare server on the network that I'd like to have host all of our build symbols. I already know how to set up a symbol cache on my local development system and pointing my debugger (e.g. Windbg) to that path in 'Symbol File Path'. I presumed that I could do the same with another system on the network that has its own symbol cache (e.g. \\host\symbols). I set up the server and enabled file sharing on the directory, so I'm able to access it remotely through Windows Explorer. However,

Is there a known issue relating to Windows 7 Kernel Symbols?

阅读更多关于 Is there a known issue relating to Windows 7 Kernel Symbols?

I have a few Windows 7 machines that I am not able to read their memory dumps. I found something that I suspect may be related, but am not positive: https://twitter.com/aionescu/status/634028737458114560 I also found this: http://support.microsoft.com/kb/2528507 However, the scenario message regarding wow64exts given in the doc is not seen in any of my dumps. I also cannot apply that hotfix at this time to test it. So I'm just looking for some more information or opinions. I'm able to open any other OS dump as well as my own system's Windows 7 dump, but there are 2 other machines that run Win

Getting rid of “There is no source code available for the current location.”

阅读更多关于 Getting rid of “There is no source code available for the current location.”

问题 OK, this is my own fault, but I can't seem to rescue myself. Whenever I try to step into a class that has fields with assignments calling into .NET code, I get a dialog box that contains the text "There is no source code available for the current location.": For instance, stepping into the constructor of the following class would give me the above message: public class Test { private Stack<String> _Dummy = new Stack<String>(); public Test() { } } I assume this is because at some point I

Release generating .pdb files, why?

阅读更多关于 Release generating .pdb files, why?

Why does Visual Studio 2005 generate the .pdb files when compiling in release? I won't be debugging a release build, so why are they generated? Cody Gray Because without the PDB files, it would be impossible to debug a "Release" build by anything other than address-level debugging. Optimizations really do a number on your code, making it very difficult to find the culprit if something goes wrong (say, an exception is thrown). Even setting breakpoints is extremely difficult, because lines of source code cannot be matched up one-to-one with (or even in the same order as) the generated assembly

How to disassemble one single function using objdump?

阅读更多关于 How to disassemble one single function using objdump?

问题 I've got a binary installed on my system, and would like to look at the disassembly of a given function. Preferrably using objdump , but other solutions would be acceptable as well. From this questions I've learned that I might be able to disassemble part of the code if I only know the boundary addresses. From this answer I've learned how to turn my split debug symbols back into a single file. But even operating on that single file, and even disassembling all the code (i.e. without start or

How to tell if a .NET application was compiled in DEBUG or RELEASE mode?

阅读更多关于 How to tell if a .NET application was compiled in DEBUG or RELEASE mode?

I have an application installed on my computer. How do I find out if it was compiled in DEBUG mode or not? I've tried to use .NET Reflector , but it does not show anything specific. Here is what I see: // Assembly APPLICATION_NAME, Version 8.0.0.15072 Location: C:\APPLICATION_FOLDER\APPLICATION_NAME.exe Name: APPLICATION_NAME, Version=8.0.0.15072, Culture=neutral, PublicKeyToken=null Type: Windows Application I blogged this a long time ago, and I don't know if it still valid or not, but the code is something like... private void testfile(string file) { if(isAssemblyDebugBuild(file)) {

Should I compile release builds with debug info as “full” or “pdb-only”?

阅读更多关于 Should I compile release builds with debug info as “full” or “pdb-only”?

问题 In Visual Studio 2010 for a C# project, if you go to Project Properties > Build > Advanced > Debug Info you have three options: none, full, or pdb-only. Based on the answer to this question, I believe I understand some of the differences between full and pdb-only. However, which is more appropriate for a release build? If I use \"full\" will there be performance ramifications? If I use \"pdb-only\" will it be harder to debug production issues? What is the difference between \"full\" and \

Release generating .pdb files, why?

阅读更多关于 Release generating .pdb files, why?

问题 Why does Visual Studio 2005 generate the .pdb files when compiling in release? I won\'t be debugging a release build, so why are they generated? 回答1: Because without the PDB files, it would be impossible to debug a "Release" build by anything other than address-level debugging. Optimizations really do a number on your code, making it very difficult to find the culprit if something goes wrong (say, an exception is thrown). Even setting breakpoints is extremely difficult, because lines of