A couple of days ago I suggested a series of lessons on X86 assembly, which deals with 32-bit chips. One might think that they may be irrelevant for today's state of technology but is not actually the case.
Learning 32-bit assembly or any other type of assembly (because assembly is a family of programming languages, depending on the processor you are referring to) will allow you to be able to code and also debug for the others as well (small changes in registry names, as well as some changes in how information is handled should not be too hard to comprehend).
Anyhow, it's quite not easy to find good resources on this type of stuff. Most tutorials, lessons, and courses focus on higher level languages. This also makes me mention the fact that I have a hard time finding good materials on reverse engineering with IDA. Not to diverge...
This series I'm suggesting today seems to be worth following as it delves into x64 assembly. I'm already a few 'inches' deep, so I have to say that Mike, the presenter, has a unique way of delivering knowledge. If you're into this kind of stuff, enjoy and happy learning!
To stay in touch with me, follow @cristi
Cristi Vlad Self-Experimenter and Author
X64.......huh. I am no expert in it but having studied processor architecture I have had to deal with it in the past.
The presenter says that 'Assembly is etched into the the CPU' - that is a very interesting way of putting it. It is actually true and for an electronics engineer's perspective it is the perfect way of putting it.
It always bugged me a little to know that it is called a low level language language :-)
Yeah, the pain points I remember from learning x86 asm have to do with screwing up dealing with both 16-bit and 32-bit ints and pointers in the same program. This part of ICT for me was crazy
Excellent. Great to see some people are still interested in programming low level languages and understand how computers really work.
I program mainly in C myself and must confess I rarely have the opportunity to use assembly but I look forward to learn more in your series.
Funnily enough I found a bug in gcc one day by examining the generated assembly. That was a b**ch to debug...
Thanks for sharing!