windbg

问题 How do I share Javascript code between files in Windbg preview? Right now I have several helper methods that I have copied and pasted into different javascript files. I'm not all that experienced with javascript, so my apologies if this is a stupid question. As an example, let's say I want to use this function in more than one file: function GetGuid( objectPtr ) { return ExecuteCommandToString( "dt nt!_GUID " + objectPtr ) .FindLineContaining("{").trim().replace("{", "").replace("}",""); }

问题 I am currently analyzing a application hang issue of a .Net 4.0 Application. Based on the stack traces of few threads my guess is that few key value pairs in a dictionary has been removed some how. To confirm the same, i am trying to analyze the contents of the Dictionary using Windbg In could see that the 'entries' in the dictionary is a array. So tried to list the entries using '!da', but it does not work. Tried !dumpvc (i know its does not work for list), but just gave a try And of course

问题 I am currently analyzing a application hang issue of a .Net 4.0 Application. Based on the stack traces of few threads my guess is that few key value pairs in a dictionary has been removed some how. To confirm the same, i am trying to analyze the contents of the Dictionary using Windbg In could see that the 'entries' in the dictionary is a array. So tried to list the entries using '!da', but it does not work. Tried !dumpvc (i know its does not work for list), but just gave a try And of course

问题 I am currently analyzing a application hang issue of a .Net 4.0 Application. Based on the stack traces of few threads my guess is that few key value pairs in a dictionary has been removed some how. To confirm the same, i am trying to analyze the contents of the Dictionary using Windbg In could see that the 'entries' in the dictionary is a array. So tried to list the entries using '!da', but it does not work. Tried !dumpvc (i know its does not work for list), but just gave a try And of course

问题 Is there a way to WinDbg in pure headless mode ? My use case is that I should be able to imitate "!analyze -v" command for a minidump on command line without launching WinDbg GUI. 回答1: With the Debugging Tools for Windows, there is also cdb , the console debugger. To debug a crash dump, use the -z "<dump>" option. To run a command immediately, use -c "<command>" . To output everything into a file you can redirect the output with a usual DOS > <file> or open a log file using .logopen <file> .

问题 I want to parse the full crash dump (*.dmp) file and get the private bytes data. I know that VMMap of SysInternals can tell me how much my private bytes, heap etc are all but what I need is if I have the dump, I should be able to parse it and get the Heap (managed Heap) Structure and data in the heap. I am already done with this by reading the PEB and then walking through heaps. What I am not able to figure out is how to read the private bytes (other than Heap, which is supposed to be the

问题 I have a crash dump for a customer's application built with a very old version of our dll (release build, don't have original symbols) that I've been analyzing in WinDbg. In order to get more information, I rebuilt the dll in release mode, with symbols this time, using the same compiler version and I believe the same settings as when the dll was originally built. I added the symbol file to my symbol path, but the WinDbg extension !itoldyouso tells me the module in the dump doesn't match the

问题 I have a crash dump for a customer's application built with a very old version of our dll (release build, don't have original symbols) that I've been analyzing in WinDbg. In order to get more information, I rebuilt the dll in release mode, with symbols this time, using the same compiler version and I believe the same settings as when the dll was originally built. I added the symbol file to my symbol path, but the WinDbg extension !itoldyouso tells me the module in the dump doesn't match the

问题 Is there any extension command could to do so? I just want to the the whole command line including all parameters. 回答1: Information like the command line args are stored in the PEB (Process Environment Block). You can find a list of common commands here. !peb will display the PEB. 回答2: try vercommand it's a lot simpler than !peb this is a good place to get you started: http://windbg.info/doc/1-common-cmds.html#2_general_cmds 来源： https://stackoverflow.com/questions/6224834/how-to-get-the

问题 Is there any extension command could to do so? I just want to the the whole command line including all parameters. 回答1: Information like the command line args are stored in the PEB (Process Environment Block). You can find a list of common commands here. !peb will display the PEB. 回答2: try vercommand it's a lot simpler than !peb this is a good place to get you started: http://windbg.info/doc/1-common-cmds.html#2_general_cmds 来源： https://stackoverflow.com/questions/6224834/how-to-get-the