| View previous topic :: View next topic |
| Author |
Message |
xeratal Advanced Cheater
Reputation: 1
Joined: 05 Nov 2005 Posts: 93
|
Posted: Tue Dec 27, 2011 5:04 pm Post subject: Memory address and memory location difference? |
|
|
Something I have NEVER understood:
e.g. memory location @ 00400000 has bytes 4D (dec ebp)
yet location [00400000] stores something else.
What is the difference between them? I know that they are obviously different, but aren't there better technical terms for them? To me, it would seem lame (and probably wrong) to call both of them memory (memory location and memory address...?) when they are completely different (I think).
Or is it both 00400000 but one in the .code and one in the .data?
Any one can enlighten me?  |
|
| Back to top |
|
 |
Geri Moderator
Reputation: 111
Joined: 05 Feb 2010 Posts: 5627
|
Posted: Tue Dec 27, 2011 5:10 pm Post subject: |
|
|
They are the same. If something is not right, check it again. You have just missed something.
Also, 00400000 is the stub. Usually the codes are starting at 00401000. _________________
|
|
| Back to top |
|
 |
xeratal Advanced Cheater
Reputation: 1
Joined: 05 Nov 2005 Posts: 93
|
Posted: Tue Dec 27, 2011 5:24 pm Post subject: |
|
|
You are right; I just wasn't looking at the memory locations in terms of [bytes]!
Slightly off my own topic, but I would assume that's how self-modifying code works - by simply changing the location's value to something new? I guess that's how AV's/Anti-hacks/CE scans memory as well... thanks! |
|
| Back to top |
|
 |
Geri Moderator
Reputation: 111
Joined: 05 Feb 2010 Posts: 5627
|
Posted: Tue Dec 27, 2011 5:41 pm Post subject: |
|
|
Memory is just having numbers. Some numbers are parameters, some numbers can be diassembled as codes and some numbers are just values to work with or text or whatever.
CE will try to disassemble any location you try, but if it is not a code, you will get gibberish only. _________________
|
|
| Back to top |
|
 |
|