public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: How to correctly rebase?
Date: Fri, 16 Oct 2015 15:50:00 -0000	[thread overview]
Message-ID: <898337219.20151016184136@yandex.ru> (raw)
In-Reply-To: <562112CE.4040407@cornell.edu>

Greetings, Ken Brown!

> I have one other suggestion: If you rebase because of a fork failure, reboot
> before retrying the application that failed.  I just had the following experience:

> I was running emacs on my 32-bit Cygwin installation and got a fork failure 
> involving /usr/bin/cygMagickCore-6.Q16-2.dll.  Windows had loaded this DLL at a
> very low address.  I did a full rebase and restarted emacs, but that DLL was 
> still loaded at a low address, even though rebasing had put the base address at
> a very reasonable 0x6e550000.  [You can see where a DLL is loaded in a process's
> address space by examining the file /proc/<PID>/maps.]  I then rebooted, 
> restarted emacs, and verified that the DLL was now loaded at 0x6e550000, as 
> expected.

> I've seen this happen many times.  I don't know the explanation, but my guess is
> that Windows does some caching that causes it to try to load a given DLL at the
> same base address as it used the last time that DLL was loaded.  Rebooting 
> clears the cache.  Can someone who understands this stuff confirm my guess or 
> provide a better explanation?

prefetch/superfetch ?
I normally disable this crap. I can live with boot times 15 seconds longer,
and these kinds of services proved to slow down the system over the years at
all times, no matter what is claimed in advertising.


-- 
With best regards,
Andrey Repin
Friday, October 16, 2015 18:40:11

Sorry for my terrible english...


--
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

  parent reply	other threads:[~2015-10-16 15:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 14:26 Dr Rainer Woitok
2015-10-14 17:27 ` Warren Young
2015-10-14 19:27   ` Achim Gratz
2015-10-14 21:30     ` Warren Young
2015-10-14 22:08       ` Warren Young
2015-10-14 22:37         ` Warren Young
2015-10-15  7:53           ` Achim Gratz
2015-10-15  7:15       ` Achim Gratz
2015-10-15 13:16   ` Dr Rainer Woitok
2015-10-15 20:54     ` Warren Young
2015-10-15 21:10       ` Ken Brown
2015-10-16 12:57         ` Dr Rainer Woitok
2015-10-16 12:58           ` Ken Brown
2015-10-16 15:08             ` Ken Brown
2015-10-16 15:16               ` cyg Simple
2015-10-16 15:29                 ` Ken Brown
2015-10-16 15:50               ` Andrey Repin [this message]
2015-10-18 11:15               ` Dr Rainer Woitok
2015-10-18 11:59                 ` Achim Gratz
2015-10-18 12:45                 ` Ken Brown
2015-10-18 16:20                 ` Dr Rainer Woitok
2015-10-19 23:59                 ` Warren Young
2015-10-20 16:55                   ` Dr Rainer Woitok
2015-10-16  7:21       ` Achim Gratz
2015-10-16 20:11         ` Warren Young
2015-12-18 16:28           ` Achim Gratz
2015-10-14 19:58 ` Achim Gratz

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=898337219.20151016184136@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=kbrown@cornell.edu \
    /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).