Your message dated Mon, 01 Oct 2007 06:44:47 -0600
with message-id <[EMAIL PROTECTED]>
and subject line (no subject)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: binutils
Version: 2.16.1cvs20050902-1
Severity: normal
When you run an assembly program without any data in the .data section,
you will get a segmentation fault in execve() and the binary won't run.
Here is an output from strace:
$ strace ./a.out
execve("./a.out", ["./a.out"], [/* 69 vars */]) = -1 EFAULT (Bad address)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
$
When I assemble and link the program with binutils 2.16.1-2, the binary
works fine. I've attached a very simple assembly program exposing this
problem. It just calls the exit system call. If you uncomment the entry
in the .data section, the assembled binary will work fine.
To assemble the program, do the following steps:
$ as exit.s -o exit.o
$ ld exit.o -o exit
Takeshi
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages binutils depends on:
ii libc6 2.3.5-6 GNU C Library: Shared libraries an binutils recommends no
packages.
-- debconf information:
binutils/oformat_warning:
* binutils/kernel_link_warning:
.section .data
# .long 0
.text
.globl _start
_start:
movl $1, %eax
movl $0, %ebx
int $0x80
--- End Message ---
--- Begin Message ---
Sorry it took very long to reply to your comments. I didn't even notice
it. It works for me now, too. So I'm closing this bug.
Thanks,
Takeshi
--- End Message ---
