logpro V1.0 plug-in for TRW2K.

1.)why LOGPRO?
===============
I had promised to someone to make such a plug-in for trw long before,
but never started,Recently I got a log3 on RCE tools by dion,It's good,but still
not the one what I want,so it(LOGPRO ) born.

2.)Usage
==============
LOGPRO [filename] [options a u k -uk p -p o -o]

a)
you can simply 
logpro	d:\test.txt
then f8 or f10 to trace,all the instructions you traced will be recorded.
or then run a soft BP by hand.

b)
or you can use options to use it's more powerful features through options
a u k -uk p -p o -o

a-->run logpro and a coreesponding g if(eip==-1) command to auto the task.

u-->record INSTRs between 0x10000 && 0x7FFFFFFF usually the application's space.
    this is default.

k-->record INSTRs <0x10000 && >0x7FFFFFFF usually the application's space.

-uk --> cancel the u or k option...record in both K and U apaces.

o--> code on including binaries

-o --> code off....this is default.

c)
you can:

LOGPRO d:\test.asm apo		//auto ,user space,including binary,only jmp call etc...
LOGPRO d:\test.asm a-uk-op
......
you can use at your own test and habbit...

3)Known-bugs:
===================
it can't distinguish some instrs from jmp call etc very well...i.e it'll record 
some rubbish except the Jxx call ret int...etc.however it includes all the key 
instr you want...

If I have time,I'll improve the distingguish routine.

BTW,
the num of INSTRs recording limit is 1000000 millions,the only purpose is to
save your disk space ,it's enough for ordinary purpose.If you want to go on 
recording after the trw popup and say "limit is reached",just run logpro off
and logpro to the file name again.


any more bugs or good ideas are always welcome,contact me as follows.

4)contact
==============
	
	humewen@21cn.com
	http://humeasm.yeah.net

			
			Hume,PR.China,August 20th,2K2.