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=mRdCqAc1/zkjNRUHfn1BsKs//Hwag
	RX2YIQVUF5lbmnjR6zMRcILzTfHxztZ9gMXBU8hNAMgSLs1SVLgwN9n1Or6CK9Au
	7SKvyCis3EncLsivWpAToElm22TN+ZZgicbOge4addwq69YFqQMc3R7DAb9+UCeS
	I4OLNa4yWDRjGE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Bill Smith <bsmith@progress.com>
To: "Brian.Inglis@SystematicSw.ab.ca" <Brian.Inglis@SystematicSw.ab.ca>,
        "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Cygwin shell eats Windows exceptions?
Date: Fri, 14 Oct 2016 12:34:37 +0000
Message-ID: <c50c7abd949841bba67dcabc0cf32a37@ntmaexbe04.bedford.progress.com>
References: <d0503299c2ae40aaa34023285486deb0@ntmaexbe04.bedford.progress.com> <384029be-4060-cb6b-d1e5-ea88cccb5999@Shaw.ca> <fd695806340147cbba3d42c761bfc063@ntmaexbe04.bedford.progress.com> <2ff7ceba-3e08-d514-372b-41e5696c37a5@SystematicSw.ab.ca>
In-Reply-To: <2ff7ceba-3e08-d514-372b-41e5696c37a5@SystematicSw.ab.ca>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit


Thanks for all of the responses from everyone. 

> If you need to do interactive debugging, run it under cmd or with cygstart.

[Bill Smith] it seems that an ok workaround is for me to use cygstart to start a command prompt within a Cygwin shell and then in the command prompt, run the program which calls DebugBreak and cause the popup to appear.  The reason for needing to run within Cygwin is because we have a complex shell script that sets the user environment to run the application.