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=mRdCqAc1/zkjNRUHfn1BsKs//Hwag RX2YIQVUF5lbmnjR6zMRcILzTfHxztZ9gMXBU8hNAMgSLs1SVLgwN9n1Or6CK9Au 7SKvyCis3EncLsivWpAToElm22TN+ZZgicbOge4addwq69YFqQMc3R7DAb9+UCeS I4OLNa4yWDRjGE= 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=ej/t3wBXiGRVamlBD7SrG35Cy+s=; b=JCz mZ9wat7PgShifLNTeSAj39g/EQzLlhmsqOEk2HhpXFm0gt2tXSLDOp9xHTnRS5Zo aoJQ/hf9TNSvaU4R+mDkO9PrloPwMCUIh/G88FFWrKThKZ9B1ffR5ErLeYXbv9rm /1p4gS2Feqoe/K8mhIJoDvE4XMioOlv1KupPVyZE= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.7 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=H*i:sk:2ff7ceb, H*MI:sk:2ff7ceb, H*f:sk:2ff7ceb X-HELO: mail1.bemta12.messagelabs.com X-Env-Sender: bsmith AT progress DOT com X-Msg-Ref: server-11.tower-108.messagelabs.com!1476448477!75367735!1 X-StarScan-Received: X-StarScan-Version: 8.84; banners=-,-,- X-VirusChecked: Checked From: Bill Smith To: "Brian DOT Inglis AT SystematicSw DOT ab DOT ca" , "cygwin AT cygwin DOT com" Subject: RE: Cygwin shell eats Windows exceptions? Date: Fri, 14 Oct 2016 12:34:37 +0000 Message-ID: References: <384029be-4060-cb6b-d1e5-ea88cccb5999 AT Shaw DOT ca> <2ff7ceba-3e08-d514-372b-41e5696c37a5 AT SystematicSw DOT ab DOT ca> In-Reply-To: <2ff7ceba-3e08-d514-372b-41e5696c37a5@SystematicSw.ab.ca> x-ms-exchange-transport-fromentityheader: Hosted 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 u9ECYs89000361 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.