ld.bfd crashed with SIGSEGV in mempcpy() while compiling ruby-1.9.2-head rev 28645

Bug #605562 reported by Matteo Settenvini
64
This bug affects 8 people
Affects Status Importance Assigned to Milestone
binutils (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: binutils

Steps to reproduce:

 * install rvm
 * try to compile ruby (rvm install ruby-1.9.2-head) with rev 28645 -- may happen also with other revs
 * crashes during linking

However, rvm ends the execution correctly, and installs ruby ok. Apport isn't happy, though, so I'm reporting this.

Applies to amd64.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: binutils 2.20.51.20100710-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic x86_64
Architecture: amd64
Date: Wed Jul 14 21:06:54 2010
ExecutablePath: /usr/bin/ld.bfd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcCmdline: /usr/bin/ld --sysroot=/ --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=both -export-dynamic -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o conftest -z relro /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crt1.o /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.4.4/crtbegin.o -L. -L../.. -L. -L/home/username/.rvm/rubies/ruby-1.9.2-head/lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib -L//lib/../lib -L//usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../.. -L//lib -L//usr/lib -L/usr/lib/x86_64-linux-gnu /tmp/cckblQxd.o -export-dynamic -lncurses -ltermcap -R /home/username/.rvm/rubies/ruby-1.9.2-head/lib -lruby-static -lncurses -ltermcap -lpthread -lrt -ldl -lcrypt -lm -lc -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/x86_64-linux-gnu/4.4.4/crtend.o /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crtn.o
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x2b32538a5692 <mempcpy+194>: mov (%rsi),%rax
 PC (0x2b32538a5692) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: binutils
StacktraceTop:
 mempcpy () at ../sysdeps/x86_64/memcpy.S:191
 _IO_new_file_xsputn (f=0x112b910, data=0x0, n=65)
 _IO_fwrite (buf=0x0, size=1, count=65, fp=0x112b910)
 ?? ()
 bfd_bwrite ()
Title: ld.bfd crashed with SIGSEGV in mempcpy()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Matteo Settenvini (tchernobog) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mempcpy () at ../sysdeps/x86_64/memcpy.S:191
 _IO_new_file_xsputn (f=0x112b910, data=0x0, n=65)
 _IO_fwrite (buf=0x0, size=1, count=65, fp=0x112b910)
 cache_bwrite (abfd=<value optimized out>,
 bfd_bwrite (ptr=<value optimized out>, size=65,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in binutils (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

I'm also getting a similar error when configuring qemu upstream (hash 08218b3527301760393b0b4ec732fcdfb7ff6cda).

Seems to run fine, but apport gets the segfault at ld.bfd:

[70428.554802] ld[28939]: segfault at 0 ip 00007fea8d784692 sp 00007fff2a067be8 error 4 in libc-2.12.so[7fea8d6fe000+17a000]

/usr/bin/ld --sysroot=/ --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=both -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o /tmp/qemu-conf--28675-.exe -z relro /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crt1.o /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.4.4/crtbegin.o -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib -L//lib/../lib -L//usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../.. -L//lib -L//usr/lib -L/usr/lib/x86_64-linux-gnu /tmp/ccqhLdme.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/x86_64-linux-gnu/4.4.4/crtend.o /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crtn.o

Segfault happened at: 0x7fea8d784692 <mempcpy+194>: mov (%rsi),%rax
PC (0x7fea8d784692) ok
source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok

mempcpy () from /lib/libc.so.6
_IO_file_xsputn () from /lib/libc.so.6
fwrite () from /lib/libc.so.6
?? ()

Revision history for this message
Matthias Klose (doko) wrote :

is this still an issue with binutils from precise or quantal?

Changed in binutils (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for binutils (Ubuntu) because there has been no activity for 60 days.]

Changed in binutils (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.