X-Recipient: archive-cygwin@delorie.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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=wILU74NClBWgklcsK5x10IDNKOMQlo6ojgVClQ1FI6AYdn7RFNe9O
	iCbi2XuXo+WSe6oVAgLs9Vtdz3BXyBzI2mCRN0HAHqII1al6ZKQMK3ZuxVVxQ9NX
	F8sO2Vchod/Jm7KSAXEA8lV87PngU9K3TAa17OurLaOiubGBkXgg04=
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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	 bh=KvluFOdcd7W7cC3khta1qXCW3Ns=; b=u4BDkxhpZCKvnWI/EdJ0c9+cFSL2
	o6DphGqSX1Nya6zOydgzD9c9u8aoAQe5etFTbhVIuGOiXPMlBIMNno6pH74w6+j5
	eLPGgIXufcBO5Q1rwBp2VHwF37sLqyILES11cl5ieZGF+fon9LVAZI11QTFUO7aV
	KkjuBly/YRjKWI0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=BAYES_20,FREEMAIL_FROM,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=hth, utilities, H*r:Unknown
X-HELO: blaine.gmane.org
To: cygwin@cygwin.com
From: Wilfried <wh_ng@gmx.de>
Subject: Re: Cygwin shell eats Windows exceptions?
Date: Tue, 18 Oct 2016 20:03:13 +0200
Lines: 20
Message-ID: <9moc0c5dvlubrrbrri118rg648j4lbh4ha@4ax.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> <c50c7abd949841bba67dcabc0cf32a37@ntmaexbe04.bedford.progress.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: ForteAgent/7.10.32.1212
X-IsSubscribed: yes

Bill Smith wrote:

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

OK, if that is the only reason for using cygwin, I can recommend another
way to run a complex shell script in windows.
There is a native windows port of the bash shell in
http://win-bash.sourceforge.net/

If you need more unix command line utilities, look in
https://sourceforge.net/projects/gnuwin32/

HTH, Wilfried
-- 
Wilfried Hennings


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple