| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
It seems the call that caused issues with the gcc wrapper before
was needed for the ghci wrapper in order for the child process
to be the one handling console events.
This code slightly refactors the wrappers to make sure only ghci
calls FreeConsole and nothing else.
Test Plan: ./validate , open ghci.exe press ctrl+c
Reviewers: RyanGlScott, austin, hvr, bgamari
Reviewed By: bgamari
Subscribers: rwbarton, thomie, erikd
GHC Trac Issues: #14150
Differential Revision: https://phabricator.haskell.org/D4028
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: Escape `\` in paths on Windows in `cwapper.c` when we re-output the paths.
Test Plan: ./validate
Reviewers: austin, bgamari
Reviewed By: bgamari
Subscribers: rwbarton, thomie
GHC Trac Issues: #13666
Differential Revision: https://phabricator.haskell.org/D3628
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In Windows 10 Insiders build 15019+ which will probably be released
mainstream somewhere this year Microsoft seems to have started being
stricter with API calls.
The call to `FreeConsole` just after `CreateProcess` is making Windows
treat the process
as an interactive process. In which case it tries to use the `Desktop
session` but fails resulting
in the cryptic error reported.
I don't understand why the call to `FreeConsole` was there and it
doesn't seem to be needed,
so removed.
This fixes #13411
Test Plan: ./validate, alternative just do anything with ghc which
requires compilation.
Reviewers: austin, bgamari, simonmar
Reviewed By: bgamari
Subscribers: rwbarton, thomie, #ghc_windows_task_force
Differential Revision: https://phabricator.haskell.org/D3319
|
| |
|
|
| |
Caught by -Werror
|
| | |
|
| | |
|
| |
|
