public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Tue, 27 Sep 2016 10:58:00 -0000	[thread overview]
Message-ID: <DM2PR0201MB079975A16D4E98A8B20250EEA7CC0@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <57E700EA.2040802@maxrnd.com>

> You're absolutely sure your rebasing operations are being done without
> any Cygwin processes running, even background cygserver, sshd, etc?

Pretty sure. I don't have any cygwin processes set up to start at login,
and I was rebooting several times here.

> Could you paste a complete sample of the error message so we can
> determine where in the Cygwin code it's coming from?

I'll have to see if I can reproduce in a VM, and hope they release a
stable build soon that doesn't expire on me or exhibit this problem.
Is anyone else testing insider builds?

-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

  reply	other threads:[~2016-09-27  5:35 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 [this message]
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=DM2PR0201MB079975A16D4E98A8B20250EEA7CC0@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).