public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tim Prince <n8tm@aol.com>
To: cygwin@cygwin.com
Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926)
Date: Mon, 03 Oct 2016 12:09:00 -0000	[thread overview]
Message-ID: <b4e5707a-0299-3bee-e4b1-9d22535469c8@aol.com> (raw)
In-Reply-To: <57F1FD3E.80601@maxrnd.com>

On 10/3/2016 2:39 AM, Mark Geisert wrote:
> Tony Kelman wrote:

>
> I see what you've been saying about different insider builds of Windows
> 10 but I don't think anybody here is beating up on these releases.
>
Win10 anniversary with a single cygwin64 installation is sufficiently 
difficult for me.  Unscheduled Microsoft update reboots, inability to 
bootstrap gcc (where it works on win8.1)...

-- 
Tim Prince

--
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

  reply	other threads:[~2016-10-03  9: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
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 [this message]
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=b4e5707a-0299-3bee-e4b1-9d22535469c8@aol.com \
    --to=n8tm@aol.com \
    --cc=cygwin@cygwin.com \
    --cc=tprince@computer.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).