From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Rebase, Peflags, and cygserver
Date: Mon, 06 Apr 2015 16:27:00 -0000 [thread overview]
Message-ID: <5522B40B.6080806@cornell.edu> (raw)
In-Reply-To: <CAK-n8j4nUYrAkVXPAeiB-zsOzmOU5CkvVssJ7R9eWcKT+Xa+sQ@mail.gmail.com>
On 4/6/2015 1:02 AM, Jim Reisert AD1C wrote:
> On Fri, Mar 27, 2015 at 2:28 PM, Achim Gratz wrote:
>
>> From the announcement of _autorebase:
>>
>> To perform a full rebase, execute "rebase-trigger fullrebase". Then
>> shut down Cygwin and simply run setup.exe. The rebase will be
>> performed even when the installation did not get modified in any way.
>
> This did not solve my particular problems.
>
> From a "Cygwin Terminal" (MINTTY), after shutting down the X.org
> server, I ran the:
>
> rebase-trigger fullrebase
>
> command. Then I ran setup-x86, nothing to update, but let it rebase
> anyway. Then I restarted my X.org server, and an xterm, then finally
> Cygwin Emacs (emacs-X11). I still can not get rid of this fork error:
>
> 0 [main] emacs-X11 10520 child_info_fork::abort:
> C:\Cygwin\bin\cyggs-9.dll: Loaded to different address:
> parent(0x1E60000) != child(0x1BC0000)
Did you make sure that all Cygwin processes were stopped before letting
_autorebase do its thing? And did you try rebooting first?
Ken
--
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
next prev parent reply other threads:[~2015-04-06 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 15:17 J. David Boyd
2015-03-27 15:27 ` Marco Atzeri
2015-03-27 19:05 ` J. David Boyd
2015-03-27 20:28 ` Marco Atzeri
2015-03-27 15:45 ` Rockefeller, Harry
2015-03-27 15:48 ` Jim Reisert AD1C
2015-03-27 20:46 ` Achim Gratz
2015-03-28 0:52 ` Ken Brown
2015-03-30 18:07 ` Rockefeller, Harry
2015-03-30 20:35 ` Marco Atzeri
2015-04-06 5:03 ` Jim Reisert AD1C
2015-04-06 16:27 ` Ken Brown [this message]
2015-04-11 9:04 ` 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=5522B40B.6080806@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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).