OllyDbg is not good at supporting breakpoints in multi-threading environment

[wilson bibe]

If I understood your question a way is is use the olly_hardware_breakpoint plugin and save yours BP, if you have problem to find your calls to dll,ocx,etc..., load the BP saved by the OHB, when you load the app in olly.
Greetings...

[BlackWhite]

Originally Posted by wilson bibe

If I understood your question a way is is use the olly_hardware_breakpoint plugin and save yours BP, if you have problem to find your calls to dll,ocx,etc..., load the BP saved by the OHB, when you load the app in olly.
Greetings...

My question is actually as follows:
(1) There are two functions say f() and g();
(2) OllyDbg debugs f() and sets a breakpoint inside g();
(3) g() is executed by another thread which is not the same as the thread
executing f();
(4) When g() is executed, the breakpoint set inside will not be triggered
whether it's a software breakpoint or hardware one.

So, do you think olly_hardware_breakpoint plugin can solve this problem?

Thanks.