On a 64-bit Windows installation is it possible to make both 32-bit and 64-bit dumps of 32-bit processes. The task manager will create a 64-bit dump, which therefore is often what you end up with users sending you. This is not a problem for native executeables since you can still load it in windbg and use the !wow64exts.sw extension to switch into the 32-bit view. However if your process is a .NET process and you want to use SoS to investigate it then you are out of luck, you'll just get the message "SOS does not support the current target architecture." This extension gets around this by hooking/patching functions in dbgeng.dll so that SoS thinks it's working with a 32-bit dump. ** Usage ** Copy soswow64.dll into the "winxp" subfolder of windbg. Then after loading a 64-bit memory dump of a 32-bit process you can simply load the extension: 0:000> .load soswow64 Successfully hooked IDebugControl::GetExecutingProcessorType. Successfully patched DbgEng!X...
:::Update::: So I've figured it out...as I suspected it isn't intuitive IMO. But here it goes: Start -> Control Panel -> User Accounts -> Manage another account -> Select Account -> Change Password The "Manage another account" is what got me last time! Enjoy! ------------------------------------------------------------------ So I just installed Windows Server 2012. I was struggling with the simplest concept, how to change my current password on my user account. Seems that the old CTRL+ALT+DELETE -> Change Password is no longer available? To get around the issue you can use one of the following methods: Method 1: Click Start ->Administrative Tools -> Computer Management -> Expand Local Users and Computers -> Expand Users -> Right Click <username> -> Click "Set Password". Method 2: Launch PowerShell -> type in LUSRMGR.MSC -> Expand Users -> Right Click <username> -> Clic...
Git branching is usually pretty straight forward and although merging can be a hassle it is important to remember the reasons for the isolation. In the event a hotfix is required, it is handy to branch off from master instead of develop - this way we can test the fix on the develop branch before merging back to master. The beauty of this makes git so powerful and the reason it's the most popular software version control software at the moment. Also a quick mention that git branch --merged to see what's now part of the new master as this will list each individual feature, bugfix or hotfix as a list. Great for generating release notes.
Comments
Post a Comment