I want to write a anti-anti debugging pluging.

[r42fr]

I want to write a anti-anti debugging plugin.But I don't know how to go throw the code to find the traps?

 

 

[Insid3Code]

It is hard to cover all existing anti-debug,  I advise you to begin with very basic detection tricks like hiding the PEB and memory patching of known API like FindWindow and other.

[r42fr]

But how to read the code of the program?

[Insid3Code]

I guess, you mean debuggee?
If you plan de code your plugin for OllyDbg you must read the PDK available on author website.To read/write into debuggee memory you can use ODBG2_Pluginnotify to get (debuggee Process ID)  when PN_NEWPROC == parm1

Edited May 19, 2013 by Insid3Code

[r42fr]

And how to print to ollydbg console?

[Insid3Code]

All you want is available into OllyDbg PDK, please read it!
hxxp://www.ollydbg.de/version2.htmlAlso, take a deep look into traceapi source for undocumented functions.

Edited May 19, 2013 by Insid3Code

[slipfake]

There're good tutorials on www.woodmann.com about anti-debugging. Follow that site!