pdb-files

Is it safe to manually generate .appxsym and .appxupload for Windows Store Apps crash analysis?

只谈情不闲聊 提交于 2019-12-05 12:21:52
We have an app with a manual packaging process (MakeAppx.exe). We would like to publish this app to the Store including the public symbols files, so that I can download the .cab process dump file for crash analysis ( such as described here ). I understand the .appxupload is a zip-file contaning the .appx package and an .appxsym file, which in turn is a .zip file containing the .pdb files ( also according to MSDN ). Is it safe to manually generate/edit these .appxsym and .appxupload for publishing? Yes. This is fine. As you note, the appxupload's format is documented as being a zip archive

Windows Debugging Symbols - Not Loading

拟墨画扇 提交于 2019-12-05 07:46:00
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 Studio (2008/2010) will not load symbols. While debugging, from Modules View, I select ntdll.dll and

VS2008 PDB file size limit redux: LNK1201, too

纵然是瞬间 提交于 2019-12-05 06:40:42
What is the size limit on PDB files in VS2k8? I am on a dev workstation with 3GB each of RAM and pagefile on a 32-bit PAE kernel, but the linker kicks out an LNK1201 error shortly after the PDB grows past 1GB. Is MSPDBSRV simply running out of address space? 来源: https://stackoverflow.com/questions/9162001/vs2008-pdb-file-size-limit-redux-lnk1201-too

How can I debug this error: 'Debugging information for iisexpress.exe cannot be found or does not match'?

試著忘記壹切 提交于 2019-12-05 05:22:04
I've been working on an MVC 5 code first project for a few months and (seemingly) out of nowhere, Visual Studio is refusing to debug and giving me some strange errors. When I try to run the application Ctrl + F5 it builds ok but the browser never gets beyond the loading stage, I still have the pinwheel in the browser tab, but the app never loads. When I try to debug the applicaiton F5 it builds ok, but then comes up with 2 errors, firstly Debugging information for iisexpress.exe cannot be found or does not match. Cannot find or open the PDB file. and then Process with an Id of xxxx is not

How to find corresponding .pdb inside .NET assembly?

杀马特。学长 韩版系。学妹 提交于 2019-12-05 05:06:36
Apparently, when a .NET assembly is created the location of the corresponding .pdb file path is included inside. Link for reference: https://msdn.microsoft.com/en-us/library/ms241613.aspx How do I access this? I have tried using ILSpy to look inside my assembly but could not find. You can use the dumpbin tool from a Developer Command Prompt, e.g. a cmd line like this dumpbin /HEADERS YourAssembly.exe would show the path to the PDB file in the Debug Directories section similar to this Microsoft (R) COFF/PE Dumper Version 14.00.24213.1 Copyright (C) Microsoft Corporation. All rights reserved.

Breakpoint in ASP.NET MVC Razor view will not be hit. No symbols have been loaded for this document

拈花ヽ惹草 提交于 2019-12-05 02:13:20
I can't get a breakpoint in a Razor view to be hit in Visual Studio 2013 while debugging in IIS Express. This is the view and unreachable breakpoint: Looking at the modules I see that the latest PDB file has been loaded: And the folder C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\53ff8402\967c7053\assembly\dl3\f3c59a34\6698ffde_b452cf01 has the latest version of the DLL and PDF files: ITVizion.VizionLogs.WeeklyLogs.Web.DLL ITVizion.VizionLogs.WeeklyLogs.Web.PDB I have already cleaned the solution, wiped the project's bin folder, restarted Visual Studio, etc but it

Is it possible to (re)create a PDB file after a DLL is made

喜夏-厌秋 提交于 2019-12-04 10:45:44
问题 I have the DLL and I have the exact sources used to create the DLL. I want our local symbol server to work when we get a dump file from customers. (Updating the DLL at the customer site can't be done before the next patch/release of our product) 回答1: That seems to be not possible. Have a look at this here: Why does Visual Studio require debugger symbol files to exactly match the binary files that they were built with? Or this article: PDB Files: What Every Developer Must Know Quote out of

How to match a crash's “Fault offset” to the source code?

杀马特。学长 韩版系。学妹 提交于 2019-12-04 03:43:01
问题 An EXE I compiled keeps crashing. I have the following info in the Event Viewer when it crashes: Exception code: 0xc0000008 Fault offset: 0x00000000000cb8e8 How do I match the "Fault offset" with my C++ code? There is a .PDB file in the Release folder, just not sure what steps to figure this out. 回答1: You also need to know what module the offset belongs too, if you are getting 0xC0000008 ( STATUS_INVALID_HANDLE ), then the exception is likely thrown from ntdll.dll, which isn't going to help

How can I inspect variable values while debugging MSVC ABI Rust programs?

蹲街弑〆低调 提交于 2019-12-04 00:10:49
问题 I've downloaded the MSVC ABI version of Rust 1.7.0 and followed the guessing game section from the docs. I notice that the builds use the native toolchain (Visual Studio 2015 Update 2 in my case) and therefore generate native PDBs (debugging symbols) consumable by native debuggers, such as WinDBG, CDB or the Visual Studio debugger. I can easily set breakpoints, step into standard library source and so on. What I cannot do is to inspect variable values. Regardless of the debugger used, the

Debugging with Pdb file and Source Code File in Visual Studio

一笑奈何 提交于 2019-12-03 14:14:52
问题 I have a web project that posts from client-side code to a method in external dll, which I have source code file and pdb file of this external dll. What I would like to do is to debug external dll using source code file and pdb. Visual studio does not stop to say no symbols are loaded for the module since. 回答1: To debug an dll a symbol file with the same version is allways needed. When you are debugging your own applications you usually don't have to care about this. But there are things