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
The optional --join argument works smoothly with the --module argument to extract a module from a given process PID. Unfortunately, the main module (from the process image file) cannot be extracted into a single file as in the case of modules. It would be great if we could run the tool as
And get a single file with the entire memory dump of the main module. I think GetProcessImageFileName can do the job, after getting the process handle by means of OpenProcess.
The text was updated successfully, but these errors were encountered:
The optional
--join
argument works smoothly with the--module
argument to extract a module from a given process PID. Unfortunately, the main module (from the process image file) cannot be extracted into a single file as in the case of modules. It would be great if we could run the tool as.\WindowsMemoryExtractor_x64.exe --pid 1234 --join
And get a single file with the entire memory dump of the main module. I think GetProcessImageFileName can do the job, after getting the process handle by means of
OpenProcess
.The text was updated successfully, but these errors were encountered: