From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Charles Wilson" <cwilson@ece.gatech.edu>,
"Jason Tishler" <jason@tishler.net>
Cc: "Michael Hudson" <mwh@python.net>,
<david_abrahams@users.sourceforge.net>,
"Cygwin" <cygwin@sources.redhat.com>
Subject: Re: dll_list::load_after_fork() blues (was Re: [ python-Bugs-489709 ] Building Fails ...)
Date: Fri, 07 Dec 2001 15:11:00 -0000 [thread overview]
Message-ID: <01fc01c17f74$0d774a20$0200a8c0@lifelesswks> (raw)
In-Reply-To: <3C0FB399.2020300@ece.gatech.edu>
----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
> > The above occurs during Cygwin's fork() when the Cygwin DLL cannot
> > load a DLL to the same address in the child that it had in the
parent.
> > I have seen this during Python 2.1.1 regression tests with threads
> > enabled.
>
>
> Part of the problem may be that cyggdbm.dll was built with
> --auto-image-base. It was later demonstrated that this can cause
> problems with fork; you're better off just letting ld assign the
default
> dllbase, which means that EVERY process will remap the dll at runtime.
> Thus, no hardcoded conflicts. Downside: *very* slightly delay in
> loading DLLs -- probably unnoticeable.
>
> (Did I get that right, robert?)
Yes. There is actually a longer term solution... which is to 'rebase'
every cygwin linked .dll on a particular system to not conflict with
each other - which has to be done by setup.exe.
Rob
> Anyway, I plan to redo cyggdbm "eventually" without the
> --auto-image-base. Doing so *may* fix this problem, but I'm not
sure...
>
> --Chuck
>
>
>
>
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-12-07 23:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0112061015100.898-100000@starship.python.net>
2001-12-06 9:44 ` Jason Tishler
2001-12-06 10:12 ` Charles Wilson
2001-12-07 6:54 ` Michael Hudson
2001-12-07 7:03 ` David Abrahams
2001-12-07 7:32 ` Jason Tishler
2001-12-07 15:11 ` Robert Collins [this message]
2001-12-07 17:02 ` Charles Wilson
2001-12-07 17:29 ` Christopher Faylor
2001-12-12 5:14 ` rebase utility (was Re: dll_list::load_after_fork() blues ...) Jason Tishler
2001-12-12 5:45 ` Robert Collins
2001-12-12 6:04 ` Jason Tishler
2001-12-07 18:41 ` dll_list::load_after_fork() blues (was Re: [ python-Bugs-489709 ] Building Fails ...) Robert Collins
2001-12-07 18:19 ` Norman Vine
2001-12-07 18:44 ` Robert Collins
2001-12-10 4:46 ` Jason Tishler
2001-12-10 5:13 ` Robert Collins
2001-12-10 7:44 ` Jason Tishler
2001-12-16 0:12 ` Robert Collins
2001-12-10 7:23 ` Michael Hudson
2001-12-10 10:46 ` Norman Vine
2001-12-12 5:56 ` Jason Tishler
2001-12-18 13:12 ` Cygwin fork() rebase solution (was Re: dll_list::load_after_fork() blues ...) Jason Tishler
2001-12-18 14:07 ` Robert Collins
2001-12-18 19:56 ` cygwin " Christopher Faylor
2001-12-21 5:02 ` Jason Tishler
2001-12-22 17:08 ` Chris McDonough
2002-01-02 10:45 ` Jason Tishler
2001-12-19 22:46 ` Cygwin " Norman Vine
2001-12-16 0:31 ` dll_list::load_after_fork() blues (was Re: [ python-Bugs-489709 ] Building Fails ...) Robert Collins
2001-12-18 5:31 ` Jason Tishler
2001-12-18 6:35 ` Robert Collins
2001-12-07 6:04 ` Jason Tishler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01fc01c17f74$0d774a20$0200a8c0@lifelesswks' \
--to=robert.collins@itdomain.com.au \
--cc=cwilson@ece.gatech.edu \
--cc=cygwin@sources.redhat.com \
--cc=david_abrahams@users.sourceforge.net \
--cc=jason@tishler.net \
--cc=mwh@python.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).