X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,TW_CX X-Spam-Check-By: sourceware.org Message-ID: <4E807FB8.1020608@cs.utoronto.ca> Date: Mon, 26 Sep 2011 09:35:52 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: rebaseall and cygstdc++-6.dll References: <4E6AC3F4 DOT 1090401 AT gmail DOT com> <4E7EC532 DOT 9020306 AT gmail DOT com> <4E7FD234 DOT 70102 AT gmail DOT com> <1317006915 DOT 8692 DOT 1 DOT camel AT YAAKOV04> <4E801B9A DOT 4060002 AT gmail DOT com> In-Reply-To: <4E801B9A.4060002@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 26/09/2011 2:28 AM, Marco Atzeri wrote: > On 9/26/2011 5:15 AM, Yaakov (Cygwin/X) wrote: >> On Mon, 2011-09-26 at 02:15 +0100, Dave Korn wrote: >>> The problem is in binutils, and the fact that it generates base >>> relocs for >>> entries from EH data that should be just ignored. >>> >>> http://sourceware.org/ml/binutils/2011-09/msg00174.html >>> contains more detail, if you want to ask more let's do it on the >>> binutils list. >>> >>> So to answer your question: the gcc language-specific runtime >>> DLLs have to >>> be built using the patched version of binutils, otherwise they break >>> when they >>> get rebased; that's why I'm rebuilding the gcc packages - having >>> already >>> locally rebuilt binutils. This will only be a big issue for anyone >>> who wants >>> to rebuild gcc from source themselves, the new packages I upload to >>> the distro >>> will still work for everyone regardless of what binutils they have >>> installed >>> and/or how or when or where they get rebased. >> >> Except that this issue doesn't affect only libstdc++, but any C++ >> library which throws exceptions (as I have seen on my system). So we >> really do need a patched binutils ASAP. >> > > There is an easy way to identify such libraries ? > Just to know if I need to rebuild some of mines . If the problem affects any library which throws (as opposed to one which merely supports propagating/unwinding due to exceptions), then the presence of __cxa_throw in the output of nm would be a good indicator. If unwind handlers are also affected, then anything with a .eh_frame section is suspect (but that would be all C++ programs unless compiled in no-except mode). Ryan -- 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