public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-developers@cygwin.com
Subject: Re: stdin, stdout, stderr when GUI app is launched from command line
Date: Fri, 5 May 2023 06:59:43 +0900	[thread overview]
Message-ID: <20230505065943.01a0d61c6e4d96a6fb5047b6@nifty.ne.jp> (raw)
In-Reply-To: <DB7PR01MB47624877D2D2E627618478468D6D9@DB7PR01MB4762.eurprd01.prod.exchangelabs.com>

On Thu, 4 May 2023 15:10:03 +0000
"Kacvinsky, Tom" wrote:
> I have a Windows GUI app that I have set to run with Windows Application Verifier.
> In particular, I have App verifier set to trigger on invalid handle exceptions (code is
> 0xC0000008).  When the application is run from the Cygwin console, it faults with
> an invalid handle three times.  I can continue past them in windbg (or gdb for that
> matter) and the application launches.  I think it is curious the invalid handle exception
> occurs three times - is it stdin, stdout and stderr that App Verifier thinks are invalid
> handles?  My hunch is yes, they are.
> 
> I did notice that if I run the GUI use run.exe, as in "run guiapp.exe", the application
> launches with no invalid handle exceptions.
> 
> I am using this version of Cygwin 64
> 
> vapkay@US05117NB ~ $ cygcheck -V
> cygcheck (cygwin) 3.1.7
> 
> But it also happens with 3.4.6
> 
> Is this to be expected with a GUI app when run under a Cygwin console?  I've never
> seen it until I ran with App Verifier.  The GUI application is a Qt app.  I check the Qt
> version we're using for use of and I don't see anything in the WinMain what would
> have to do with reading/writing to the standard IO file descriptors.
> 
> Any ideas?

I cannot reproduce your problem with cygwin 3.4.6.
Could you please provide detailed steps?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

      parent reply	other threads:[~2023-05-04 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 15:10 Kacvinsky, Tom
2023-05-04 20:27 ` Jeremy Drake
2023-05-05  1:31   ` Kacvinsky, Tom
2023-05-05  4:46     ` Jeremy Drake
2023-05-04 21:59 ` Takashi Yano [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=20230505065943.01a0d61c6e4d96a6fb5047b6@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin-developers@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).