Re: Help debugging a dll issue

["René Berber" <rene.berber@gmail.com>]

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