Given the following code :
.section .rodata
str: .string "Hello World!\n"
input: .long 2
########
.text
.globl main
.type main, @function
main:
pushl %ebp
movl %esp, %ebp
pushl $str
call printf
#return from printf:
movl $0, %eax
movl %ebp,%esp
popl %ebp
ret
The output would be "Hello World!".
Now I try to get a number from the user , and then print it out on the screen , but
it doesn’t work (code compile,but I did something wrong) .
Where is my mistake ?
.section .rodata
input: .long 2
########
.text
.globl main
.type main, @function
main:
pushl %ebp
movl %esp, %ebp
pushl %ebx
call scanf # call scanf to get number from the user
popl input # store the number entered by user in input (variable)
pushl input # push it back into the stack
call printf # print input
#return from printf:
movl $0, %eax
movl %ebp,%esp
popl %ebp
ret
I’m not really sure what sort of assembler you’re using, however I could get your code to compile with gcc so I stuck with your formatting style (not talking about the AT&T syntax).
Anyway, you should check the documentation for
scanfand realise that it takes a format string and pointers to locations in memory of where to store the values read in. It also returns the number of successfully read items and not what was read.Now do the same and check the documention for
printf. You’ll see that a format string is required to print your number in a readable form. A suitable format string is"%d\n"to print the number and a newline.Your code could now look something like this (which compiles and works fine for me with gcc):
Note that I would normally use
db/dw/ddfor allocating memory in the.(ro)dataand.bsssections as opposed to.stringand.long, so if that part’s done slightly wrong you could just fix it up.You could also use stack space for storing the number, however you already had
inputdeclared and I wanted to leave the code as similar to what you had as possible. Same goes for everything else before and after thescanfandprintfstuff, I just left that as your code.EDIT: Here’s an example of using the stack to create a local variable, as opposed to having a variable declared in the
.bssor.datasegment: