I have a memory dump (unmanaged process) . How can I extract (using windbg) one of the dlls loaded into the process ? I mean actually saving the dll file into the disk
相关问题
- Analyzing Outlook HANG dump (with GoogleCalendarSy
- How to debug static dependency loading problems?
- Generate dump with unmanaged code crash?
- windbg dump command fails with error 0x8007012b
- Determining which method is holding a ReaderWriter
相关文章
- Is my heap fragmented
- Specifying a command line for Windbg's Open Ex
- CDB command for setting a breakpoint based on a li
- Finding which function allocated a heap based on a
- Is 0x0000ffff the default load count of a dll in w
- Can I selectively create a backup of Postgres data
- sos.dll usage in visual studio 2013
- SQL Dump from DB2
To extract a DLL without using SOS, use the .writemem extension as follows:
discover the module start and end addresses using
lmvm dllname
example output for ieframe:
start end module name
61370000 61fb8000 ieframe
calculate the length = end-start:
? 61fb8000 - 61370000
output:
Evaluate expression: 12877823 = 00c48000
then save the DLL as follows:
.writemem C:\tmp\mydll.dll 61370000 L?00c48000
This is unlikely to give you the exact DLL as it was loaded from disk, fixing this up is non-trivial.
(Partly based on this article)
Yes, it's true. calc.exe will also pull up its multi user language interface information and attach it in memory, as will a lot of Windows programs like mspaint, photoviewer, etc.
You can use the sos.dll inside windbg directory.
First, load the sos.dll in windbg:
Then use !sam OR !SaveAllModule to extract the modules on specific disk location: