Hello,

I've been playing with an notepad protected with an older version of asprotect and have noticed that trace conditions seem to fail ... in other words tracing does not stop even if a stop condition is met. I'm using windows 2000. Can anyone confirm that this behavior is due to asprotect???? I have repeated this thing various times always failing. With other applications (not asprotected) tracing conditions work just as expected.


yaa

single step through some parts and find out if its clearing debug registers or if it is self checking for int 3s etc etc

there are hell lot of antidebugging tricks to really explain it out here and this forum isnt meant for it also

any way get ricardos tuts in spanish and push them through some online translator discard the rubbish texts and concentrate on some codes to understand what he is saying youll get through most of the unpacking stuff
or best but tedious way is to single step through evry useless command of it to really know how it works if you single step through it once or twice from next time onwards just by looking at dissembly youll come to know what can be happening

like repne scasb not ecx block means mostly it getting text length of some string lets skip it

oh me anon, which in the cpu pane are the debug registers???? Also, is tracing implemented using memory/hw breakpoints????

yaa

q no 1 ) right click on register pane and click view debug registers

q no 2) logially olly cannot do some magic zee boom ba stop here to pause when your condition is met so it must be using the available resources only like memory bpt hardware bprt one shot bpt like hit trace etc etc dont you think may be iam wrong but probably not