Running 32 bit assembly code on a 64 bit Linux & 64 bit Processor : Explain the anomaly

by

Remember that everything by default on a 64-bit OS tends to assume 64-bit. You need to make sure that you are (a) using the 32-bit versions of your #includes where appropriate (b) linking with 32-bit libraries and (c) building a 32-bit executable. It would probably help if you showed the contents of your makefile if you have one, or else the commands that you are using to build this example.

FWIW I changed your code slightly (_start -> main):

#include <asm/unistd.h>
#include <syscall.h>
#define STDOUT 1

    .data
hellostr:
    .ascii "hello wolrd\n" ;
helloend:

    .text
    .globl main

main:
    movl $(SYS_write) , %eax  //ssize_t write(int fd, const void *buf, size_t count);
    movl $(STDOUT) , %ebx
    movl $hellostr , %ecx
    movl $(helloend-hellostr) , %edx
    int $0x80

    movl $(SYS_exit), %eax //void _exit(int status);
    xorl %ebx, %ebx
    int $0x80

    ret

and built it like this:

$ gcc -Wall test.S -m32 -o test

verfied that we have a 32-bit executable:

$ file test
test: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not stripped

and it appears to run OK:

$ ./test
hello wolrd

More Related Contents:

  1. How are the fs/gs registers used in Linux AMD64?
  2. Using gdb to single-step assembly code outside specified executable causes error “cannot find bounds of current function”
  3. What are the calling conventions for UNIX & Linux system calls (and user-space functions) on i386 and x86-64
  4. Where is the x86-64 System V ABI documented?
  5. glibc scanf Segmentation faults when called from a function that doesn’t align RSP
  6. Can’t call C standard library function on 64-bit Linux from assembly (yasm) code
  7. Using printf in assembly leads to empty output when piping, but works on the terminal
  8. Printing an integer as a string with AT&T syntax, with Linux system calls instead of printf
  9. Nasm segmentation fault on RET in _start
  10. How to print a number in assembly NASM?
  11. Why do x86-64 Linux system calls modify RCX, and what does the value mean?
  12. What is better “int 0x80” or “syscall” in 32-bit code on Linux?
  13. Calling printf in x86_64 using GNU assembler
  14. Linux default behavior of executable .data section changed between 5.4 and 5.9?
  15. Hello, world in assembly language with Linux system calls?
  16. Minimal executable size now 10x larger after linking than 2 years ago, for tiny programs?
  17. How do I disassemble raw 16-bit x86 machine code?
  18. How to print a character in Linux x86 NASM?
  19. Is garbage allowed in high bits of parameter and return value registers in x86-64 SysV ABI?
  20. Number of executed Instructions different for Hello World program Nasm Assembly and C
  21. How to single step ARM assembly in GDB on QEMU?
  22. Assembly segmentation fault after making a system call, at the end of my code
  23. How to calculate time for an asm delay loop on x86 linux?
  24. Why Linux/gnu linker chose address 0x400000?
  25. Trying to understand gcc’s complicated stack-alignment at the top of main that copies the return address
  26. Segmentation fault on printf – NASM 64bit Linux
  27. What is the default register state when program launches (asm, linux)?
  28. How to convert Linux 32-bit gcc inline assembly to 64-bit code? [closed]
  29. Linux x64: why does r10 come before r8 and r9 in syscalls?
  30. x86_64 Assembly Linux System Call Confusion

Leave a Comment