From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Dmitry Karasik <dmitry@karasik.eu.org>
Subject: Re: coredumps and/or CPU eating zombies after dlopen/fork
Date: Sat, 26 Nov 2022 10:43:19 +0900 [thread overview]
Message-ID: <20221126104319.ee7b013e6f706c11246e1668@nifty.ne.jp> (raw)
In-Reply-To: <20221125132215.GA24139@nataraj.eu.org>
On Fri, 25 Nov 2022 14:22:15 +0100
Dmitry Karasik wrote:
> Otherwise, to reproduce, download and unpack http://karasik.eu.org/misc/cygwin/cygwin-gtk-dlopen-fork-bug.tar
> and run ./try there.
Why do you include windows.h in test.c?
I encountered following error.
/usr/include/w32api/processthreadsapi.h:165:11: Error: expected identifier or ‘(’ before numeric constant
165 | ULONG ControlMask;
| ^~~~~~~~~~~
Removing #include <windows.h> or adding
#undef ControlMask
is necessary to compile test.c without errors.
With that modification, your problem can not be reproducible
in my environment. The result is as follows.
not expecting a bug
child existed with 0
expecting a bug
child existed with 0
no bug detected
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2022-11-26 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 13:22 Dmitry Karasik
2022-11-25 15:38 ` Thomas Wolff
2022-11-26 1:43 ` Takashi Yano [this message]
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=20221126104319.ee7b013e6f706c11246e1668@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=dmitry@karasik.eu.org \
/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).