Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Apr  3 11:18, Michael Haubenwallner wrote:
> On 4/1/19 5:56 PM, Corinna Vinschen wrote:
> > On Apr  1 16:56, Corinna Vinschen wrote:
> >> On Apr  1 16:28, Michael Haubenwallner wrote:
> >>> On 3/28/19 9:30 PM, Corinna Vinschen wrote:
> >>>> can you please collect the base addresses of all DLLs generated during
> >>>> the build, plus their size and make a sorted list?  It would be
> >>>> interesting to know if the hash algorithm in ld is actually as bad
> >>>> as I conjecture.
> >>>
> >>> Please find attached the output of rebase -i for the dlls after bootstrap
> >>> on Cygwin 3.0.4, each built with ld from binutils-2.31.1.
> > 
> > Oh, wait.  That's not what I was looking for.  The addresses are ok, but
> > the paths *must* be the ones at the time the DLLs have been created,
> > because that's what ld uses when creating the image base addresses.  The
> > addresses combined with the installation paths don't make sense anymore.
> 
> So I have intercepted the ld.exe to show 'rebase -i' on any just created dll,
> tell about the exact -o argument to ld, and the current directory.
> 
> This is with binutils-2.31.1
> 
> Anything else needed?

No, that should be sufficient, thanks for collecting this!


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

Attachment: signature.asc
Description: PGP signature