From: Tony Kelman <tony@kelman.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926)
Date: Mon, 03 Oct 2016 09:10:00 -0000 [thread overview]
Message-ID: <DM2PR0201MB0799524392929535EA60054EA7C20@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <87intaeyco.fsf@Rainer.invalid>
> No, that looks like I'd expect it to. You need to look at the process
> map when you have fork problems, since the problem seems to be
> intermittent.
How so? Something like
for i in `seq 1000`; do
cat /proc/self/maps > procselfmaps_`date +%s.%N`.txt;
done &
before running the problematic command? It does take a variable amount
of time to trigger, and sometimes exhibits as a complete freeze instead
of an error. What should I be looking for here?
> Have you tried to play around with the virus scanner settings?
I already have a Windows Defender exclusion for my Cygwin installs.
Turning off real-time protection temporarily didn't help.
> One sure-fire way to make sure your 32-bit E: installation is not causing havoc
> with your 64-bit C: installation is to temporarily rename E:\cygwin32 to
> E:\somethingelse and retry your build. This should not be necessary but I don't
> know what else to suggest.
Good idea. Tried it, didn't help.
--
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
prev parent reply other threads:[~2016-10-03 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:51 Tony Kelman
2016-09-24 13:49 ` Tony Kelman
2016-09-25 8:20 ` Mark Geisert
2016-09-27 10:58 ` Tony Kelman
2016-10-02 6:58 ` Tony Kelman
2016-10-02 9:38 ` Mark Geisert
2016-10-02 9:56 ` Tony Kelman
2016-10-02 10:00 ` Tony Kelman
2016-10-03 6:57 ` Mark Geisert
2016-10-03 12:09 ` Tim Prince
2016-10-02 15:09 ` Achim Gratz
2016-10-03 3:58 ` Tony Kelman
2016-10-03 6:40 ` Achim Gratz
2016-10-03 9:10 ` Tony Kelman [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=DM2PR0201MB0799524392929535EA60054EA7C20@DM2PR0201MB0799.namprd02.prod.outlook.com \
--to=tony@kelman.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).