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 hangs up if several keys are typed during outputting a lot of texts.

Hi Corinna,

I'm sorry for late reply.

On Tue, 7 Apr 2015 11:11:13 +0200
Corinna Vinschen <> wrote:

> I think we should move opost processing back to the master side.  Would
> it be much of a problem to restructure your patch to do that, without
> re-introducing the old problems your patch fixed?

I am considering of this issue for several days.
However, it is still with dificulty.

For my better understanding, may I ask a question?

At where does cygwin set the standard output handle
for native windows programs to fhandler_pty_slave::

Since I found SetStdHandle() calls in,
I tried to disable all of them. However, the output
of icacls still appears in mintty screen.

I wonder where the standard output handle is set.

By the way,

> Hmm, even after cbb9849fa76f1dbe6c66d91b68d9a10f46f1ba69,
> it does not work in my environment.

this problem has been gone after the following change.

commit 72f7cd89f230342107ec9e22fea38bf75bcb698d
Author: Jon TURNEY <>
Date:   Sat Apr 4 23:31:03 2015 +0100

    Compile with -fno-omit-frame-pointer on x86

    Selectively using -fomit-frame-pointer when -O is used doesn't make sense
    anymore, apparently since gcc 4.6, -O implies -fomit-frame-pointer. must be compiled with -fno-omit-frame-pointer on x86, as it uses
    RtlCaptureContext, which requires a frame pointer.

        * : Remove setting -fomit-frame-pointer for compiling
        various files, it is already the default.  Set
        -fno-omit-frame-pointer for on x86.

    Signed-off-by: Jon TURNEY <>

Takashi Yano <>

Problem reports:
Unsubscribe info:

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