process-startup headache.

Robert Collins
Sat Jun 9 23:13:00 GMT 2001

----- Original Message -----
From: "Christopher Faylor" <>
To: <>
Sent: Sunday, June 10, 2001 2:43 PM
Subject: Re: process-startup headache.

> I haven't waded through my email but I assume that this probably
> is quoted from the cygwin list since it seems to have shown up
> here with no preceding messages.

Nope, it's a quote from a prior thread here, which I managed to confuse
you with. Sorry..

> Can I ask that when people decide to move a discussion here that they
> provide enough context to understand what people are talking about?

Thats a very reasonable request. I thought I had achieved that by
quoting the paragraph in my earlier full email about slow startup &&
trouble with paul's ld. Both of which I thought were non-application,
cygwin1.dll only issues.

I suspect I erred on the side of bandwidth :].

> For instance, the words "A similar-in-appearance problem is
> occurring..." would be helped with something indicating what the
> similarity was referring to.

The problem as initially reported was similar to the slow startup
issue - that has turned out to be a call to NetEnumServers, which
Corinna indicates she may have fixed, but I haven't had time to look
into yet.


> cgf
> On Sat, Jun 09, 2001 at 11:35:20PM +1000, Robert Collins wrote:
> >----- Original Message -----
> >From: "Robert Collins" <>
> >
> >
> >> Hi folk,
> >>
> >> A similar-in-appearance problem is occuring with binaries linked by
> >> patched ld.exe, (which I just installed tonight, so the first thing
> >> not an artifact of that). I'm trying out Paul Solovosky{I hope
> >> right}'s ld-that-auto-imports.
> >>
> >
> >This problem is not related to the slow startup problem. The problem
> >that the .dll's generated by Paul's ld, have a default base address
> >0x610c0000 which collides with cygwin's base addres of 0x61000000.
> >Cygwin doesn't seem to be relocatable in practice, even though the
> >is marked as relocatable.
> >
> >Workaround: To build .dll's with the patched ld that work with cygwin
> >1.3.2 use -Wl,--image-base=0x10000000 on the gcc commandle line.
> >(0x10000000 is the default .dll address according to MSDN. [don't
> >use --dll - --dll creates the 0x610c0000 address that doesn't work).
> >
> >Long term solution:I think cygwin1.dll should be marked
> >to prevent .dll's that collide with the cygwin1.dll causing crashes
> >unexplained behaviour.

More information about the Cygwin-developers mailing list