rebasing the database

[neko...@gmail.com]

Hi,

Sometimes I need to work on code that dynamically unpacks itself to VirtualAlloc'd memory and I can't find any way to keep the database of breakpoints, labels, etc in sync, nor can I reliably force the OS to map the allocated memory to a repeatable address.  So every time I restart the debugging session my database is invalidated.

First of all if anybody has tips for working around this problem I would love to hear them.  The best I've been able to do so far is debug in a virtual machine so I can export my database, rewind the VM to an earlier point, then re-import the database.  It works but it's tedious and wasteful.

I've been thinking it would be really useful to be able to rebase address ranges of the database once I know the allocation.  Something like "rebasedb oldbase, newbase" and it would infer the size from the current allocation.  Then all the breakpoints, labels, comments, etc. would be usable again without resorting to a VM.

Is this a sane idea?  Is it best done with a plugin and do plugins have API for iterating over database items?

[Duncan Ogilvie]

You can use virtual modules for this purpose.

On Sat, 24 Nov 2018 at 12:23, <neko...@gmail.com> wrote:

[R]

Thank you, I was not aware of this feature but it is exactly what I need! 

On Sat, Nov 24, 2018, 22:41 Duncan Ogilvie <mr.exod...@gmail.com wrote:

You can use virtual modules for this purpose.

On Sat, 24 Nov 2018 at 12:23, <neko...@gmail.com> wrote:

--
Don't forget to report issues on http://issues.x64dbg.com!
---
You received this message because you are subscribed to a topic in the Google Groups "x64dbg" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/x64dbg/XQ5RgI6i9U0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to x64dbg+un...@googlegroups.com.
To post to this group, send email to x64...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.