You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sos today provides both the clrmodules command, which enumerates all modules in memory along with their address, and the savemodule command, which accepts a module address and a file path and writes the module out to disk. This is really useful for being able to extract an assembly and save it out for use with other tools, like ILSpy. But this is tedious (or requires separate scripting) to use to extract all modules in order to browse the whole app or service being debugged.
Proposed Feature
!SaveAllModules directory_path
The command will effectively automate getting the list of modules (aka clrmodules) and saving out each to the specified destination directory.
Background and Motivation
sos today provides both the
clrmodules
command, which enumerates all modules in memory along with their address, and thesavemodule
command, which accepts a module address and a file path and writes the module out to disk. This is really useful for being able to extract an assembly and save it out for use with other tools, like ILSpy. But this is tedious (or requires separate scripting) to use to extract all modules in order to browse the whole app or service being debugged.Proposed Feature
!SaveAllModules directory_path
The command will effectively automate getting the list of modules (aka
clrmodules
) and saving out each to the specified destination directory.Usage Examples
!SaveAllModules c:\users\myname\Desktop\DebuggingTmp
The text was updated successfully, but these errors were encountered: