X-Recipient: archive-cygwin AT delorie DOT com
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=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=RCVqUX8dGbUFrj3+1fTKHc4Ab08=; b=T0F
	oz6PXyNBLtzDu2pGBkATqvQ/LIUMNIYTWMaiAwZGySoBB6asV2A+ndWn251AjKQC
	WhWbUCSh8DdT+NKECFR2vLKMSSERBFyxpByqJ0vSkVjH5yzHL7+GO1tGw/WNAweU
	XhCr7sX+w6K6ugmwHcpaLZkwyKCWTQjVuCYfZ4k8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_50,MIME_BASE64_BLANKS,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO: nihxway3out.hub.nih.gov
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkcFAOJSOVOcKEew/2dsb2JhbABZgwaBEoMKwA0ZgQIWdIIlAQEBAwESERFKCwIBCA0NAgYgAgICHRMVEAEBBBsah08Io3SKIqIVF4EpjSU4gm81gRQEjniQS4tAgzCCKw
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT 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 AT MLBXv04 DOT nih DOT gov> <20140331101915 DOT GC23383 AT calimero DOT vinschen DOT de>
In-Reply-To: <20140331101915.GC23383@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id s2VBavYH024769

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