Madman Posted November 10, 2005 Author Posted November 10, 2005 ANY language you code in IS compiled to binary/assembly, upon execution latest (.NET Framework compiles upon execution) as binary/assembly is the only stuff your comp can executeSo debugging something is accessing at the binary level, therfore it returns assembly stuff.
Lucandrake Posted November 10, 2005 Posted November 10, 2005 So that means to debug all the programs I want to debug I have to learn assembly right? Which is what im trying to do, the thing is difficult ><
Gryph Posted November 10, 2005 Posted November 10, 2005 Dude, you need to learn the basics before you start delving into the actual coding. That'd be like me learning how to do heart surgery before knowing what the heart does.
Lucandrake Posted November 10, 2005 Posted November 10, 2005 What is there to learn, how a computer works??? I'll learn that eventually, actuall code is much more fun *nods twice*
taratata Posted November 11, 2005 Posted November 11, 2005 (edited) I'm sure cutting through fresh flesh with a scalpel is also much more fun than learning how the heart works. However, I'm not sure I'd like to know the surgeon that would open my chest has skipped theory because "it's more fun to cut". You don't need to learn every detail of how a computer works to code; but jumping straight into coding won't lead you anywhere either. To learn assembly coding though, you'll have to know how the processor you will code for works. At the very least, to code in any language, try to learn the basics of data structures and how an algorithm works (for high level languages; assembly would require more technical knowledge). Coding can be a little fun when you jump straight into it, but it's so much better when you know what you're doing. Also, forget about debugging programs you didn't write yourself. To save on space, they usually remove all labels, making it almost impossible to understand anything about the disassembled code, even for professionnals. You could begin by trying to understand the source code of open-source programs, even that is tough. EDIT: I forgot something. If you want to have fun coding, stay the hell away from assembly. Any sane person would get crazy trying to code something really elaborate in assembly. It's like building a wooden house with matches. Edited November 11, 2005 by taratata
Lucandrake Posted November 11, 2005 Posted November 11, 2005 *sighs* I hate when im going one direction and suddenly everyone advises to go the other, well, if it's for the best, time to go on google and look up on how proccessers work *tear*
Weirdy Posted November 11, 2005 Posted November 11, 2005 you can also do inline assembly in c++ I think it's _ASM{} I read up on assembly and I was like..."wtf "
Lucandrake Posted November 11, 2005 Posted November 11, 2005 Yea it's weird, I remember gryph telling me "Some consider it a programming language others don't"
taratata Posted November 12, 2005 Posted November 12, 2005 *sighs* I hate when im going one direction and suddenly everyone advises to go the other, well, if it's for the best, time to go on google and look up on how proccessers work *tear*<{POST_SNAPBACK}>Noone forces you to do anything. If you really want to, go ahead. All I can tell you is that I have started to learn assembly, and the best achievement I have done so far, is a program that can output its own name (on the command line). Good luck!
Lucandrake Posted November 13, 2005 Posted November 13, 2005 *sighs* I hate when im going one direction and suddenly everyone advises to go the other, well, if it's for the best, time to go on google and look up on how proccessers work *tear*<{POST_SNAPBACK}>Noone forces you to do anything. If you really want to, go ahead. All I can tell you is that I have started to learn assembly, and the best achievement I have done so far, is a program that can output its own name (on the command line). Good luck! <{POST_SNAPBACK}> Thanks you to taratata, your so helpfull ^.^
taratata Posted November 13, 2005 Posted November 13, 2005 I forgot to say something: the longest is not writing the programs, it's debugging them. Have a coffee machine ready
Lucandrake Posted November 13, 2005 Posted November 13, 2005 I forgot to say something: the longest is not writing the programs, it's debugging them. Have a coffee machine ready <{POST_SNAPBACK}> I know that already lol
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now