-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
an example to get DLL from dump #212
Comments
The dlls are not in the memory dump: it contains only data, no executable code so I don't think it's possible. |
If its a full memory dump, the full dlls are in the dump. I pull them out via windbg and reflect them all the time. |
Right, this very much depends on whether the dump is a full dump or a minidump |
yes, full dump @Muppetdog can you point me (where can i read) how to do, step by step? |
I'm sorry but I've no idea how to do that. Memoscope is just a UI: all features come from ClrMd and I can't find anything in this to extract dlls. |
Easiest way to dump out dlls from a dump is with the Mex debugging extension for Windbg. !writemodule -a -p pathtosave It will save all the modules in the dump, managed and unmanaged https://www.microsoft.com/en-us/download/details.aspx?id=53304 |
@fremag , ah, sorry, seems i have made duplicate request for that, however, what your thoughts about last comment by @Muppetdog ? Could that be integrated? |
under Memory>Modules, we can view DLLs...
but when right click on any item in the list, it only shows: "Copy selected rows".
so, is there any way, and if so, an example - how to get dll to write to a normal .dll file for further usage for JustDecompile ( or like that)?
or to write whole content of specific dll dump into a readable files, similarly as JustDecompile (or etc), create a project folder from .DLL
The text was updated successfully, but these errors were encountered: