[ANNOUNCEMENT] Updated: setup (2.919)

2022-07-02 Thread Jon Turney
A new version of Setup (2.919) has been uploaded to: https://cygwin.com/setup-x86_64.exe (64 bit version) https://cygwin.com/setup-x86.exe (32 bit version) Changes compared to 2.918: - Fix '-P package-with-only-a-test-version' - De-clutter the mirror selection listbox Where a mirror

[ANNOUNCEMENT] New: pass 1.7.4-1

2022-07-02 Thread Christian Franke
The latest upstream release of pass (password-store) is now available in the Cygwin distribution. https://www.passwordstore.org/ 'pass' is a command line tool which stores, retrieves and generates passwords securely using gpg. Optionally password changes could be tracked and synchronized with

Unexpected zero return code from `throw std::runtime_error`

2022-07-02 Thread Adam Dinwoodie
I'm currently experimenting with compiling rdfind for Cygwin, and one of the testcases is failing because std::runtime_error is expected to result in the compiled program exiting with a non-zero return code, but on Cygwin, it just seems to cause the program to terminate with a zero return code. I'

Re: Unexpected zero return code from `throw std::runtime_error`

2022-07-02 Thread Joost Kraaijeveld
Hi, The exception is not handled by the program. In that case "[[noreturn]] void std::terminate()" is called by the C++-runtime. std::terminate calls the currently installed std::terminate_handler. The default std::terminate_handler calls std::abort. After calling std::abort an implementation defi

[ANNOUNCEMENT] New: etckeeper 1.18.17-1

2022-07-02 Thread Christian Franke
The latest upstream release of etckeeper is now available in the Cygwin distribution. https://etckeeper.branchable.com/ Etckeeper is a tool to let /etc be stored in git or mercurial. It hooks into Cygwin Setup to automatically commit changes made to /etc during package upgrades. It tracks fil

Re: Unexpected zero return code from `throw std::runtime_error`

2022-07-02 Thread Adam Dinwoodie
On Sat, Jul 02, 2022 at 04:14:51PM +0200, Joost Kraaijeveld wrote: > Hi, > > The exception is not handled by the program. In that case "[[noreturn]] > void std::terminate()" is called by the C++-runtime. std::terminate > calls the currently installed std::terminate_handler. The default > std::term

setup 2.920 release candidate - please test

2022-07-02 Thread Jon Turney
A new setup release candidate is available at: https://cygwin.com/setup/setup-2.920.x86_64.exe (64 bit version) https://cygwin.com/setup/setup-2.920.x86.exe(32 bit version) Please test, and report any problems here. This is not the place for setup feature requests. Changes compared to

Re: Weird issue with file permissions

2022-07-02 Thread Ken Brown
On 7/1/2022 11:23 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: That way I'm sure I won't have any surprises with permissions when working in /cygdrive/g/cygwin. Do you want to try that and see if it makes a difference? I have no problems with /cygdrive/g/cygwin -- my socket file gets create

RE: [EXTERNAL] Unexpected zero return code from `throw std::runtime_error`

2022-07-02 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
Looks like your program does not throw an exception on Cygwin (unlike it does on Debian), so it terminates normally, and the exit code 0 is not unexpected. Debian's version calls abort() and that sends a signal and terminates with a code 128+signal#, and SIGABRT=6, so 134 is the expected result

RE: Weird issue with file permissions

2022-07-02 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
I forgot to mention that my "umask" is the standard 022... The man page says that for directories with the ACLs, it is ignored. So in my code bind() wouldn't have created the socket with 0777, and that's fine! Which is why I call fchmod() to fix the permissions up, and THAT does not work. BTW,

[ANNOUNCEMENT] Updated: cpuid 20220620

2022-07-02 Thread Cygwin cpuid Maintainer
The following package has been upgraded in the Cygwin distribution: * cpuid 20220620 The program displays detailed information about the CPU(s) gathered from the CPUID instruction, and also determines the exact model of CPU(s). Whereas /proc/cpuinfo is like an abstract of the features im

fish-3.5.0-1: /etc/fish/conf.d/cygwin.fish only readable by owner

2022-07-02 Thread Christian Franke
The permission of cygwin.fish looks somewhat random (depends on umask during build?): $ tar tvf fish-3.4.1-1.tar.xz etc/defaults/etc/fish/conf.d/cygwin.fish -rw-r-xr-- ... 1101 2022-04-07 20:34 etc/defaults/etc/fish/conf.d/cygwin.fish $ tar tvf fish-3.5.0-1.tar.xz etc/defaults/etc/fish/conf.d

Re: [ANNOUNCEMENT] New: pass 1.7.4-1

2022-07-02 Thread Andrey Repin
Greetings, Christian Franke! > The latest upstream release of pass (password-store) is now available in the > Cygwin distribution. Wow THANK you! Just in the time I've installed the version from Git :D > https://www.passwordstore.org/ > 'pass' is a command line tool which stores, retrieves and

Re: Weird issue with file permissions

2022-07-02 Thread Ken Brown
On 7/2/2022 12:16 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: I forgot to mention that my "umask" is the standard 022... The man page says that for directories with the ACLs, it is ignored. So in my code bind() wouldn't have created the socket with 0777, and that's fine! Which is why I cal

RE: [EXTERNAL] Re: Weird issue with file permissions

2022-07-02 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
> what your test program was actually doing. But you seem to be assuming that > calling fchmod on a socket descriptor should affect the permissions on the > socket file (assuming the socket is bound). Is that documented anywhere? > POSIX > says that the behavior of fchmod on a socket descriptor

Re: Unexpected zero return code from `throw std::runtime_error`

2022-07-02 Thread Csaba Raduly
On Sat, 2 Jul 2022 at 15:22, Adam Dinwoodie wrote: > > I'm currently experimenting with compiling rdfind for Cygwin, and one of > the testcases is failing because std::runtime_error is expected to > result in the compiled program exiting with a non-zero return code, > but on Cygwin, it just seems

Re: Unexpected zero return code from `throw std::runtime_error`

2022-07-02 Thread Adam Dinwoodie
On Sat, Jul 02, 2022 at 10:19:44PM +0200, Csaba Raduly wrote: > On Sat, 2 Jul 2022 at 15:22, Adam Dinwoodie wrote: > > > > I'm currently experimenting with compiling rdfind for Cygwin, and one of > > the testcases is failing because std::runtime_error is expected to > > result in the compiled prog

Re: [EXTERNAL] Re: Weird issue with file permissions

2022-07-02 Thread Ken Brown
On 7/2/2022 3:37 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: what your test program was actually doing. But you seem to be assuming that calling fchmod on a socket descriptor should affect the permissions on the socket file (assuming the socket is bound). Is that documented anywhere? POSIX

Re: [EXTERNAL] Re: Weird issue with file permissions

2022-07-02 Thread Andrey Repin
Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]! >> what your test program was actually doing. But you seem to be assuming that >> calling fchmod on a socket descriptor should affect the permissions on the >> socket file (assuming the socket is bound). Is that documented anywhere? >> POSIX >>

Re: Unexpected zero return code from `throw std::runtime_error`

2022-07-02 Thread Csaba Raduly
On Sat, 2 Jul 2022 at 23:34, Adam Dinwoodie wrote: > > That's definitely closer to the behaviour I'd expect! I don't think it > should be dumping a core, though, at least based on the behaviour I see > on Debian. It should be dumping core, because std:terminate() calls abort(), as Joost has expl

Re: VS Code is missing a few characters when running launch task in Git Bash

2022-07-02 Thread Takashi Yano
On Sat, 2 Jul 2022 08:34:06 +0900 Takashi Yano wrote: > Thanks. I could reproduce the issue. I will submit a patch > for this issue shortly. Does the patch I pushd to cygwin-3_3-branch solve the VS Code issue? -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ:

RE: Weird issue with file permissions

2022-07-02 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
> That's not what I'm seeing when I run your test program on Linux: > > $ ./sun > fstat mode = 140666 > stat mode = 140777 True, but it creates the socket file with exactly how umask(0) told it to, and stat() shows that. So yeah, I should retract that it works on Linux with fchmod() -- on Linux