public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin" <cygwin@cygwin.com>
Subject: Re: killpg(pgid, 0) fails if the process is in the middle of spawnve()
Date: Thu, 19 May 2022 13:51:07 +0900	[thread overview]
Message-ID: <0C6FFD9B-F723-4F8C-BDA9-A67A64EB71E0@kba.biglobe.ne.jp> (raw)
In-Reply-To: <YoUIi9n3xoUogD1z@calimero.vinschen.de>


> 2022/05/18 23:54, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> 
> For a start, can you try the above patch? 

Thanks for a quick response. The patch seems to solve the problem.
Of course there is a possibility that it happens with very low probability,
but I haven't get the problem by running 'cmd | less' many times, say
fifty times or so.

I didn't notice any bad side effects, and I guess the probability is
very low if it ever happens (so not easy to detect it).
# I tried running 'ls | less' several times while running 
#   while true; do ps; done
# in another terminal, but didn't get duplicated processes.


PS:
I'm new to building cygwin1.dll by myself, and have a few questions:
(1) After make, I've manually copied new-cygwin1.dll to /bin/cygwin1.dll.
I didn't copy/install any other files. Is this OK?
(2) What are cygwin0.dll and cygwin1.dbg? The latter is a new cygwin1.dll
with debug info?
(3) Is there a simple way to build only new-cygwin1.dll (and anything
required by it), without building (or trying to build) unnecessary
things (especially documents)?

--
Jun

  reply	other threads:[~2022-05-19  4:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 11:19 Jun T
2022-05-18 14:54 ` Corinna Vinschen
2022-05-19  4:51   ` Jun T [this message]
2022-05-19  7:46     ` Corinna Vinschen

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=0C6FFD9B-F723-4F8C-BDA9-A67A64EB71E0@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --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).