The class procs that olly detects on this target are bogus: when I try to set message breakpoints, ollydbg screams that the addresses are in the data section. I tried using spy++, but the addresses it gives for the winproc of the window and of the class, while different from those listed in ollydbg, don't seem to point at the right stuff either. Is there some conversion I need to do from spyxx addresses to ollydbg addresses?

Is there some other way to break in olly on a wm_gettext under XP? I tried a bp on user32.getwindowtexta, but apparently it isn't being called.

Hi Mike,

I don't know if this helps in sorting out the Spy++ window proc addresses you see or forcing a msg break when nothing else works..

http://www.woodmann.net/forum/showpost.php?p=60118&postcount=4

Kayaker

thanks