public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Pat Tressel <ptressel@myuw.net>
To: cygwin@cygwin.com
Subject: Re: Cygwin errors after altering Windows command prompt shortcut (???)
Date: Mon, 30 Apr 2012 12:19:00 -0000	[thread overview]
Message-ID: <CABT-+2qo-Ee3fdzdD1_Jh0=6fWRNFu=Fw-he25=_3anZfW+iNA@mail.gmail.com> (raw)
In-Reply-To: <CABT-+2rgkM5rG7AFgxPev1vBd534+6q=NkV7-20-N-RAOH=TnQ@mail.gmail.com>

> bash-4.1$ ls
>       0 [main] bash 8316 child_info_fork::abort: cygreadline7.dll: Loaded to different address: parent(0x3C0000) != child(0x320000)
> bash: fork: retry: Resource temporarily unavailable
>       0 [main] bash 7708 child_info_fork::abort: cygreadline7.dll: Loaded to different address: parent(0x3C0000) != child(0x320000)
> bash: fork: retry: Resource temporarily unavailable
>
> Starting a new Cygwin shell instance got errors from bash before entering a command.

Forget those other things that might have been possible causes -- they
now look like red herrings.  This happened again recently, once after
the system hibernated, and once after a reboot.  (In the second case,
I believe there were no Cygwin windows open when the system was shut
down, but it's possible that the process had not finished exiting and
was killed by shutdown.)

Recall from the previous occurrence that restoring from the last
restore point caused the error to go away, but that's not a good
workaround, as it takes at least half an hour to make a restore point
or restore from it, and restoring throws away anything installed since
the last restore point.

This is a very recent version of Cygwin -- it was updated 6 days ago.

Any ideas what might be wrong?  Perhaps something that wasn't cleaned
up during shutdown if the process did get killed?

Thanks!

-- Pat

--
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:[~2012-04-30 12:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABT-+2rFSA4V6eoS0f9a1RX7+cmk7NpkQBgGx5DSiHhBSThJyg@mail.gmail.com>
2012-02-28 11:33 ` Pat Tressel
2012-02-28 12:23   ` Corinna Vinschen
2012-02-28 22:50     ` Pat Tressel
2012-02-29  2:27   ` Andrey Repin
2012-02-29  3:49     ` Pat Tressel
2012-02-29 12:52       ` Earnie Boyd
2012-02-29 21:28         ` Andrey Repin
     [not found] ` <CABT-+2rgkM5rG7AFgxPev1vBd534+6q=NkV7-20-N-RAOH=TnQ@mail.gmail.com>
2012-04-30 12:19   ` Pat Tressel [this message]
2012-04-30 13:04     ` Pat Tressel
     [not found] <0105D5C1E0353146B1B222348B0411A20A5C157275@NIHMLBX02.nih.gov>
2012-03-01  6:20 ` Andrey Repin
2012-03-01  6:33   ` Pat Tressel
2012-03-01  6:24 ` Pat Tressel
2012-03-01 23:05   ` Andrey Repin

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='CABT-+2qo-Ee3fdzdD1_Jh0=6fWRNFu=Fw-he25=_3anZfW+iNA@mail.gmail.com' \
    --to=ptressel@myuw.net \
    --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).