Welcome to the new Woodmann RCE Messageboards Regroupment
Please be patient while the rest of the site is restored.

To all Members of the old RCE Forums:
In order to log in, it will be necessary to reset your forum login password ("I forgot my password") using the original email address you registered with. You will be sent an email with a link to reset your password for that member account.

The old vBulletin forum was converted to phpBB format, requiring the passwords to be reset. If this is a problem for some because of a forgotten email address, please feel free to re-register with a new username. We are happy to welcome old and new members back to the forums! Thanks.

All new accounts are manually activated before you can post. Any questions can be PM'ed to Kayaker.

Setcpu and Setdisasm - problem

Found a bug in OllyDbg? Post a report here.
Locked
hnedka
Junior Member
Posts: 14
Joined: Thu Mar 13, 2008 7:58 pm

Setcpu and Setdisasm - problem

Post by hnedka »

I have a problem with functions Setcpu and Setdisasm. Under normal conditions, they work correctly. But when I use VirtualAllocEx to allocate memory in the process's address space, then I use Writememory to write code to that area and then I use one of the above functions, they display just an empty window(s). Going to that allocated area using ctrl-G work as it should. But going to that area using one of those functions doesn't work until I visit it manually using ctrl-G.

Is there any workaround or am I doing something wrong?
Thanks.
hnedka
Junior Member
Posts: 14
Joined: Thu Mar 13, 2008 7:58 pm

Post by hnedka »

Never mind, went again through all the functions and found solution - Listmemory(). This function actualizes list of memory blocks and then it works as it should. Hope this helps someone in the future.
Locked