--
What|Removed |Added
CC||nickc at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5487
--- You are receiving this ma
--- Additional Comments From ambro at b4ever dot net 2007-12-16 22:32
---
That was just after 'dllwrap', before 'dlltool'
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5487
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching s
--- Additional Comments From ambro at b4ever dot net 2007-12-16 22:30
---
Created an attachment (id=2140)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=2140&action=view)
libwine.dll linked with broken binutils and one commit before
--
http://sourceware.org/bugzilla/show_bug
--- Additional Comments From ambro at b4ever dot net 2007-12-16 22:15
---
I've been doing bisecting and found out this commit causes the regression:
http://sourceware.org/ml/binutils-cvs/2007-01/msg00093.html
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5487
--- You are re
bash-3.2$ cat note-2.s
.globl _entry
.text
_entry:
.byte 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
.section .foo,"awx",%progbits
.byte 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
.section .note,"",%note
.byte 0
bash-3.2$ cat note-2.t
ENTRY(_entry)
PHDRS
{
data PT
There is a bug in binutils 2.18 and current cvs about linking DLLs. It causes
some crash in Wine DDLs. See http://bugs.winehq.org/show_bug.cgi?id=10783
I tested several binutils versions and it turned out the bug is not present in
2.17, but present in 2.17.50, up to current cvs.
What's interestin
