DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=cAaBHOF5loYfIEvevhIDYzhSY4/OK
	tmaT/jGE63RtXbHCOr0QbZNblePGOkRuxbRhiNcZx6VBW+D6O38Qn9AE64hVEsgk
	Vha36d5ZaACiHU7RfLM0D2aizoy/G37/L+fXrOpYioZA6pVZr+WPOPYR36I1slpq
	zjhIcs4dfmtvjE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: exe.stackdump is always empty
Date: Mon, 31 Mar 2014 11:36:29 +0000
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C8A9B8C@MLBXv04.nih.gov>
References: <5F8AAC04F9616747BC4CC0E803D5907D0C8A8F7F@MLBXv04.nih.gov> <20140331101915.GC23383@calimero.vinschen.de>
In-Reply-To: <20140331101915.GC23383@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

> If your process crashes with a thoroughly scrambled stack, there's
> a good chance that Cygwin won't be able to create a stackdump file
> because it crashes again while producing the stackdump.

I don't think it's all that bad -- it was merely an assert()
triggering app's abort...