ld crashes when building ZDoom with winelib
Hi all, First excuse me, if this is the wrong place to report this, but AFAIK ld should not crash, no matter what I try to link. So this seems to be a bug of ld to me. I'm trying to build the Windows version of ZDoom 2.1.7 under Linux with Winelib. Of course, I know that ZDoom can be compiled natively under Linux, but I'm aiming to port Skulltag (which is based on ZDoom) to Linux and if ZDoom can't be build with Winelib, Skulltag can't be either. With little modifications I was able to compile ZDoom with winegcc, but during linking ld crashes, with a malloc error. This only happens if I link the dxguid library, but I need to link it, since I get undefined references otherwise. It happens to me under Ubuntu 7.04 and openSUSE 10.2 with the GNU binutils and Wine versions supplied by these distros. Under Ubuntu I also tried Wine 0.9.35 and 0.9.36 and the latest weekly of binutils. In case someone wants to reproduce it, I can supply the source. I get this message during linking: - *** glibc detected *** /usr/bin/ld: malloc(): memory corruption: 0x0b293c00 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0x40136ef3] /lib/tls/i686/cmov/libc.so.6(__libc_malloc+0x7e)[0x4013860e] /lib/tls/i686/cmov/libc.so.6(qsort+0x61)[0x400fb011] /usr/lib/libbfd-2.17.50.so(bfd_elf_final_link+0x2e2a)[0x4007f84a] /usr/bin/ld[0x805f90b] /usr/bin/ld[0x805ef20] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0x400e4ebc] /usr/bin/ld[0x804b011] === Memory map: 08048000-080b7000 r-xp 08:01 932679 /usr/bin/ld 080b7000-080b9000 rw-p 0006f000 08:01 932679 /usr/bin/ld 080b9000-0b36b000 rw-p 080b9000 00:00 0 [heap] 4000-40019000 r-xp 08:01 572341 /lib/ld-2.5.so 40019000-4001b000 rw-p 00019000 08:01 572341 /lib/ld-2.5.so 4001b000-40029000 rw-p 4001b000 00:00 0 40029000-400c3000 r-xp 08:01 933679 /usr/lib/libbfd-2.17.50.so 400c3000-400cb000 rw-p 0009a000 08:01 933679 /usr/lib/libbfd-2.17.50.so 400cb000-400cf000 rw-p 400cb000 00:00 0 400cf000-4020a000 r-xp 08:01 575620 /lib/tls/i686/cmov/libc-2.5.so 4020a000-4020b000 r--p 0013b000 08:01 575620 /lib/tls/i686/cmov/libc-2.5.so 4020b000-4020d000 rw-p 0013c000 08:01 575620 /lib/tls/i686/cmov/libc-2.5.so 4020d000-4032e000 rw-p 4020d000 00:00 0 4033a000-40345000 r-xp 08:01 572384 /lib/libgcc_s.so.1 40345000-40346000 rw-p a000 08:01 572384 /lib/libgcc_s.so.1 4034f000-403f8000 rw-p 4034f000 00:00 0 4040-40421000 rw-p 4040 00:00 0 40421000-4050 ---p 40421000 00:00 0 bfeeb000-bff03000 rw-p bfeeb000 00:00 0 [stack] e000-f000 r-xp 00:00 0 [vdso] collect2: ld terminated with signal 6 [Aborted], core dumped - Any suggestions? Thanks, Benjamin ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: ld crashes when building ZDoom with winelib
Hi Benjamin, First excuse me, if this is the wrong place to report this, No this is the right place. If you want to, you could also submit a bug report at: http://sourceware.org/bugzilla but AFAIK ld should not crash, no matter what I try to link. True. It happens to me under Ubuntu 7.04 and openSUSE 10.2 with the GNU binutils and Wine versions supplied by these distros. Can you please tell us which versions these are ? Could you be running out of memory ? If so, then maybe adding the --reduce-memory-overheads switch to the linker command line might help. In case someone wants to reproduce it, I can supply the source. I get this message during linking: It would be more helpful to have a tarball of the object files and libraries, plus a copy of the linker command line. Cheers Nick ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: ld crashes when building ZDoom with winelib
Hi Nick, >> It happens to me under Ubuntu 7.04 and openSUSE 10.2 with the GNU >> binutils and Wine versions supplied by these distros. > > Can you please tell us which versions these are ? Sure, according to Ubuntu the versions are: wine = 0.9.36~winehq0~ubuntu~7.04.1 (feisty) binutils = 2.17.20070103cvs-0ubuntu2 I also tried wine 0.9.33. > Could you be running out of memory ? If so, then maybe adding the > --reduce-memory-overheads switch to the linker command line might > help. I can't rule out this totally, but the --reduce-memory-overheads switch doesn't help. > It would be more helpful to have a tarball of the object files and > libraries, plus a copy of the linker command line. Here you go: http://files.filefront.com//;7400443;/ This archive contains all the ZDoom object files and a file with the linker command. The fmod library I link is (http://www.fmod.org/files/fmodapi375linux.tar.gz) I didn't include the libraries supplied by Ubuntu. Do you need them too? Best regards, Benjamin ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug gas/4448] New: overstrict check for powerpc lswi
[ forwarded from http://bugs.debian.org/421799 ] seen with 20070426 CVS The opcode check for the lswi instruction is overstrict: | $ cat test.S | lswi 5,24,0 | $ as test.S | test.S: Assembler messages: | test.S:1: Error: operand out of range (0 is not between 1 and 32) The IBM reference say: | lswi RT, RA, NB | NB is the byte count. | N is NB, which is the number of bytes to load. If NB is 0, then N is 32. -- Summary: overstrict check for powerpc lswi Product: binutils Version: 2.18 (HEAD) Status: NEW Severity: normal Priority: P2 Component: gas AssignedTo: unassigned at sources dot redhat dot com ReportedBy: doko at debian dot org CC: bug-binutils at gnu dot org GCC target triplet: powerpc-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=4448 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
