X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:reply-to:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=ix+f9noiKVYexu68XgYPk7J7NaWr9F
	AJttvdp4vyLWxEv5nuEBhwVQz97Ye+8k/2p+YR+0cEb8TQfAO3kUoFHipqPo3G7y
	Mxw8MRV0wKof1BYXv+Ld8TSQ631ofuf3GsCF9Dl4ZVxtEweIIVvRczIjavP6MsVP
	gxoTiEl8Yq60M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:reply-to:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=X+tgnxtI71Eazul58rVQ9KhPCoo=; b=oVW0
	P8errKTnqHU4aURDYFq/GUy42mpzNfSLVRDeS1XzDtW905LpXQcarxSTJ8OLT9yI
	uSItux8XM+iP+mPibuDdLwIPddR+WgubCuN94GLf92eDRDNmOvdTN+436vg2lpQv
	LiT/ZTxapMEFIqDCuAVP9FPHhKvUwCuVhU8dVjk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=H*i:sk:830e7bc, H*f:sk:830e7bc, H*MI:sk:830e7bc, dlls
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: =?UTF-8?Q?Ren=c3=a9_Berber?= <rene DOT berber AT gmail DOT com>
Subject: Re: Help debugging a dll issue
Date: Sat, 21 May 2016 20:45:26 -0500
Lines: 28
Message-ID: <nhr30c$qm5$1@ger.gmane.org>
References: <b21c0ab1-341b-d6f5-915b-f73973b8079b AT cs DOT umass DOT edu> <830e7bcd-aeb5-264e-6436-799dfa54d7a0 AT cs DOT umass DOT edu>
Reply-To: Do not reply <rene DOT berber AT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
In-Reply-To: <830e7bcd-aeb5-264e-6436-799dfa54d7a0@cs.umass.edu>
X-IsSubscribed: yes

On 5/21/2016 6:30 PM, Eliot Moss wrote:

[snip]
> I used binary search, eliminating .o files from the .dll on the thought
> that it was either a particular .o file that was leading to a problem,
> or possibly the overall size (this is a huge link!).  I found that a .dll
> with 58725 section 1 symbols (as reported by objdump -t) works, and one
> with 66675 section one symbols fails.  So it appears to be a size issue.

That's telling, since USHRT_MAX (65535) may be the limit, then somewhere
there is the use of a variable of that type (unsigned short int,
uint16_t), which may be part of some specification (i.e. the format of
libraries).

Supporting that is: https://ghc.haskell.org/trac/ghc/ticket/5292 which
mentions:

"65536 symbols. This is the limit that Windows DLLs can handle (the
source of the limitation is that they use 16-bit integers to represent
"ordinals")"

and also point to an interesting bug report (5 years old):

https://sourceware.org/bugzilla/show_bug.cgi?id=12969

No answers, but at least an explanation.
-- 
René Berber


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