Log in

View Full Version : tracing API's


shadows
March 27th, 2004, 01:06
Hi all.
I hope I dont rehash here whats allready been discussed 5 billion times.
Im trying to break on certain messagebox but there are like soooooooo
many modules. Any tips on how to locate the right messagebox ?
I use Olly. I've tried a few methods...maybe Im on the right track.
There's an option in the memory pane to view all names in a specific module-- or all modules....can also inspect resource data.
In many case the messagebox info I found in a module name
listing is really a data define...so I would highlight that and check for all
code references to it and break on them. But it's funny cuz they arent
breaking at all and I'm clueless as to why not.
I've hear nice stories of SoftICE and how one can just set BP on any API
and when it hits SICE will dump you right there in the code.....must
be nice, I've never experianced such bliss.
Well
regards and thanks for any advice
_________________

Ricardo Narvaja
March 27th, 2004, 15:12
If you have nt/2000 or XP you can put bpx on api similar to softice, you can trace the apis, and work more confortable than softice.

Ricardo