From: Bill Smith <bsmith@progress.com>
To: cyg Simple <cygsimple@gmail.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Cygwin shell eats Windows exceptions?
Date: Thu, 13 Oct 2016 20:29:00 -0000 [thread overview]
Message-ID: <a1d1e1973fe0405ebfb68bea291027b4@ntmaexbe04.bedford.progress.com> (raw)
In-Reply-To: <895baaa1-50d4-129f-1737-5621f7ed72b9@gmail.com>
> > Sorry for the lack of info. This is a Windows native console application.
> Here's the source code:
> >
> > #include <windows.h>
> >
> 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.
next prev parent reply other threads:[~2016-10-13 19:00 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 [this message]
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
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=a1d1e1973fe0405ebfb68bea291027b4@ntmaexbe04.bedford.progress.com \
--to=bsmith@progress.com \
--cc=cygsimple@gmail.com \
--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).