Hello!
Did anyone test whether Cygwin 3.6 will still work on Windows 8? I
know, Win8 is unsupported, but apparently it is still needed
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
On Fri, Mar 7, 2025 at 9:01 AM Takashi Yano via Cygwin
wrote:
>
> On Fri, 7 Mar 2025 16:29:51 +0900
> Takashi Yano wrote:
> > On Wed, 5 Mar 2025 11:23:26 +0100
> > Christian Franke wrote:
> > > Takashi Yano via Cygwin wrote:
> > > > On Mon, 24 Feb 20
On Fri, Mar 7, 2025 at 8:29 AM Takashi Yano via Cygwin
wrote:
> On Wed, 5 Mar 2025 11:23:26 +0100
> Christian Franke wrote:
[snip]
> > A 'ps' is a second terminal then shows that the child process is still
> > in S)topped state. 'kill -CONT ...' works t
On Fri, 7 Mar 2025 16:29:51 +0900
Takashi Yano wrote:
> On Wed, 5 Mar 2025 11:23:26 +0100
> Christian Franke wrote:
> > Takashi Yano via Cygwin wrote:
> > > On Mon, 24 Feb 2025 11:29:59 +0100
> > > Christian Franke wrote:
> > >> Found with 's
On Wed, 5 Mar 2025 11:23:26 +0100
Christian Franke wrote:
> Takashi Yano via Cygwin wrote:
> > On Mon, 24 Feb 2025 11:29:59 +0100
> > Christian Franke wrote:
> >> Found with 'stress-ng --cpu-sched 1':
> >>
> >> Testcase (attached):
> &
On Mar 6 13:24, Christian Franke via Cygwin wrote:
> Found because 'stress-ng --context 1 ...' always hangs.
>
> The attached testcase uses the example from Linux swapcontext(3) to call the
> context functions.
Just tested with 3.5.3 and it doesn't work there, either
Hi Corinna, hi Takashi,
Am 06.03.2025 um 11:23 schrieb Rainer Emrich:
Hi Corinna, hi Takashi,
Am 06.03.2025 um 10:58 schrieb Corinna Vinschen via Cygwin:
with a big "THANK YOU!" to Takashi, the "Lost connection" problem will
be fixed in 3.6:
a really big thank you to b
Found because 'stress-ng --context 1 ...' always hangs.
The attached testcase uses the example from Linux swapcontext(3) to call
the context functions.
$ uname -r
3.6.0-0.419.g3c1308ed890e.x86_64
$ gcc -o ctxnosig ctxnosig.c
$ ./ctxnosig # ... and hit ^C
waste_time: started
[^C][SIGINT]
wast
Hi Corinna, hi Takashi,
Am 06.03.2025 um 10:58 schrieb Corinna Vinschen via Cygwin:
with a big "THANK YOU!" to Takashi, the "Lost connection" problem will
be fixed in 3.6:
a really big thank you to both of you.
https://sourceware.org/cgit/newlib-cygwin/commit/?id=691afb1
Hi Rainer,
with a big "THANK YOU!" to Takashi, the "Lost connection" problem will
be fixed in 3.6:
https://sourceware.org/cgit/newlib-cygwin/commit/?id=691afb1f6d5a
The next test release cygwin-3.6.0-0.422.g691afb1f6d5a will contain the
patch. Should be up in about an hou
On Mar 5 20:49, Dimitry Andric via Cygwin wrote:
> In my opinion, it is wrong that scanners rely on this information. :-)
Exactly.
> I guess something similar could be done in the Cygwin package. This is
> up to the Cygwin maintainers of course.
And that doesn't change if some
Guys, I already applied a patch.
Thanks,
Corinna
On Mar 5 15:51, Glenn Strauss via Cygwin wrote:
> On Wed, Mar 05, 2025 at 08:27:53PM +, Lavrentiev, Anton (NIH/NLM/NCBI)
> [C] via Cygwin wrote:
> > > We could change this to a macro instead:
> > >
&
On Wed, Mar 05, 2025 at 08:27:53PM +, Lavrentiev, Anton (NIH/NLM/NCBI) [C]
via Cygwin wrote:
> > We could change this to a macro instead:
> >
> > -static inline void setproctitle_init (int, char *[], char *[]) {}
> > +#define setproctitle_init(c, a, e)
>
&g
> We could change this to a macro instead:
>
> -static inline void setproctitle_init (int, char *[], char *[]) {}
> +#define setproctitle_init(c, a, e)
Changing to the empty marco removes the side effects in the arguments (such as
len++, for example),
which may silently break existing code -- so
try to make the case that Tenable needs to change it's method or get an
exception.
Best Regards,
Ted Summers
From: Dimitry Andric
Sent: Wednesday, March 5, 2025 11:50 AM
To: SUMMERS, TED
Cc: cygwin@cygwin.com
Subject: Re: Cygwin OpenSSH version detection by Tenable
CAUTION: External Email
.patch?ref_type=heads
I guess something similar could be done in the Cygwin package. This is up to
the Cygwin maintainers of course.
-Dimitry
> On 5 Mar 2025, at 20:30, SUMMERS, TED via Cygwin wrote:
>
> Dear list member(s),
>
> I've reviewed the list archives for the
On Mar 5 20:10, Dimitry Andric via Cygwin wrote:
> Maybe it's because -Wsystem-headers is not enabled? I'm unsure what
> gcc's default behavior is with -Wall, but if you add an explicit
> -Wsystem-headers you might still get that warning.
Thanks, that was the reason. Wit
H is still at a vulnerable version.
Even though I have openssh 9.9p2-1 installed, some query methods show the
version only as OpenSSH 9.9.
IF I login to my Cygwin installation and perform "ssh -V" I receive the
expected correct up-to-date values in the response:
OpenSSH_9.9p2, OpenSSL 3.
Maybe it's because -Wsystem-headers is not enabled? I'm unsure what gcc's
default behavior is with -Wall, but if you add an explicit -Wsystem-headers you
might still get that warning.
-Dimitry
> On 5 Mar 2025, at 19:58, Corinna Vinschen via Cygwin
> wrote:
>
>
> The error is valid because the addition of this very old C++ feature
> took a very long time :-)
Well, it may be so, but adding the parameter names in those prototype on Cygwin
end of things would be a better and less disruptive approach, IMO.
$.02,
Anton Lavrentiev
Contractor NIH/NL
On Mar 5 17:16, Christian Franke via Cygwin wrote:
> Roland Mainz via Cygwin wrote:
> > Small issue with Cygwin 3.6 (3.6.0-0.419.g3c1308ed890e.x86_64) system
> > /usr/include/unistd.h and clang:
> > snip
> > $ clang --version
> > clang version 8.0.1 (t
Roland Mainz via Cygwin wrote:
Small issue with Cygwin 3.6 (3.6.0-0.419.g3c1308ed890e.x86_64) system
/usr/include/unistd.h and clang:
snip
$ clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-windows-cygnus
Thread model: posix
InstalledDir: /usr/bin
Hi!
Small issue with Cygwin 3.6 (3.6.0-0.419.g3c1308ed890e.x86_64) system
/usr/include/unistd.h and clang:
snip
$ clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-unknown-windows-cygnus
Thread model: posix
InstalledDir: /usr/bin
$ clang -std=gnu17 -Wall
Takashi Yano via Cygwin wrote:
On Mon, 24 Feb 2025 11:29:59 +0100
Christian Franke wrote:
Found with 'stress-ng --cpu-sched 1':
Testcase (attached):
$ uname -r
3.6.0-0.387.g8cebbb2b42bf.x86_64
$ gcc -o timersig timersig.c
$ ./timersig
638: fork()=639
!...!!
On Tue, 4 Mar 2025, Cedric Blancher via Cygwin wrote:
> Good evening!
>
> Is IO_REPARSE_TAG_LX_SYMLINK supported in Cygwin 3.3?
>
> Ced
Use the Source, Luke
https://sourceware.org/cgit/newlib-cygwin/tree/winsup/cygwin/path.cc?h=cygwin-3_3-branch#n2625
(that's the reading p
Good evening!
Is IO_REPARSE_TAG_LX_SYMLINK supported in Cygwin 3.3?
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https
On Mar 4 12:38, Corinna Vinschen via Cygwin wrote:
> On Mar 4 12:20, Lionel Cons via Cygwin wrote:
> > On Tue, 4 Mar 2025 at 11:08, Corinna Vinschen via Cygwin
> > wrote:
> > >
> > > On Mar 3 23:07, Lionel Cons via Cygwin wrote:
> > > > On Mon, 3 M
On Mar 4 12:20, Lionel Cons via Cygwin wrote:
> On Tue, 4 Mar 2025 at 11:08, Corinna Vinschen via Cygwin
> wrote:
> >
> > On Mar 3 23:07, Lionel Cons via Cygwin wrote:
> > > On Mon, 3 Mar 2025 at 12:43, Corinna Vinschen via Cygwin
> > > wrote:
> > &g
On Tue, 4 Mar 2025 at 11:08, Corinna Vinschen via Cygwin
wrote:
>
> On Mar 3 23:07, Lionel Cons via Cygwin wrote:
> > On Mon, 3 Mar 2025 at 12:43, Corinna Vinschen via Cygwin
> > wrote:
> > >
> > > On Feb 28 15:36, Lionel Cons via Cygwin wrote:
> > &
On Mar 3 23:07, Lionel Cons via Cygwin wrote:
> On Mon, 3 Mar 2025 at 12:43, Corinna Vinschen via Cygwin
> wrote:
> >
> > On Feb 28 15:36, Lionel Cons via Cygwin wrote:
> > > We've hit a scalability issue in Cygwin today, the application in
> > > questi
On Tue, 4 Mar 2025 at 00:21, Dan Shelton via Cygwin wrote:
>
> Hello!
>
> Customer question: How can someone report Windows 10 bugs (kernel
> panic by unprivileged appl, utils bugs etc) related to Cygwin&co to
> Microsoft?
>
Start a blog? Just blog the reproducer,
Hello!
Customer question: How can someone report Windows 10 bugs (kernel
panic by unprivileged appl, utils bugs etc) related to Cygwin&co to
Microsoft?
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
--
Problem reports: https://cygwin.com/problems.html
FAQ: h
On Mon, 3 Mar 2025 at 12:43, Corinna Vinschen via Cygwin
wrote:
>
> On Feb 28 15:36, Lionel Cons via Cygwin wrote:
> > We've hit a scalability issue in Cygwin today, the application in
> > question ran out of POSIX realtime signals (i.e. SIGRTMIN-SIGRTMAX).
> >
>
On Fri, 21 Feb 2025, Jeremy Drake via Cygwin wrote:
> I rebased msys2's msys2-runtime fork of cygwin on top of cygwin's master
> branch, and then rebased git-for-windows' msys2-runtime on top of THAT.
>
> 1. Git for Windows's test suite still passes with that (wh
On Mar 1 01:18, Dan Shelton via Cygwin wrote:
> On Fri, 28 Feb 2025 at 20:34, Dan Shelton wrote:
> >
> > Hello!
> >
> > Which Cygwin/POSIX file locking API work over SMB? We need file
> > locking across multiple SMB clients
>
> Coworker just said that Cy
On Feb 28 15:36, Lionel Cons via Cygwin wrote:
> We've hit a scalability issue in Cygwin today, the application in
> question ran out of POSIX realtime signals (i.e. SIGRTMIN-SIGRTMAX).
>
> Could Cygwin support 128 POSIX realtime signals?
Not possible. sigset_t is an unsigned
On Fri, 28 Feb 2025 at 20:34, Dan Shelton wrote:
>
> Hello!
>
> Which Cygwin/POSIX file locking API work over SMB? We need file
> locking across multiple SMB clients
Coworker just said that Cygwin does not support file locking over
remote (SMB, NFS, ...) filesystems. Is that tru
Hello!
Which Cygwin/POSIX file locking API work over SMB? We need file
locking across multiple SMB clients
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https
We've hit a scalability issue in Cygwin today, the application in
question ran out of POSIX realtime signals (i.e. SIGRTMIN-SIGRTMAX).
Could Cygwin support 128 POSIX realtime signals?
Lionel
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.co
Hi Corinna,
Am 28.02.2025 um 13:46 schrieb Corinna Vinschen via Cygwin:
Hi Rainer,
On Feb 17 20:37, Rainer Emrich via Cygwin wrote:
Am 17.02.2025 um 18:00 schrieb Corinna Vinschen via Cygwin:
On Feb 17 12:51, Rainer Emrich via Cygwin wrote:
I'm facing a strange major issue with scp
Hi Rainer,
On Feb 17 20:37, Rainer Emrich via Cygwin wrote:
> Am 17.02.2025 um 18:00 schrieb Corinna Vinschen via Cygwin:
> > On Feb 17 12:51, Rainer Emrich via Cygwin wrote:
> > > I'm facing a strange major issue with scp. The issue exists in all cygwin
> &g
On Mon, 24 Feb 2025 11:29:59 +0100
Christian Franke wrote:
> Found with 'stress-ng --cpu-sched 1':
>
> Testcase (attached):
>
> $ uname -r
> 3.6.0-0.387.g8cebbb2b42bf.x86_64
>
> $ gcc -o timersig timersig.c
>
> $ ./timersig
> 638: fork()=639
> !...!SIGSTOP: Permission de
On Feb 27 05:58, Roland Mainz via Cygwin wrote:
> On Wed, Feb 26, 2025 at 9:26 PM Corinna Vinschen via Cygwin
> wrote:
> > On Feb 26 20:16, Roland Mainz via Cygwin wrote:
> > > Something is wrong with UNC paths in Cygwin 3.6 build
> > > 3.6.0-0.404.g323729f654ae.x86_
On Wed, Feb 26, 2025 at 9:26 PM Corinna Vinschen via Cygwin
wrote:
> On Feb 26 20:16, Roland Mainz via Cygwin wrote:
> > Something is wrong with UNC paths in Cygwin 3.6 build
> > 3.6.0-0.404.g323729f654ae.x86_64 and ms-nfs41-client 2025-02-21:
> >
> > Example:
On Feb 26 20:16, Roland Mainz via Cygwin wrote:
> Hi!
>
> -
>
> Something is wrong with UNC paths in Cygwin 3.6 build
> 3.6.0-0.404.g323729f654ae.x86_64 and ms-nfs41-client 2025-02-21:
>
> Example:
> snip
> $ cd //derfwnb4966_ipv4.global.loc@2049/n
Hi!
-
Something is wrong with UNC paths in Cygwin 3.6 build
3.6.0-0.404.g323729f654ae.x86_64 and ms-nfs41-client 2025-02-21:
Example:
snip
$ cd //derfwnb4966_ipv4.global.loc@2049/nfs4/bigdisk/builds/bash_build1
$ rm -Rfv bash
removed 'bash/builtins/hash.o'
removed
Cygwin must be a valuable business to be a command line interface.
Microsoft Windows since Windows NT 2000, has advertised Cygwin. MS-DOS was
renounced from system platform, near the year 2000. Cygwin was proposed as
a download command line interface as a video game development. Whereas my
main
On Feb 25 14:49, Christian Franke via Cygwin wrote:
> Corinna Vinschen via Cygwin wrote:
> > [I sent this on 2024-02-14 to the cygwin-announce mailing list,
> > but forgot to CC the cygwin mailing list. Doing it now...]
> >
> >
> > Hi folks,
> >
>
Corinna Vinschen via Cygwin wrote:
[I sent this on 2024-02-14 to the cygwin-announce mailing list,
but forgot to CC the cygwin mailing list. Doing it now...]
Hi folks,
we're planning the next major release in the next few (hopefully
not more than two) weeks.
...
Below you'll find
On Feb 24 17:01, LLoyd via Cygwin wrote:
> Hello.
>
> I'll try to keep this short:
> In Cygwin only, using bash 5.2.21-1 or 5.2.15-3 (the only 5.* versions
> available), "empty" in a regular expression is not properly matched
> and breaks the regular expression.
&
On Mon, 24 Feb 2025 at 17:01, LLoyd wrote:
>
> [...]
> reg='foo|'; [[ foo =~ $regex ]]
>
> [...]
Sorry, typo on that line, I meant to write that I also tested:
regex='foo|'; [[ foo =~ $regex ]]
It's probably a libc bug.
Please let me know if I can do anything.
LLoyd
--
Problem reports: h
Hello.
I'll try to keep this short:
In Cygwin only, using bash 5.2.21-1 or 5.2.15-3 (the only 5.* versions
available), "empty" in a regular expression is not properly matched
and breaks the regular expression.
It's not a quoting issue, I also tested with:
reg='foo|';
Found with 'stress-ng --cpu-sched 1':
Testcase (attached):
$ uname -r
3.6.0-0.387.g8cebbb2b42bf.x86_64
$ gcc -o timersig timersig.c
$ ./timersig
638: fork()=639
!...!SIGSTOP: Permission denied
0 [itimer] timersig 639 sig_send: error sending signal 14, pid 639,
pipe
It seems the " -engine 1" parameter was all that was needed.
Cygwin/X now shows up on my new Windows 11 laptop, as it did on my older
one, with the saved session bringing up three xterm windows and all.
Giving me a richer experience and enabling me to work more efficiently than
when I ha
On Feb 22 09:24, Jeremy Drake via Cygwin wrote:
> On Sat, 22 Feb 2025, Corinna Vinschen via Cygwin wrote:
>
> > On Feb 21 14:35, Jeremy Drake via Cygwin wrote:
> > > 2. This seems to have fixed a severe performance regression in Curl's test
> > > suite (http
On Sat, 22 Feb 2025, Corinna Vinschen via Cygwin wrote:
> On Feb 21 14:35, Jeremy Drake via Cygwin wrote:
> > 2. This seems to have fixed a severe performance regression in Curl's test
> > suite (https://github.com/curl/curl/pull/16217) that I was recently
> > looking
Cedric Blancher via Cygwin writes:
> We are VERY concerned that this plan will backfire. Basically nothing
> here works right now, and we are still trying to determinate the root
> causes. Plural. Too many bugs.
I've said it before, but if you really didn't recognize it unti
On Feb 21 14:35, Jeremy Drake via Cygwin wrote:
> I rebased msys2's msys2-runtime fork of cygwin on top of cygwin's master
> branch, and then rebased git-for-windows' msys2-runtime on top of THAT.
>
> 1. Git for Windows's test suite still passes with that (which i
On Fri, 21 Feb 2025 at 17:41, Brian Inglis via Cygwin wrote:
>
> Please retry with latest test 3.6 as it is scheduled to be promoted to current
> stable in the next few weeks.
We are VERY concerned that this plan will backfire. Basically nothing
here works right now, and we are still
I rebased msys2's msys2-runtime fork of cygwin on top of cygwin's master
branch, and then rebased git-for-windows' msys2-runtime on top of THAT.
1. Git for Windows's test suite still passes with that (which is nice, it
tended to hang when we did this with 3.5.5).
2. This s
Please retry with latest test 3.6 as it is scheduled to be promoted to current
stable in the next few weeks.
On 2025-02-20 06:58, Cedric Blancher via Cygwin wrote:
Given that updating to Cygwin 3.6 broke LOTS of scripts and
applications here, and therefore seems to be MONTHS away from being
On 19/02/2025 19:05, Erik Dybdahl via Cygwin wrote:
Actually, I found a way to make it work somehow, namely by passing "-engine
1" to XWin.exe, following a (21 year old) tip from here:
https://cygwin-xfree.cygwin.narkive.com/maSzrlKY/crash-when-remote-desktop-changes-screen-resolution
On Fri, Feb 21, 2025 at 11:33 AM Corinna Vinschen via Cygwin <
cygwin@cygwin.com> wrote:
>
> On Feb 20 23:49, Martin Wege via Cygwin wrote:
> > Hello!
> >
> > FYI https://github.com/mirror/newlib-cygwin has not been getting
> > updates for months. Can anyone p
On Feb 21 12:15, Christian Franke via Cygwin wrote:
> Corinna Vinschen via Cygwin wrote:
> > ...
> >
> > I just deployed 0.12.2-2 as test. Apart from setproctitle{_init}, it
> > also drops exporting the following symbols already exported from Cygwi
Corinna Vinschen via Cygwin wrote:
...
I just deployed 0.12.2-2 as test. Apart from setproctitle{_init}, it
also drops exporting the following symbols already exported from Cygwin:
arc4random*
explicit_bzero
fpurge
getprogname
reallocarray
reallocf
On Feb 20 23:49, Martin Wege via Cygwin wrote:
> Hello!
>
> FYI https://github.com/mirror/newlib-cygwin has not been getting
> updates for months. Can anyone please have a look?
Wrong address. We have nothing to do with https://github.com/mirror.
Our official github mirror
Hello!
FYI https://github.com/mirror/newlib-cygwin has not been getting
updates for months. Can anyone please have a look?
Thanks,
Martin
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Hey there
cygwin ,
I hope all is well with you! I am Melissa Lazaro reaching out to you from
SAKUTO KNIVES JP, We are famed for our top-quality Damascus Chef Knives.
We have been reviewing cygwin, for quite some time, and We find your content to
be perpetually impressive and captivating
On Feb 20 16:32, Takashi Yano via Cygwin wrote:
> On Wed, 19 Feb 2025 16:23:41 +0900
> Takashi Yano wrote:
> > On Wed, 19 Feb 2025 07:59:00 +0100
> > Cedric Blancher wrote:
> > > Good morning!
> > >
> > > Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on
Good afternoon!
Given that updating to Cygwin 3.6 broke LOTS of scripts and
applications here, and therefore seems to be MONTHS away from being
usable, it'll be nice to put fac7441835b00d3b9a8252538bcf54c441c3841e
on the 3.5-branch and make a Cygwin 3.5.8 release.
Ced
-- Forw
On Feb 20 12:38, Cedric Blancher via Cygwin wrote:
> On Wed, 19 Feb 2025 at 22:30, Corinna Vinschen via Cygwin
> wrote:
> >
> > On Feb 18 19:34, Cedric Blancher via Cygwin wrote:
> > > Good evening!
> > >
> > > Cygwin 3.6.0-0.374.g4dd859d01c22.x86_
On Wed, 19 Feb 2025 at 22:30, Corinna Vinschen via Cygwin
wrote:
>
> On Feb 18 19:34, Cedric Blancher via Cygwin wrote:
> > Good evening!
> >
> > Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on Win10/AMD64/64bit:
> >
> > df -k no longer shows the data of SMB fil
On Feb 20 10:44, Corinna Vinschen via Cygwin wrote:
> On Feb 20 10:39, Corinna Vinschen via Cygwin wrote:
> > On Feb 20 08:34, Christian Franke via Cygwin wrote:
> > > Corinna Vinschen via Cygwin wrote:
> > > > I uploaded a 0.11.8-1 test package which fixes this iss
On Feb 20 10:39, Corinna Vinschen via Cygwin wrote:
> On Feb 20 08:34, Christian Franke via Cygwin wrote:
> > Corinna Vinschen via Cygwin wrote:
> > > I uploaded a 0.11.8-1 test package which fixes this issue. I'll
> > > propagate it to non-test when 3.6.0 is rele
On Feb 20 08:34, Christian Franke via Cygwin wrote:
> Corinna Vinschen via Cygwin wrote:
> > On Feb 19 16:37, Corinna Vinschen via Cygwin wrote:
> > > On Feb 19 14:40, Corinna Vinschen via Cygwin wrote:
> > > > On Feb 19 14:25, Christian Franke via Cygwin wrote:
Corinna Vinschen via Cygwin wrote:
On Feb 19 16:37, Corinna Vinschen via Cygwin wrote:
On Feb 19 14:40, Corinna Vinschen via Cygwin wrote:
On Feb 19 14:25, Christian Franke via Cygwin wrote:
Corinna Vinschen via Cygwin wrote:
So I think we rather shouldn't supply the libbsd versi
On Wed, 19 Feb 2025 16:23:41 +0900
Takashi Yano wrote:
> On Wed, 19 Feb 2025 07:59:00 +0100
> Cedric Blancher wrote:
> > Good morning!
> >
> > Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on Win10/AMD64/64bit:
> >
> > Pipe between Cygwin and non Cygwin (CRT/URT)
On Thu, 20 Feb 2025, Roland Mainz via Cygwin wrote:
> > > Same happens with dash and ksh93.
>
> And THAT statement is BAD, because it means basic shell functionality
> is broken, affecting dash/bash/ksh93 - reading that IMO means Cygwin
> has a problem in the pipe/fifo cod
On Wed, Feb 19, 2025 at 8:23 AM Takashi Yano via Cygwin
wrote:
>
> On Wed, 19 Feb 2025 07:59:00 +0100
> Cedric Blancher wrote:
> > Good morning!
> >
> > Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on Win10/AMD64/64bit:
> >
> > Pipe between Cygwin and non Cygwin
On Feb 18 19:34, Cedric Blancher via Cygwin wrote:
> Good evening!
>
> Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on Win10/AMD64/64bit:
>
> df -k no longer shows the data of SMB filesystems, e.g. mount points
> N:-Z: are mounted, but df -k shows nothing:
> $ df -k
> F
On Feb 19 16:37, Corinna Vinschen via Cygwin wrote:
> On Feb 19 14:40, Corinna Vinschen via Cygwin wrote:
> > On Feb 19 14:25, Christian Franke via Cygwin wrote:
> > > Corinna Vinschen via Cygwin wrote:
> > > > So I think we rather shouldn't supply the libbsd v
Actually, I found a way to make it work somehow, namely by passing "-engine
1" to XWin.exe, following a (21 year old) tip from here:
https://cygwin-xfree.cygwin.narkive.com/maSzrlKY/crash-when-remote-desktop-changes-screen-resolutions
ons. 19. feb. 2025 kl. 19:59 skrev Erik Dybdahl :
Thanks,
That first command does indeed cause a server window titled "Cygwin/X:0.0
to appear (an all white window).
The next command gives some info and warnings, and then 10 of these:
winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 88760827
winShadowUpdateDDNL - IDirectDrawSurface
On Feb 19 14:40, Corinna Vinschen via Cygwin wrote:
> On Feb 19 14:25, Christian Franke via Cygwin wrote:
> > Corinna Vinschen via Cygwin wrote:
> > > So I think we rather shouldn't supply the libbsd version of
> > > setproctitle_init/setproctitle anymore, as soon a
On Feb 19 14:25, Christian Franke via Cygwin wrote:
> Hi Corinna,
>
> Corinna Vinschen via Cygwin wrote:
> > Hi Christian,
> >
> > On Feb 19 11:14, Christian Franke via Cygwin wrote:
> > > Testcase:
> > >
> > > $ uname -r
> > > 3
Hi Corinna,
Corinna Vinschen via Cygwin wrote:
Hi Christian,
On Feb 19 11:14, Christian Franke via Cygwin wrote:
Testcase:
$ uname -r
3.6.0-0.375.ged18acfe8c76.x86_64
$ cygcheck -f /usr/include/bsd/unistd.h
libbsd-devel-0.11.7-3
$ cat spt.c
#include
int main(int argc, char **argv, char
Hi Christian,
On Feb 19 11:14, Christian Franke via Cygwin wrote:
> Testcase:
>
> $ uname -r
> 3.6.0-0.375.ged18acfe8c76.x86_64
>
> $ cygcheck -f /usr/include/bsd/unistd.h
> libbsd-devel-0.11.7-3
>
> $ cat spt.c
> #include
>
> int mai
On Feb 19 09:54, Takashi Yano via Cygwin wrote:
> On Wed, 19 Feb 2025 01:20:59 +0100
> Lionel Cons wrote:
> > Something is very wrong with bash. If I redirect the output of xcopy
> > or icacls into a bash variable, like stdout="$(icacls "$(cygpath -w
> > "
Testcase:
$ uname -r
3.6.0-0.375.ged18acfe8c76.x86_64
$ cygcheck -f /usr/include/bsd/unistd.h
libbsd-devel-0.11.7-3
$ cat spt.c
#include
int main(int argc, char **argv, char **envp)
{
initsetproctitle(argc, argv, envp);
setproctitle("argc = %d", argc);
sleep(2);
return 0;
}
$ gcc -o
On Wed, 19 Feb 2025 07:59:00 +0100
Cedric Blancher wrote:
> Good morning!
>
> Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on Win10/AMD64/64bit:
>
> Pipe between Cygwin and non Cygwin (CRT/URT) randomly loses
> characters. We do not have a reproducer yet, but it is happening at
>
On Wed, 19 Feb 2025 07:59:00 +0100
Cedric Blancher wrote:
> Good morning!
>
> Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on Win10/AMD64/64bit:
>
> Pipe between Cygwin and non Cygwin (CRT/URT) randomly loses
> characters. We do not have a reproducer yet, but it is happening at
>
Good morning!
Cygwin 3.6.0-0.374.g4dd859d01c22.x86_64 on Win10/AMD64/64bit:
Pipe between Cygwin and non Cygwin (CRT/URT) randomly loses
characters. We do not have a reproducer yet, but it is happening at
least hourly on our test machines. Sometimes we only get a single
character, and sometimes
On Tue, 18 Feb 2025 at 21:02, Corinna Vinschen via Cygwin
wrote:
>
> On Feb 18 11:41, Jeremy Drake via Cygwin wrote:
> > On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
> >
> > > On Feb 18 11:19, Jeremy Drake via Cygwin wrote:
> > > > On Tue, 18 Feb
. Very
> strange
Thanks for the report. But I cannot reproduce that.
Doesn't this occur with cygwin 3.5.7?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscri
Something is very wrong with bash. If I redirect the output of xcopy
or icacls into a bash variable, like stdout="$(icacls "$(cygpath -w
"$PWD")")", then sometimes I get only a letter in the middle. Very
strange
Lionel
On Tue, 18 Feb 2025 at 10:37, Corinna Vinsch
On Feb 18 11:41, Jeremy Drake via Cygwin wrote:
> On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
>
> > On Feb 18 11:19, Jeremy Drake via Cygwin wrote:
> > > On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
> > >
> > > > Yep. Are you go
On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
> On Feb 18 11:19, Jeremy Drake via Cygwin wrote:
> > On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
> >
> > > Yep. Are you going to create a patch?
> >
> > I'm not seeing a parti
On Feb 18 20:29, Corinna Vinschen via Cygwin wrote:
> On Feb 18 11:19, Jeremy Drake via Cygwin wrote:
> > On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
> >
> > > Yep. Are you going to create a patch?
> >
> > I'm not seeing a parti
On Feb 18 11:19, Jeremy Drake via Cygwin wrote:
> On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
>
> > Yep. Are you going to create a patch?
>
> I'm not seeing a particularly clean way to do this. Bring back
> available_drives, mask off bits when we see th
On Tue, 18 Feb 2025, Corinna Vinschen via Cygwin wrote:
> Yep. Are you going to create a patch?
I'm not seeing a particularly clean way to do this. Bring back
available_drives, mask off bits when we see the corresponding drive root
from dos_drive_mappings, and return those drive lette
1 - 100 of 40254 matches
Mail list logo
