hodge-podge How do I cheat?
Reputation: 0
Joined: 11 Jun 2009 Posts: 5 Location: New Hampshire
|
Posted: Fri Mar 05, 2010 8:50 pm Post subject: Architecture of a program, or whatever you call it. |
|
|
One of the daunting concepts I have yet to overcome and understand is the "Architecture of the program". This lack of understanding inhibits me in using tools like CE or Ollydbg etc to their full and intended potential. I call it this for lack of a better better word.
What I mean by "architecture" is the flow of the program. In attempts to better understand reverse engineering programs, I've written my own exe's and have tried to reverse engineer them. The thing is that even with simple "hello world" programs I get thousands of lines of code. I'm pretty sure this is because of all the .dlls etc that are called when running any app, correct me if I am wrong.
My problems come while looking at the memory view, and I cannot tell whether I am looking at various resources called, or the exe I wrote itself. Basically, I cannot seem to begin to navigate through the complexity of even the most simple of programs.
For instance, where is CE getting the info in the OPCODE view from? How is it different from the Memory view? How are the addresses in the two related? etc...
Any advice, tips, resources? All would be greatly appreciated.
|
|