This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: Cygwin shell eats Windows exceptions?

From: Bill Smith <bsmith at progress dot com>
To: "Brian dot Inglis at SystematicSw dot ab dot ca" <Brian dot Inglis at SystematicSw dot ab dot ca>, "cygwin at cygwin dot com" <cygwin at cygwin dot com>
Date: Fri, 14 Oct 2016 12:34:37 +0000
Subject: RE: Cygwin shell eats Windows exceptions?
Authentication-results: sourceware.org; auth=none
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>

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.

Follow-Ups:
- Re: Cygwin shell eats Windows exceptions?
  - From: Wilfried

References:
- Cygwin shell eats Windows exceptions?
  - From: Bill Smith
- Re: Cygwin shell eats Windows exceptions?
  - From: Brian Inglis
- RE: Cygwin shell eats Windows exceptions?
  - From: Bill Smith
- Re: Cygwin shell eats Windows exceptions?
  - From: Brian Inglis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]