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: Sat, 24 Sep 2016 13:49:00 -0000 [thread overview]
Message-ID: <DM2PR0201MB07990C9272767BC3A62529C2A7CB0@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <DM2PR0201MB079977535C2477CA6B0EF745A7F30@DM2PR0201MB0799.namprd02.prod.outlook.com>
> I've tried manually rebasing, setting rebase-trigger, rerunning latest
> setup, rebooting, etc. During big parallel makes none of the above helped
> with getting rid of intermittent heap mismatch errors during fork after I
> upgraded to Windows 10 Insider build 14926. I had been on the Insider fast
> ring for a few months
Anybody? Just checked 14931 and it has the same problem.
I'll be switching back the slow ring as soon as it lets me, but
I'm about to start getting "build will expire" popups.
-Tony
--
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:[~2016-09-24 10:10 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 [this message]
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
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=DM2PR0201MB07990C9272767BC3A62529C2A7CB0@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).