Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<ba40711f05052516524ca3c0ec@mail.gmail.com>
Date:	Wed, 25 May 2005 19:52:37 -0400
From:	Lev Bishop <lev DOT bishop AT gmail DOT com>
Reply-To:	Lev Bishop <lev DOT bishop AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] Updated: binutils-20050520-1
In-Reply-To:	<SERRANO25q8awYFDIfW00000138@SERRANO.CAM.ARTIMI.COM>
Mime-Version:	1.0
References:	<ba40711f050525035423005994 AT mail DOT gmail DOT com> <SERRANO25q8awYFDIfW00000138 AT SERRANO DOT CAM DOT ARTIMI DOT COM>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id j4PNqjGQ021074

On 25/05/05, Dave Korn wrote:
> ----Original Message----
> >From: Lev Bishop
> >Sent: 25 May 2005 11:54

> Yow.  So you copy it from a PE to an ELF, and then back to PE?  You very
> much need to read the section on canonicalisation in the bfd section of the
> ld manual.  "info ld" then search for "BFD information loss".

Yeah, I saw that. I wasn't really expecting the exe to still run after
this or anything, just that it would be something I could get a
reliable fingerprint from. In fact the reason I was doing this is that
I *wanted* to lose information (the date/time field in particular).

> > Segmentation fault (core dumped)
> >
> > This happens with the new binutils and also the previous version.
> 
>  Yup, so something vital didn't get carried over to the ELF format, or
> didn't get converted back.  To be expected really.

Well, I wasn't really expecting it to work, just stabbing in the dark.
However, from the binutils info file "Bug Criteria" section:
]   If you are not sure whether you have found a bug, here are some
] guidelines:
]
]   * If a binary utility gets a fatal signal, for any input whatever,
]     that is a bug.  Reliable utilities never crash.

And from the "Bug Reporting"  section:
]   A number of companies and individuals offer support for GNU
] products.  If you obtained the binary utilities from a support
] organization, we recommend you contact that organization first.

I assumed "support organization"==Cygwin, and thought I'd better be a
good citizen and mention the crash.

Anyway, thanks DaveK for the hint to look at the gcc bootstrap files.

Lev

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -