From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926)
Date: Mon, 03 Oct 2016 06:40:00 -0000 [thread overview]
Message-ID: <87intaeyco.fsf@Rainer.invalid> (raw)
In-Reply-To: <CY1PR0201MB0796D83501EC1E9C7AAA09A2A7C20@CY1PR0201MB0796.namprd02.prod.outlook.com> (Tony Kelman's message of "Mon, 3 Oct 2016 01:28:30 +0000")
Tony Kelman writes:
>> Something occupies the heap area for Cygwin, based on the low address.
>> What does /proc/self/maps tell you?
>
> $ cat /proc/self/maps
[…]
>
> Hopefully you know what you're looking at there. Anything meaningful in that?
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. Have you tried to play around with the virus scanner
settings?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
--
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-10-03 6:33 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 [this message]
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=87intaeyco.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).