From: Yaakov (Cygwin/X) <yselkowitz@users.sourceforge.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Binutils objcopy bug (was Re: rebase segfault)
Date: Thu, 24 Jan 2013 09:02:00 -0000 [thread overview]
Message-ID: <20130124030145.22fa143f@YAAKOV04> (raw)
In-Reply-To: <50F6AD63.8080106@gmail.com>
On Wed, 16 Jan 2013 14:38:43 +0100, marco atzeri wrote:
> On 1/16/2013 1:35 PM, Corinna Vinschen wrote:
> > On Jan 16 08:15, marco atzeri wrote:
> >> On 1/15/2013 11:03 PM, marco atzeri wrote:
> >>> On 1/15/2013 12:24 PM, Corinna Vinschen wrote:
> > This is a serious bug in objcopy in the current binutils. Given that
> > cygport creates the debug info automatically, we might end up with
> > spuriously broken DLLs in the distro.
>
> we already have some :
>
> /usr/bin/cygcrypto-1.0.0.dll
> 8 .gnu_deb 0000001c 67542000 67542000 0017ac00 2**2
>
> /usr/bin/cyglsa.dll
> 6 .gnu_deb 00000014 10007000 10007000 00001400 2**2
>
> /usr/bin/cygssl-1.0.0.dll
> 8 .gnu_deb 0000001c 58fcf000 58fcf000 00059a00 2**2
I checked every /usr/bin/*.dll on my system (which is a lot), and these
three, plus cyglsa64.dll (which can only be read by
x86_64-w64-mingw32-objdump), are the only ones which show this. I did
manage to reproduce this on my machine with openssl, and passing
--long-section-names=enable to objcopy does fix this, but why are only
these DLLs affected?
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-01-24 9:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 8:44 rebase segfault marco atzeri
2013-01-15 10:08 ` Corinna Vinschen
2013-01-15 10:36 ` marco atzeri
2013-01-15 11:24 ` Corinna Vinschen
2013-01-15 22:04 ` marco atzeri
2013-01-16 7:16 ` marco atzeri
2013-01-16 12:35 ` Binutils objcopy bug (was Re: rebase segfault) Corinna Vinschen
2013-01-16 13:38 ` marco atzeri
2013-01-16 14:42 ` Corinna Vinschen
2013-01-16 15:12 ` marco atzeri
2013-01-16 16:26 ` Corinna Vinschen
2013-01-24 9:02 ` Yaakov [this message]
2013-01-24 9:28 ` Corinna Vinschen
2013-01-24 9:49 ` marco atzeri
2013-01-24 10:01 ` Corinna Vinschen
2013-01-24 10:16 ` marco atzeri
2013-01-24 12:09 ` Corinna Vinschen
2013-01-24 12:35 ` marco atzeri
2013-01-24 14:12 ` Corinna Vinschen
2013-01-25 12:34 ` marco atzeri
2013-01-25 13:20 ` Kai Tietz
2013-01-25 15:01 ` Corinna Vinschen
2013-01-25 15:12 ` marco atzeri
2013-01-26 6:32 ` Reini Urban
2013-01-26 7:53 ` marco atzeri
2013-01-29 22:30 ` Reini Urban
2013-01-30 16:46 ` Andrew Dunstan
2013-01-30 17:03 ` marco atzeri
2013-03-04 20:01 ` Andrew Dunstan
2013-03-04 21:30 ` marco atzeri
2013-03-04 21:41 ` Andrew Dunstan
2013-03-04 22:32 ` Andrew Dunstan
2013-03-05 5:42 ` marco atzeri
2013-03-05 15:39 ` Andrew Dunstan
2013-01-25 13:22 ` Kai Tietz
2013-01-24 15:56 ` Christopher Faylor
2013-01-24 16:17 ` marco atzeri
2013-01-18 15:34 ` marco atzeri
2013-01-18 15:44 ` Christopher Faylor
2013-01-19 8:56 ` marco atzeri
2013-01-19 15:23 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130124030145.22fa143f@YAAKOV04 \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).