during an analysis, I had the following situation: The main thread allocates some space, the base address is 002E0000. Then it put opcodes (of the new thread) to that place. So, 002E0000 was the starting address of the new thread and later it called
CreateRemoteThread() API and Ollydbg switchs to 002E0000 (dwCreationFlags was set to 0 , so the new thread started immediately)
Now, my question: When I try to set a BP on one of the virtual addresses of the new thread, I get the following error message.
I also tried on Hardware BPs but it did not help. Why I can not set the BP ? In the main thread, everything was ok. How can I bypass this to analyze the new thread with all the BP setting features of Ollydbg ? Note: I am using Ollydbg v1.10