From: alw@al-williams.com (Al Williams)
Subject: Re: [OT?] rebasing cygwin, was: cygwin/xfree86/emacs problems after upgrading
Date: 16 Feb 2004 17:24:41 -0800 [thread overview]
Message-ID: <a9835df1.0402161724.4461b931@posting.google.com> (raw)
In-Reply-To: mailman.2448.1076893498.928.help-gnu-emacs@gnu.org
Thomas L Roche <tlroche@us.ibm.com> wrote in message news:<mailman.2448.1076893498.928.help-gnu-emacs@gnu.org>...
> Could you give me, or pass pointers to, a bit more information about
> rebase? I'm asking because I can't find much online, except
Well, actually it did not completely eliminate the problem although it
did reduce its frequency significantly (once or twice a day instead of
five or six times an hour).
Each DLL has a preferred load address. If it can be loaded at that
address, fine. If not, Windows will put it at a different address.
Apparently (and I don't know this for sure) the Cygwin stuff assumes
all DLLs will be at the same address in each process space (as would
always be the case in Win98, for example). So if DLLs conflict and are
loaded in different order, it is possible for process A to have DLLx
at addresss Z and process B has DLLy at the same address and Cygwin
apparently detects this and stops.
Rebasing moves the DLL load addresses to make this less likely.
If you google on:
rebaseall cygwin
You'll see this is a common issue with certain packages. I don't think
it will really hurt anything. If you are really worried, copy all the
DLL files under c:\cygwin (or whatever your CYGROOT is) before you
start.
Al Williams
http://www.al-williams.com
next parent reply other threads:[~2004-02-17 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2448.1076893498.928.help-gnu-emacs@gnu.org>
2004-02-17 1:24 ` Al Williams [this message]
[not found] <E1Arq3I-0000UF-R6@monty-python.gnu.org>
2004-02-16 1:04 ` [OT?] rebasing cygwin, was: cygwin/xfree86/emacs problems after upgrading Thomas L Roche
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a9835df1.0402161724.4461b931@posting.google.com \
--to=alw@al-williams.com \
/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).