This functionality is available in Cheat Engine where the debugger won't be attached until you set a breakpoint or explicitly ask for the debugger to be attached. I've looked everywhere and couldn't find anything similar for x64dbg. It's very useful when you want to view or modify memory of the process which employs anti-debug measures.
-
C functions: WriteProcessMemory and ReadProccessMemory – MkInitCpIO Sep 29 '19 at 2:06
-
I'm aware that these are the functions that tools make use of in order to read and modify debugee's memory. But I'm asking if there is a plugin or functionality in x64dbg to do this without attaching the debugger. It seems to me that the only way to open a process in x64dbg is to attach the debugger. – l3240120 Oct 1 '19 at 5:57
-
1@l3240120 Yeah... The thing is, x64dbg IS a debugger - you can't expect it to do anything else than debugging. Although I do understand the need to view/modify memory. I personally just use CE for doing it. – Anonymous Anonymous Oct 2 '19 at 7:33
-
I'm not entirely sure but I would wager a guess that the answer is no. You're talking about using a tool that is exclusively a debugger but without any debugging. Cheat Engine is fine if you simply want to view / edit memory. There are many memory manager tools, why so insistent on x64dbg when it doesn't seem to be the right tool for your job? – Pickle Rick Oct 11 '19 at 3:46
-
The TitanEngine.dll is no longer available for download. Is it possible a reupload? Thanks – Danrevella Jan 17 at 9:21
Yes, this is possible. You can replace TitanEngine.dll with https://github.com/mrexodia/StaticEngine and “attach” to a running process.
There is however no way to switch debugging modes and breakpoints etc will simply not work.
