-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
Attach a debbuger like WinDBG or x64dbg directly to the file system. #9
Comments
If debugging Windows it should auto-generate a memory.dmp file which you should be able to open in WinDbg. Setting breakpoints and such aren't working though, but it will detect os, kernel and processes and automatically download required symbols and such. If wanting to patch something you'll have to open process virtual memory (or physical memory) in your hexeditor and patch. Note tho that patching .exe/,dll/.sys image in one process will likely patch it in all processes since writes goes down to physical memory. Patching heaps/stacks and such generally have no such side effects. |
Is it your intend not to include the dump file per process or is it my PC that doesnt have one? |
only full dump is currently available, I'm unsure about per-process minidumps, it's on my todo-list to look into but I'm not sure about the complexibility. you should be able to switch into process context in WinDbg already though .... replace the ffff-value in .process with your process EPROCESS address.
|
Dear Ufrisk
Is there a way to attach a debugger like the two above directly to the memory file system with FPGA devices? I have tried to dump the raw binary of a function at the target virtual address and analyze with IDA but honestly without dependencies the disassembler code is not quite meaningful.
Leo
The text was updated successfully, but these errors were encountered: