From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: fork errors
Date: Tue, 03 Apr 2018 20:40:00 -0000 [thread overview]
Message-ID: <1f65087a-e62e-ddc1-8831-7f5d9f0ab4cd@gmail.com> (raw)
In-Reply-To: <CAEUYfyPOX_t4VYGMbbKhT=rGVkQkUm29fdr1ui3KV7Nu943+Yg@mail.gmail.com>
On 03/04/2018 17:20, Simon Matthews wrote:
> I have been seeing a large number of error messages like this:
> 2 [main] bash 8652 fork: child -1 - forked process 7532 died
> unexpectedly, retry 0, exit code 0xC0000005, errno 11
> 2 [main] bash 8652 fork: child -1 - forked process 7532 died
> unexpectedly, retry 0, exit code 0xC0000005, errno 11
>
> I followed the instruction to run "rebaseall" and this appears to have
> worked properly.
>
> I suspect that the cause is that I am running a daemon that I compiled
> myself on a different instance of cygwin and then copied across. This
> daemon is not in the normal /usr tree.
>
> Should I rebase the binaries associated with this daemon and, if so,
> how do I do this?
>
> Simon
>
Simon,
copied across what ?
Rebase is only for shared libraries; how is your demon implemented ?
Regards
Marco
--
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:[~2018-04-03 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 15:20 Simon Matthews
2018-04-03 20:40 ` Marco Atzeri [this message]
2018-04-03 21:12 ` Jürgen Wagner
2018-04-04 3:06 ` Simon Matthews
2018-04-04 5:28 ` Simon Matthews
2018-04-03 23:09 ` Tatsuro MATSUOKA
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 18:51 Fork errors Dale Lobb
2023-09-06 21:00 ` Jose Isaias Cabrera
2023-09-06 21:03 ` Jose Isaias Cabrera
2023-09-06 23:32 ` Mark Geisert
2023-09-07 15:20 ` Bill Stewart
2023-09-08 5:02 ` Mark Geisert
2000-04-07 5:28 fork errors Earnie Boyd
2000-04-06 14:28 Ron Huber
2000-04-06 13:32 Ron Huber
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=1f65087a-e62e-ddc1-8831-7f5d9f0ab4cd@gmail.com \
--to=marco.atzeri@gmail.com \
--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).