From: Peter Rosin <peda@lysator.liu.se>
To: cygwin@cygwin.com
Subject: Re: Cygwin shell eats Windows exceptions?
Date: Fri, 14 Oct 2016 10:52:00 -0000 [thread overview]
Message-ID: <b2fc486d-274f-ce32-6209-aab0f641d9ad@lysator.liu.se> (raw)
In-Reply-To: <2e88aba8-6214-4bef-b248-cc7809afea4a@lysator.liu.se>
On 2016-10-14 00:52, Peter Rosin wrote:
> On 2016-10-13 16:35, Bill Smith wrote:
>> Hi,
>> I'm trying to run my Windows C++ application which has a call to DebugBreak() to bring up the popup asking if you want to debug this application or terminate it. If I run the program within Cygwin, the program just exits.
>>
>> If I run the application from a Windows command prompt, I get the Windows popup that I'm expecting. It seems that the Cygwin shell is eating exceptions (sigsegv or similar signals?). Is there a way for me to disable this behavior?
>
> I believe you want the reverse of this program:
>
> https://github.com/msysgit/msys/blob/master/winsup/utils/error-mode.c
>
> error-mode can make the popups go away (getting cygwin behavior
> on msys), but it should be possible to modify it to make the
> popup appear instead. I think...
feeep, should have read my old code before I posted. The program
should fit the bill. My memory is apparently bad but short.
Sorry for the noise.
Cheers,
Peter
--
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
prev parent reply other threads:[~2016-10-13 22:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 15:24 Bill Smith
2016-10-13 16:57 ` Brian Inglis
2016-10-13 18:19 ` Bill Smith
2016-10-13 19:00 ` cyg Simple
2016-10-13 20:29 ` Bill Smith
2016-10-13 22:52 ` Larry Hall (Cygwin)
2016-10-14 12:34 ` Herbert Stocker
2016-10-13 22:55 ` Brian Inglis
2016-10-14 17:46 ` Bill Smith
2016-10-18 18:22 ` Wilfried
2016-10-18 19:46 ` cyg Simple
2016-10-13 22:55 ` Peter Rosin
2016-10-14 10:52 ` Peter Rosin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2fc486d-274f-ce32-6209-aab0f641d9ad@lysator.liu.se \
--to=peda@lysator.liu.se \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).