Using arcanist with a cygwin PHP installation (and console) on Windows results in a segfault in the current master and stable branches.
029e5a7c2900b7a4f516ac7e7c1415b0c6500ed1 works fine,
7e677c27eccfeaaf15921e8edbbc8eb5f1951351 segfaults instantly, when simply calling `arc`.
From a babun console (babun installs/prepares a cygwin+zsh shell environment):
{ arcanist } HEAD » arc /cygdrive/d/projects/arcanist
[1] 3556 segmentation fault (core dumped) arc
```
{ arcanist } HEAD » cat php.exe.stackdump /cygdrive/d/projects/arcanist
Exception: STATUS_ACCESS_VIOLATION at eip=6E026247
eax=FFE45000 ebx=002879F0 ecx=00287AD0 edx=FFE44FFF esi=FFE45000 edi=FFE44FFF
ebp=00000000 esp=00287910 program=C:\Users\Klass\.babun\cygwin\bin\php.exe, pid 3556, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
End of stack trace
```
The non existant stacktrace is not really helpful.
To me, it seems that the commit 7e677c27eccfeaaf15921e8edbbc8eb5f1951351 does not really introduce usage of new/other php features or extensions.
Amongst other things, a call to `phutil_console_format` is introduced, which is used earlier in the same file arcanist.php as well.
My colleague said he undid one line change and was able to verify it being the causing issue.
I know a PHP segfault should be reported to PHP or in this case probably cygwin package creator, but I won’t analyze this further nor look for where I would report such a thing.
Maybe this information will help you support other cases or maybe you want to work around this, or maybe someone even wants to report to cygwin php.