Message-ID: <49A5ACDF.4020001@gmail.com>
Date: Wed, 25 Feb 2009 20:41:03 +0000
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dave Korn <dave.korn.cygwin@googlemail.com>
CC: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [1.7] Updated: file-5.00-1
References: <announce.20090210093102.GB11175@calimero.vinschen.de> <499E2B9A.5030907@cwilson.fastmail.fm> <20090220095916.GA759@calimero.vinschen.de> <499EB5A6.5000707@gmail.com> <499EBABE.8080303@gmail.com> <499EC6E5.5000408@gmail.com>
In-Reply-To: <499EC6E5.5000408@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Dave Korn wrote:

>   The purpose of playing these games is in order not to drag in the whole
> exception handling machinery into a statically-linked application unless we
> actually need it.  We're relying on detecting an unlinked weak symbol by it
> having a value of zero at runtime.  That usually works, but the pointer
> variable register_frame_info_ptr must have some kind of reloc pointing at it,
> because rebase adjusts it, so instead of zero it becomes equal to the
> difference between the new and old base addresses.


  That rang a bell, and reminded me of something Danny posted a little while back:

http://sourceware.org/ml/binutils/2008-07/msg00372.html

  So I believe now this is a symptom of a buggy ld already fixed upstream.
I'll try the testcase again against one of my CVS builds of binutils and
report back, but I expect it will fix the problem and rebase will no longer
alter the unlinked weak null-initialised pointer.

    cheers,
      DaveK


--
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/