odd behavior(bug?) during run of setup

2018-04-26 Thread L A Walsh
When running setup -- a few time have gotten an error saying that it couldn't create /llvm-objdump.exe.stackdump (setup-x86-64-2.891) I looked, and there is no such file in the root dir, so I traced it with process monitor and first saw it try to CreateFile C:\llvm-objdump.exe.stackdump (Name no

Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash

2018-04-26 Thread Gilles Detillieux
On 2018-04-26 09:03, Jon Turney wrote: On 19/04/2018 22:15, Gilles Detillieux wrote: Has anybody else run into this problem? I've done two installations of Cygwin/X on Windows 10 systems this week, and they both had problems with the XWin Server dying just a few seconds after starting up. I tr

Re: ssh login to cygwin bash?

2018-04-26 Thread Ulli Horlacher
On Thu 2018-03-29 (22:21), Marco Atzeri wrote: > as it seems you have not done so, likely you have another > ssh server than cygwin one running on your pc. Late feedback: this was the case! Thanks for the hint! I have now disabled the foreign sshd, reinstalled cygwin openssh server, opened port 2

Re: umask problem: wrong permissions for new files

2018-04-26 Thread Ulli Horlacher
On Fri 2018-04-20 (07:25), Brian Inglis wrote: > Cygwin supports Windows ACLs as POSIX ACLs, which are also supported by > Linux. Use setfacl to set similar default ACLs (DACLs) on a Linux > directory, rerun your test there, and you should see similar results. (How) can I completly remove ACLs fr

Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash

2018-04-26 Thread Jon Turney
On 19/04/2018 22:15, Gilles Detillieux wrote: Has anybody else run into this problem? I've done two installations of Cygwin/X on Windows 10 systems this week, and they both had problems with the XWin Server dying just a few seconds after starting up. I traced the problem back to xwin-xdg-menu.e

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Houder
On Thu, 26 Apr 2018 13:12:53, Thomas Zimmermann wrote: > > > After the invocation of the handler, the program continues with the code > > > that attempts 'to divide by zero'. > > >=20 > > > As result of that, the handler is invoked again. > > > > This means that the behavior of the test case is in

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Thomas Zimmermann
I just saw that the result after returning from a synchronous signal is undefined. So any behavior seems be OK. I'd still encourage to unify the behavior of 32-bit and 64-bit code. (See my other mail.) Best regards Thomas Am 26.04.2018 um 13:01 schrieb Houder: > On Thu, 26 Apr 2018 12:52:54, Thom

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Thomas Zimmermann
Hi Am 26.04.2018 um 13:01 schrieb Houder: > > After the invocation of the handler, the program continues with the code > that attempts 'to divide by zero'. > > As result of that, the handler is invoked again. This means that the behavior of the test case is incorrect when running in 32-bit mode

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Houder
On Thu, 26 Apr 2018 12:52:54, Thomas Zimmermann wrote: > Hi > > Am 26.04.2018 um 12:45 schrieb Houder: > >> The expected behavior is that an installed signal handler runs exactly > >> once for a signal and the OS terminates the program if the handler > >> returns. This works on 32-bit Cygwin. Fro

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Houder
On 2018-04-26 12:45, Houder wrote: On Thu, 26 Apr 2018 09:57:59, Thomas Zimmermann wrote: Hello mailing list, I noticed that synchronous signals (e.g., SIGSEGV, SIGFPE) appear to be broken on 64-bit Cygwin systems. I could not find additional information on the mailing list. If this is not a

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Thomas Zimmermann
Hi Am 26.04.2018 um 12:45 schrieb Houder: >> The expected behavior is that an installed signal handler runs exactly >> once for a signal and the OS terminates the program if the handler >> returns. This works on 32-bit Cygwin. From my observation, Cygwin 64 >> differs in the follow ways: > > .. u

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Houder
On Thu, 26 Apr 2018 09:57:59, Thomas Zimmermann wrote: > Hello mailing list, > > I noticed that synchronous signals (e.g., SIGSEGV, SIGFPE) appear to be > broken on 64-bit Cygwin systems. I could not find additional information > on the mailing list. If this is not already a known problem, you'll

Re: Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Marco Atzeri
On 4/26/2018 9:57 AM, Thomas Zimmermann wrote: Hello mailing list, I noticed that synchronous signals (e.g., SIGSEGV, SIGFPE) appear to be broken on 64-bit Cygwin systems. I could not find additional information on the mailing list. If this is not already a known problem, you'll find some analys

Bug: Synchronous signals broken on Cygwin 64

2018-04-26 Thread Thomas Zimmermann
Hello mailing list, I noticed that synchronous signals (e.g., SIGSEGV, SIGFPE) appear to be broken on 64-bit Cygwin systems. I could not find additional information on the mailing list. If this is not already a known problem, you'll find some analysis below. I use Cygwin DLL 2.10 with all packag