Yah, this place is dead as shit.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: DeTaiLs on November 19, 2005, 09:17 PMI think my school attracts attention whores.
It seems like kids in your school have some serious issues and you where holding that anger in for a long time.
Quote from: noob on November 15, 2005, 10:26 PMI dont agree with you there. E-books and books are a great resource for learning. Learning off generated code from a C compiler wont teach you how to optimize your code. And it never hurts to have a good understanding of ASM, programs may be written in ASM and not C (or even a different langauge) so you wont know what you're looking at becuase the code wasnt generated from the compiler you're familiar with.
Also, don't bother with any books on ASM. They teach you bad habits. Learn on your own.
Write something, for example:
int main(void)
{
printf("string\n");
return 0;
}
and gcc with -S:
.file "asdf.c"
.section .rodata
.LC0:
.string "string\n"
.text
.globl main
.type main, @function
main:
pushl %ebp
movl %esp, %ebp
subl $8, %esp
andl $-16, %esp
movl $0, %eax
subl %eax, %esp
movl $.LC0, (%esp)
call printf
movl $0, %eax
leave
ret
Learn how functions are called, how conditionals are evaluated and acted upon, etc. Since you're interesting in game hacking, which is largely disassembling, knowing how certain chunks of C code looks in assembler is key. You don't really have to understand ASM deeply, just know what to look for.
Page created in 0.212 seconds with 16 queries.