[Bug 287264] Re: ld crashed with SIGSEGV in memcpy()

2009-07-05 Thread Matthias Klose
you need to be consistant with the architecture. Either always compile and link with -m32 or never. ** Changed in: binutils (Ubuntu) Status: New => Invalid -- ld crashed with SIGSEGV in memcpy() https://bugs.launchpad.net/bugs/287264 You received this bug notification because you are a m

[Bug 287264] Re: ld crashed with SIGSEGV in memcpy()

2009-05-15 Thread Erwan Legrand
I'm removing the Incomplete status since I did provide a test case for this one. ** Changed in: binutils (Ubuntu) Status: Incomplete => New -- ld crashed with SIGSEGV in memcpy() https://bugs.launchpad.net/bugs/287264 You received this bug notification because you are a member of Ubuntu B

[Bug 287264] Re: ld crashed with SIGSEGV in memcpy()

2009-03-06 Thread Erwan Legrand
Here is a simple test case to trigger this crash: $ gcc -c -fPIC -o truc.o truc.c $ file truc.o truc.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped $ gcc -m32 -o truc truc.o collect2: ld terminated with signal 11 [Segmentation fault], core dumped /usr/bin/ld: i386:x86-64 arc

[Bug 287264] Re: ld crashed with SIGSEGV in memcpy()

2008-12-23 Thread Matthias Klose
according to the buildds gcc-3.4 did build fine. I'll close this report unless you can show a configuration with the failing build. ** Visibility changed to: Public ** Changed in: binutils (Ubuntu) Status: New => Incomplete -- ld crashed with SIGSEGV in memcpy() https://bugs.launchpad.n