Topic created on: December 22, 2007 07:24 CST by Piotr .

Well today i tried to make some ollydbg plugin, and i was pretty confused when i tried to handle breakpoints inside ODBG_Pluginmainloop. The Go() function from SDK continued the process but with DBG_EXCEPTION_NOT_HANDLED, instead of DBG_CONTINUE and even after playing with a hella t_regs/t_thread options i got the same effect. It almost seems patching the orginal debugger would be a simplier task then doing it clearly :) Anyway i have done the following task with help of ODBG_Pausedex callback (and now the Go() function continues the process with the correct options), however it's still  doesnt suit my needs. Because its damn slow, and all these window CPU/REGS/MEM updates slow the process even more (i tried to play with some window functions and broadcasting but with no proper effect). One of the dirty solutions maybe hooking the WaitForDebugEvent but like i said before i want to do it in clear way (if it can be done). So this is a question for olly plugin fanatics, can it be done? :) Lets assume i want to handle access violation inside of the plugin and continue the debugging process without ollydbg chipping in.