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=ICJxTBEV9+96tOkp2U2W993p2Glrh 7DdrV2l2bpkzwcELYsxsNUyYaxEM9WXubkQhBpG3DkSyY8ZLsgluvM+nqvduxOr6 kltpevnx61t22/2RwmxAJYmd+SqUDAdtmHodrM/znCD26+tkIKiuSVEurafDL3kK zRyg7887GxJIQM= 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=7PRV1R4gyKJY25QzYAa8VhWaAyk=; b=NYi iI4Ms5MO9h4YnKUZPDxlnkfw2jZtv4NYcQ6Uex6S1w+gSmcmgyG0NwLp4W0kCBzb nrBARQEU97oue5Eg0xTOhtoTQJRFBViDyO4V29qukkWakYMMYZ8D4Gv+uw8+US0T 04iAWmfqY9pq+Ceui1hjKtLlfgoeq2kU9QfUWC6o= 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*MI:sk:895baaa, H*i:sk:895baaa, H*f:sk:895baaa X-HELO: mail1.bemta8.messagelabs.com X-Env-Sender: bsmith AT progress DOT com X-Msg-Ref: server-4.tower-119.messagelabs.com!1476385219!71077068!1 X-StarScan-Received: X-StarScan-Version: 8.84; banners=-,-,- X-VirusChecked: Checked From: Bill Smith To: cyg Simple , "cygwin AT cygwin DOT com" Subject: RE: Cygwin shell eats Windows exceptions? Date: Thu, 13 Oct 2016 19:00:19 +0000 Message-ID: References: <384029be-4060-cb6b-d1e5-ea88cccb5999 AT Shaw DOT ca> <895baaa1-50d4-129f-1737-5621f7ed72b9 AT gmail DOT com> In-Reply-To: <895baaa1-50d4-129f-1737-5621f7ed72b9@gmail.com> 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 u9DJ0cTS005892 > > Sorry for the lack of info. This is a Windows native console application. > Here's the source code: > > > > #include > > > A "console application" doesn't require windows.h but this isn't the issue. [Bill Smith] Not sure that I understand. Is your point that because it includes Windows.h, it's a GUI application? I was just following the docs here: https://msdn.microsoft.com/en-us/library/windows/desktop/ms679297%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396 > The Windows cmd console and the Cygwin console behave differently to the > exception. Not a bug, just not what you wanted. [Bill Smith] Ok, understood. > What if you 'cmd.exe /c foo.exe' from the Cygwin shell? Will the Dialogue > popup box occur? If so you can provide a sh script foo to execute the > foo.exe file. [Bill Smith] Thanks for the suggestion but that doesn't work. If I try to open a command prompt from a Cygwin shell (just type in "cmd"), I get the same behavior where I don't see the popup. If I run "cygstart cmd.exe", then running the program from the command prompt will generate the popup.