windbg

ERROR: Symbol file could not be found. windbg.exe

女生的网名这么多〃 提交于 2019-12-02 18:18:33
I downloaded the symbols from http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx the package (Windows 7 RTM x86 retail symbols, all languages) but it still gives me the same error! Done .sympath but still not working .sympath C:\inetpub\wwwroot\ProductsService\bin\ProductsEntityModel.pdb;srv c:\Symbols http://msdl.microsoft.com/download/symbols Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved.

_NT_SYMBOL_PATH format

喜欢而已 提交于 2019-12-02 17:06:55
I'm trying to use windbg more, and I keep having problems with the symbol cache. It isn't clear to me what the format of the string is supposed to be. I have a few requirements: use Microsoft's server http://msdl.microsoft.com/download/symbols use symbols from our software that are archived at \\foo\Build1234 use a local cache at c:\dev\symbols The archive of symbols from our distributed build at \\foo\Build1234 are not organized as a symbol server. If I understand it correctly, I need to use the cache keyword. Given these requirements, does this look like a properly formatted srvpath: cache*\

How to use Windbg for opening a dump and launching some Windbg commands from the command prompt?

删除回忆录丶 提交于 2019-12-02 14:11:18
As mentioned in this other question , I'd like to start Windbg , open a dump, and launch some commands ( .load pykd.pyd and !py heap_stat.py ). I thought this would be easy, but even starting Windbg and open a crash dump seems not that easy, as you can see from following unsuccessful examples: Prompt>windbg.exe /? Prompt>windbg.exe --help Prompt>windbg.exe E:\Bugs\program.exe_181212_215503.dmp Prompt>windbg.exe -D E:\Bugs\program.exe_181212_215503.dmp Prompt>windbg.exe -zertyuiopqsdfghjklwxcvbn Prompt>windbg.exe -help Prompt>windbg.exe help The idea is to get something like: Prompt>windbg.exe

How can I find the data structure that represents mine layout of Minesweeper in memory?

和自甴很熟 提交于 2019-12-02 13:48:46
I'm trying to learn about reverse engineering, using Minesweeper as a sample application. I've found this MSDN article on a simple WinDbg command that reveals all the mines but it is old, is not explained in any detail and really isn't what I'm looking for. I have IDA Pro disassembler and the WinDbg debugger and I've loaded winmine.exe into both of them. Can someone provide some practical tips for either of these programs in terms of finding the location of the data structure that represents the mine field? In WinDbg I can set breakpoints, but it is difficult for me to imagine at what point to

What is your favourite Windbg tip/trick? [closed]

六眼飞鱼酱① 提交于 2019-12-02 13:46:46
I have come to realize that Windbg is a very powerful debugger for the Windows platform & I learn something new about it once in a while. Can fellow Windbg users share some of their mad skills? ps: I am not looking for a nifty command, those can be found in the documentation. How about sharing tips on doing something that one couldn't otherwise imagine could be done with windbg? e.g. Some way to generate statistics about memory allocations when a process is run under windbg. Kris Kumler My favorite is the command .cmdtree <file> (undocumented, but referenced in previous release notes). This

IIS crashes and restarts without dropping a mini-dump

不打扰是莪最后的温柔 提交于 2019-12-02 13:44:40
问题 I have a tough scenario I'm trying to debug... On a web forms page, when I click submit, the web server hits some error and restarts the w3svc process. I do not see any stack trace dumped to the event log. The only entry in the Windows Application Log is: Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bd0eb Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0 Exception code: 0xe053534f There is no mini dump created for me to

IIS crashes and restarts without dropping a mini-dump

微笑、不失礼 提交于 2019-12-02 04:43:36
I have a tough scenario I'm trying to debug... On a web forms page, when I click submit, the web server hits some error and restarts the w3svc process. I do not see any stack trace dumped to the event log. The only entry in the Windows Application Log is: Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bd0eb Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0 Exception code: 0xe053534f There is no mini dump created for me to attach windbg to... Any ideas how to debug my issue? I suspect that you make a loop call like public

WinDbg: Version mismatch of dbghelp.dll when trying to attach to a process

落爺英雄遲暮 提交于 2019-12-02 04:04:52
问题 Over a year ago I already used WinDbg and DebugDiag to find a memory leak in a JNI native DLL that we use from within Java. Now I am searching for a thread handle leak. I created a memory dump using Process Explorer and tried to analyze it in DebugDiag, but all I get are script errors: I also tried WinDbg, but it is not able to attach to a process anymore. I always get the error message "dbghelp.dll has a version mismatch with the debugger": ("Unbekannter Fehler" means "Unknown error") I

Debugging winform crash - C# [ADPlus + Windbg]

与世无争的帅哥 提交于 2019-12-02 03:04:41
问题 System.AccessViolationException was unhandled Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Source=System.Windows.Forms StackTrace: at System.Windows.Forms.UnsafeNativeMethods.PeekMessage(MSG& msg, HandleRef hwnd, Int32 msgMin, Int32 msgMax, Int32 remove) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32

Can DebugDiag generate reports with “inclusive size” like Visual Studio 2013

☆樱花仙子☆ 提交于 2019-12-02 02:39:36
问题 Visual Studio 2013 can show a column for inclusive size (which includes size of child objects) - http://blogs.msdn.com/b/visualstudioalm/archive/2013/10/16/net-memory-analysis-enhancements-in-visual-studio-2013.aspx DebugDiag's memory analysis reports currently only shows object size without including child objects. Is there a way to make DebugDiag include size of child objects in its report? What do you suggest is a good way to generate such a report for .NET 4.0 since Visual Studio only