win program is launched from a non-Cygwin shell, I personally
find it more natural for it to follow quoting semantics similar to Bash.
I'm afraid that's not the case...
> It sadly breaks builds driven by Windows-native tools since they expect
> the standard command line handli
pected output. Is the way the escaped quotation mark is
> treated intended
> behavior? I cannot really see how it would be, given that the parser is only
> used for command lines
> stemming from being launched by Windows-native programs.
>echo-win32.exe C:\"Program File
On Wed, 23 Jul 2025 17:02:22 +0900
Takashi Yano wrote:
> Recent cygwin setup-x86_64.exe has Japanese translation and
> it uses Japanese when it is running in Japanese Windows.
>
> However, sometimes I would like to setup-x86_64.exe with
> English. I tried:
> LANG=en_US.UTF-8
&g
force setup.exe to use English?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
On Fri, 18 Jul 2025 22:32:01 +0900
Takashi Yano wrote:
> On Fri, 18 Jul 2025 21:31:52 +0900
> Takashi Yano wrote:
> > On Fri, 18 Jul 2025 09:54:20 +0200
> > Corinna Vinschen wrote:
> > > On Jul 18 01:28, Takashi Yano via Cygwin wrote:
> > > > On Fri, 18 Jul 2
On Sat, 19 Jul 2025 00:04:56 +0900
Takashi Yano wrote:
> On Fri, 18 Jul 2025 16:25:49 +0200
> Corinna Vinschen wrote:
> > On Jul 18 22:32, Takashi Yano via Cygwin wrote:
> > > I embedded debug code into mm/cygheap.cc, that is:
> > >
> > > diff --git a/wins
On Fri, 18 Jul 2025 16:25:49 +0200
Corinna Vinschen wrote:
> On Jul 18 22:32, Takashi Yano via Cygwin wrote:
> > I embedded debug code into mm/cygheap.cc, that is:
> >
> > diff --git a/winsup/cygwin/mm/cygheap.cc b/winsup/cygwin/mm/cygheap.cc
> > index 338886468..bab406
On Fri, 18 Jul 2025 21:31:52 +0900
Takashi Yano wrote:
> On Fri, 18 Jul 2025 09:54:20 +0200
> Corinna Vinschen wrote:
> > On Jul 18 01:28, Takashi Yano via Cygwin wrote:
> > > On Fri, 18 Jul 2025 00:44:46 +0900
> > > Takashi Yano wrote:
> > > > On Thu,
On Fri, 18 Jul 2025 09:54:20 +0200
Corinna Vinschen wrote:
> On Jul 18 01:28, Takashi Yano via Cygwin wrote:
> > On Fri, 18 Jul 2025 00:44:46 +0900
> > Takashi Yano wrote:
> > > On Thu, 17 Jul 2025 17:19:49 +0200
> > > Corinna Vinschen wrote:
> > > > O
On Fri, 18 Jul 2025 17:42:47 +0900
Takashi Yano wrote:
> On Fri, 18 Jul 2025 09:54:20 +0200
> Corinna Vinschen wrote:
> > On Jul 18 01:28, Takashi Yano via Cygwin wrote:
> > > On Fri, 18 Jul 2025 00:44:46 +0900
> > > Takashi Yano wrote:
> > > > On Thu,
On Fri, 18 Jul 2025 09:51:11 +0200
Corinna Vinschen via Cygwin wrote:
> On Jul 18 00:44, Takashi Yano via Cygwin wrote:
> > On Thu, 17 Jul 2025 17:19:49 +0200
> > Corinna Vinschen wrote:
> > > On Jul 17 23:14, Takashi Yano via Cygwin wrote:
> > > > Hi Cori
On Fri, 18 Jul 2025 09:54:20 +0200
Corinna Vinschen wrote:
> On Jul 18 01:28, Takashi Yano via Cygwin wrote:
> > On Fri, 18 Jul 2025 00:44:46 +0900
> > Takashi Yano wrote:
> > > On Thu, 17 Jul 2025 17:19:49 +0200
> > > Corinna Vinschen wrote:
> > > > O
On Fri, 18 Jul 2025 09:55:27 +0200
Corinna Vinschen wrote:
> On Jul 18 00:32, Takashi Yano via Cygwin wrote:
> > On Thu, 17 Jul 2025 23:14:21 +0900
> > Takashi Yano wrote:
> > > As a starting point, I tried tntroducing locking. It almost works
> > > as expected
On Fri, 18 Jul 2025 00:44:46 +0900
Takashi Yano wrote:
> On Thu, 17 Jul 2025 17:19:49 +0200
> Corinna Vinschen wrote:
> > On Jul 17 23:14, Takashi Yano via Cygwin wrote:
> > > Hi Corinna,
> > >
> > > On Wed, 16 Jul 2025 17:36:42 +0200
> > > Corinna
On Thu, 17 Jul 2025 17:19:49 +0200
Corinna Vinschen wrote:
> On Jul 17 23:14, Takashi Yano via Cygwin wrote:
> > Hi Corinna,
> >
> > On Wed, 16 Jul 2025 17:36:42 +0200
> > Corinna Vinschen wrote:
> > > On Jul 16 23:52, Takashi Yano via Cygwin
On Thu, 17 Jul 2025 23:14:21 +0900
Takashi Yano wrote:
> As a starting point, I tried tntroducing locking. It almost works
> as expected, however, sometimes my STC in my first report is hangs
> if N is large e.g. 100. The patch is as attached.
>
> What am I missing?
Patch revise
Hi Corinna,
On Wed, 16 Jul 2025 17:36:42 +0200
Corinna Vinschen wrote:
> On Jul 16 23:52, Takashi Yano via Cygwin wrote:
> > Hi Corinna,
> >
> > On Wed, 18 Jun 2025 20:31:27 +0900
> > Takashi Yano wrote:
> > > On Tue, 17 Jun 2025 15:42:26 -0700
> >
Hi Corinna,
On Wed, 18 Jun 2025 20:31:27 +0900
Takashi Yano wrote:
> On Tue, 17 Jun 2025 15:42:26 -0700
> Mark Geisert wrote:
> > Hi Takashi,
> >
> > On 6/17/2025 5:54 AM, Takashi Yano via Cygwin wrote:
> > > Hi,
> > >
> > > If system() is
On Wed, 16 Jul 2025 22:45:32 +0900
Takashi Yano via Cygwin wrote:
> On Wed, 16 Jul 2025 21:36:04 +0900
> Takashi Yano via Cygwin wrote:
> > On Wed, 16 Jul 2025 21:13:59 +0900
> > Takashi Yano via Cygwin wrote:
> >
> > > On Tue, 17 Jun 2025 21:46:47 +0900
&g
On Wed, 16 Jul 2025 21:36:04 +0900
Takashi Yano via Cygwin wrote:
> On Wed, 16 Jul 2025 21:13:59 +0900
> Takashi Yano via Cygwin wrote:
>
> > On Tue, 17 Jun 2025 21:46:47 +0900
> > Takashi Yano wrote:
> > > I encountered a problem of doxygen when many call graphs a
On Wed, 16 Jul 2025 21:13:59 +0900
Takashi Yano via Cygwin wrote:
> On Tue, 17 Jun 2025 21:46:47 +0900
> Takashi Yano wrote:
> > I encountered a problem of doxygen when many call graphs are generated.
> >
> > How to reproduce:
> > 1) Make a empty directory.
> &g
On Tue, 17 Jun 2025 21:46:47 +0900
Takashi Yano wrote:
> I encountered a problem of doxygen when many call graphs are generated.
>
> How to reproduce:
> 1) Make a empty directory.
> 2) Place two files (Doxyfile, x.c) attached in the directory.
> 3) Run doxygen in the directory.
On Sun, 13 Jul 2025 20:34:56 +0900
Takashi Yano wrote:
> On Sun, 13 Jul 2025 11:40:10 +0200
> Christoph Reiter wrote:
> > I'm having the problem that under cygwin flushing stdin for some reason
> > doesn't
> > work when running in mintty. It works when running
sizeof(buffer), stdin);
> printf("You entered: %s\n", buffer);
>
> return 0;
> }
> ```
Thanks for the report.
This seems to be a bug of pty code. If you enter 'return' key
in the first 5 sec, the input will be flushed.
I'll look into that.
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
On Tue, 17 Jun 2025 15:42:26 -0700
Mark Geisert wrote:
> Hi Takashi,
>
> On 6/17/2025 5:54 AM, Takashi Yano via Cygwin wrote:
> > Hi,
> >
> > If system() is called in parallel in threads, system()
> > fails with exit code 127.
> >
> > Just compile
Hi,
If system() is called in parallel in threads, system()
fails with exit code 127.
Just compile pthread_system.c attached and run.
I believe system() is multi-thread safe so the STC
should work.
--
Takashi Yano
#include
#include
#include
#include
#include
void *func(void *arg
On Sat, 31 May 2025 09:00:10 +0900
Takashi Yano wrote:
> On Sat, 31 May 2025 00:39:24 +0200
> Dan Shelton wrote:
> > Hello!
> >
> > Does Cygwin have a compiler which allows compiling ISO C applications
> > as DOS *.exe?
>
> If you mean 16-bit MS-DOS *.exe by
ll the package
mingw64-x86_64-gcc-core-12.4.0-1 (64-bit)
or
mingw64-i686-gcc-core-12.4.0-1 (32-bit)
and compile with
mingw64-x86_64-gcc-core-12.4.0-1 (64-bit)
or
mingw64-i686-gcc-core-12.4.0-1 (32-bit)
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ:
On Thu, 29 May 2025 20:01:31 +0200
Christian Franke wrote:
> Takashi Yano via Cygwin wrote:
> > On Thu, 29 May 2025 17:32:19 +0200
> > Christian Franke wrote:
> > ...
> >> I still don't fully understand why a SIGSEGV triggered by an instruction
> >> c
On Thu, 29 May 2025 17:32:19 +0200
Christian Franke wrote:
> Takashi Yano via Cygwin wrote:
> > On Wed, 28 May 2025 21:57:07 +0900
> > Takashi Yano wrote:
> >> Hi Christian,
> >>
> >> On Mon, 19 May 2025 12:55:46 +0200
> >> Christian Frank
On Wed, 28 May 2025 21:57:07 +0900
Takashi Yano wrote:
> Hi Christian,
>
> On Mon, 19 May 2025 12:55:46 +0200
> Christian Franke wrote:
> > The attached testcase was originally intended to investigate why a
> > SIGSEGV from non-signal code could interrupt an already run
(pid: 1342) thread 5056 exited with status 0x0
> [several minutes delay]
> --- Process 148 (pid: 1342) thread 9388 created
>
> The process then ignores SIGKILL.
Thanks for reporting this. I finally found the solution.
Please test
https://cygwin.com/pipermail/cygwin-patches/2025q2/01373
On Fri, 16 May 2025 15:08:16 -0400
Ken Brown wrote:
> On 5/16/2025 4:59 AM, Takashi Yano via Cygwin wrote:
> > On Fri, 16 May 2025 08:46:40 +0900
> > Takashi Yano wrote:
> >> diff --git a/winsup/cygwin/local_includes/cygheap.h
> >> b/winsup/cygwin/local_includ
Hi Jon,
On Fri, 16 May 2025 21:14:00 +0900
Takashi Yano via Cygwin wrote:
> On Fri, 16 May 2025 13:46:21 +0200
> Christian Franke wrote:
> > Testcase:
> >
> > $ uname -r # Also occurs with 3.6.1-1.x86_64
> > 3.7.0-0.95.g854150fda310.x86_64
> &g
on c005 at 000
> SUCCESS: ... (localized message from taskkill)
>
>
> The problem also occurs if a SIGSEGV handler is present. The handler
> code is not executed if strace is used but works as expected without strace.
I could reproduce that. And also found cygwin
On Fri, 16 May 2025 08:46:40 +0900
Takashi Yano wrote:
> diff --git a/winsup/cygwin/local_includes/cygheap.h
> b/winsup/cygwin/local_includes/cygheap.h
> index fed87ec2b..7d11fbb37 100644
> --- a/winsup/cygwin/local_includes/cygheap.h
> +++ b/winsup/cygwin/local_includes/cyghea
Hi Ken,
On Thu, 15 May 2025 18:18:26 -0400
Ken Brown wrote:
> Hi Takashi,
>
> On 5/14/2025 5:29 AM, Takashi Yano via Cygwin wrote:
> > Hi Ken,
> >
> > I encountered the problem with fifo. The following STC hangs
> > in cygwin while it works in linux.
>
pthread_create(&th, NULL, thr1, NULL);
fd = open(fifo1, O_RDONLY);
pthread_join(th, NULL);
read(fd, &c, 1);
write(1, &c, 1);
close(fd);
return 0;
}
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ:
42), exception c096 at 0001004011b9
> --- Process 6856 (pid: 142), exception c096 at 0001004011b9
> ... likely repeated until disk is full or time_t wraps around...
> --- Process 6856 (pid: 142), exception c096 at 0001004011b9
>
>
> Problem also occurs
> - w
ce_name}
> then
>echo
>echo "There is a cygserver (${service_name}) already running. Nothing to
> do, apparently."
Thanks for the report and patch snippet. I'll push the fix.
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ:
/debug/cygwin-3.7.0-0.68.g37c49decc835/winsup/cygwin/cygtls.cc:28
> #5 0x7ffe66f17374 in KERNEL32!BaseThreadInitThunk () from
> /cygdrive/c/Windows/System32/KERNEL32.DLL
> #6 0x7ffe68f3cc91 in ntdll!RtlUserThreadStart () from
> /cygdrive/c/Windows/SYSTEM32/ntdll.dll
>
On Sun, 20 Apr 2025 19:15:42 +0200
Bruno Haible wrote:
> Hi,
>
> Takashi Yano wrote:
> > > > Thanks for the new testcase. I think the issue has been fixed in:
> > > > cygwin-3.7.0-0.68.g37c49decc835 (Test)
> > >
> > > Thanks.
> > >
but it is not going smoothly.
Is there any other blocker to build Rust for cygwin?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
On Tue, 15 Apr 2025 11:33:55 +0200
Bruno Haible wrote:
> Takashi Yano wrote:
> > Thanks for the new testcase. I think the issue has been fixed in:
> > cygwin-3.7.0-0.68.g37c49decc835 (Test)
>
> Thanks.
>
> > Please test.
>
> Sorry, I don't know how
On Tue, 15 Apr 2025 21:58:19 +0900
Takashi Yano via Cygwin wrote:
> On Tue, 15 Apr 2025 06:43:33 -0600
> Brian Inglis via Cygwin wrote:
> > On 2025-04-15 03:33, Bruno Haible via Cygwin wrote:
> > > Takashi Yano wrote:
> > >> Thanks for the new testcase. I
On Tue, 15 Apr 2025 06:43:33 -0600
Brian Inglis via Cygwin wrote:
> On 2025-04-15 03:33, Bruno Haible via Cygwin wrote:
> > Takashi Yano wrote:
> >> Thanks for the new testcase. I think the issue has been fixed in:
> >> cygwin-3.7.0-0.68.g37c49decc835 (Test)
> >
pusshed is
cygwin-3.7.0-0.68.g37c49decc835.
Could you please have a look?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml
pusshed is
cygwin-3.7.0-0.68.g37c49decc835.
Could you please take a look?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml
.6.1, the most likely culprit
> > is commit d750786e7de013b58e2968eeb6a7fd59dcc535c9 .
>
> Especially since this commit modified select.cc, removing a comment
> /* TODO: Buffer really full or non-Cygwin reader? */
> and here we are exactly in that case: a non-Cygwin process rea
fprintf (stderr, "incorrect return value\n");
> exit (1);
> }
> fprintf (result_file, "%d\n", ret);
> exit (0);
> }
> }
> }
> }
> fprintf (stderr, "Usage: test-select-fd mode fd
On Thu, 10 Apr 2025 10:39:02 -0700 (PDT)
Jeremy Drake wrote:
> On Thu, 10 Apr 2025, Takashi Yano via Cygwin wrote:
>
> > On Wed, 9 Apr 2025 16:41:18 -0700 (PDT)
> > Jeremy Drake wrote:
> > > I've been doing some building with cmake 4.0.0 and ninja 1.12.1 (of
>
or the child process
exits. This is due to a bug introduced by:
3312f2d21f13 ("Cygwin: console: Redesign mode set strategy on close().")
Could you please test if the patch attached helps?
--
Takashi Yano
diff --git a/winsup/cygwin/fhandler/console.cc
b/winsup/cygwin/fhandler/console.
e, so List_insert method cannot lock the mutex again.
>
> I have searched though the POSIX docs and didn't find any words that one
> should not call pthread_key_create in the destructor of a pthread_key. I
> think it should be a bug of cygwin.
Fixed. Please try cygwin-3.7.0-0.4
client_fd == -1) {
> perror("client socket");
> exit(EXIT_FAILURE);
> }
>
> if (connect(client_fd, (struct sockaddr*)&server_addr,
> sizeof(server_addr)) == -1) {
> perror("connect");
> exit(EXIT_FAIL
On Wed, 2 Apr 2025 23:41:46 -0700 (PDT)
Jeremy Drake wrote:
> On Thu, 3 Apr 2025, Takashi Yano via Cygwin wrote:
>
> > It seems that raw_write() is called before returning from
> > pthread::atforkchild() in fork::child().
> >
> > Moving _my_tls.fixup_after_fork() bef
On Thu, 3 Apr 2025 12:32:35 +0900
Takashi Yano wrote:
> > Still, I wonder in which thread raw_write is running during fork().
>
> Weird enough, raw_write() is called in the main thread (_main_tls).
> Any chance, fixup_after_fork() is not called?
It seems that raw_write() i
On Wed, 2 Apr 2025 20:15:54 +0200
Corinna Vinschen wrote:
> Hi Takashi,
>
> On Apr 3 01:52, Takashi Yano via Cygwin wrote:
> > > Currently, I am looking into this problem.
> > >
> > > What I noticed so far is:
> > > * The problem occurs after the
On Wed, 2 Apr 2025 22:01:25 +0900
Takashi Yano via Cygwin wrote:
> Hi Corinna,
>
> On Mon, 31 Mar 2025 11:28:44 +0200
> Corinna Vinschen wrote:
> > On Mar 30 22:58, Jeremy Drake via Cygwin wrote:
> > > On Mon, 31 Mar 2025, Christoph Reiter via Cygwin wrote:
> &g
; !GetHandleInformation (signal_arrived, &dummy))
+ signal_arrived = NULL;
if (!signal_arrived)
{
if (wait_for_lock)
Of course, this is not the right thing to do, but this clarifies that the
cause is _cygtis::signal_arrived being invalid even though it is not NULL.
Th
On Mon, 24 Mar 2025 22:52:04 +0900
Takashi Yano wrote:
> On Mon, 24 Mar 2025 13:26:27 +0100
> Bruno Haible wrote:
> > Hi,
> >
> > Gnulib contains a few unit tests for
> > - SIGSEGV handling,
> > - stack overflow handling (via signal SIGSEGV or SIGBUS
gwin machine.
> 3. Build it: ./configure && make && make check
Thanks for the report and reprodusible steps.
In my environment, one of your problems is reproduced.
FAIL: test-c-stack.sh
PASS: test-sigsegv-catch-segv2.exe
$ uname -a
CYGWIN_NT-10.0-19045 HP-Z230 3.6.0-1.x86_64 2025
t compiler can be a cygwin-
bynary. Are there something missing from cygwin to do that?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
cygtls::interrupt_setup: armed
> signal_arrived 0x0, signal 2
> 70 15746843 [sig] dflagsig 1288 sigpacket::setup_handler: signal 2
> delivered
> --- Process 12736 (pid: 1288), exception c374 at 7ffe342dcba9
> ...
> --- Process 12736 exited with status 0xc374
>
Thanks for the report. I'll submit a patch to fix that.
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
On Sun, 16 Mar 2025 12:08:28 +0900
Takashi Yano
wrote:
> On Sat, 15 Mar 2025 19:38:20 -0600
> Jim Reisert AD1C via Cygwin wrote:
>
> > Recently, I seem to have LOCAL_APPDATA_FONTCONFIG_CACHE directories
> > popping up everywhere:
> >
> > ./DX4WIN/awd/R
Sorry, this is the building mistake in fontconfig-2.16.0-1.
Pease update to fontconfig-2.16.0-2.
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
On Fri, 14 Mar 2025 15:18:45 +0100
Corinna Vinschen wrote:
> On Mar 14 21:52, Takashi Yano via Cygwin wrote:
> > On Fri, 14 Mar 2025 13:19:28 +0100
> > Corinna Vinschen wrote:
> > > On Mar 14 20:35, Takashi Yano via Cygwin wrote:
> > > > On Fri, 14 Mar 2025 11:
On Fri, 14 Mar 2025 13:19:28 +0100
Corinna Vinschen wrote:
> On Mar 14 20:35, Takashi Yano via Cygwin wrote:
> > On Fri, 14 Mar 2025 11:01:25 +0100
> > Corinna Vinschen wrote:
> > > I don't think so. I was mulling in circles over this tonight
> > > (don'
On Fri, 14 Mar 2025 11:01:25 +0100
Corinna Vinschen wrote:
> On Mar 14 12:56, Takashi Yano via Cygwin wrote:
> > On Fri, 14 Mar 2025 08:12:36 +0900
> > Takashi Yano wrote:
> > > On Thu, 13 Mar 2025 23:46:49 +0100
> > > Corinna Vinschen wrote:
> > > &g
On Fri, 14 Mar 2025 08:18:41 +0900
Takashi Yano wrote:
> On Fri, 14 Mar 2025 08:12:36 +0900
> Takashi Yano wrote:
> > On Thu, 13 Mar 2025 23:46:49 +0100
> > Corinna Vinschen wrote:
> > > On Mar 13 17:30, Corinna Vinschen via Cygwin wrote:
> > > > On Mar
On Fri, 14 Mar 2025 08:12:36 +0900
Takashi Yano wrote:
> On Thu, 13 Mar 2025 23:46:49 +0100
> Corinna Vinschen wrote:
> > On Mar 13 17:30, Corinna Vinschen via Cygwin wrote:
> > > On Mar 13 21:31, Takashi Yano via Cygwin wrote:
> > > > What about following patch
On Fri, 14 Mar 2025 08:12:36 +0900
Takashi Yano wrote:
> On Thu, 13 Mar 2025 23:46:49 +0100
> Corinna Vinschen wrote:
> > On Mar 13 17:30, Corinna Vinschen via Cygwin wrote:
> > > On Mar 13 21:31, Takashi Yano via Cygwin wrote:
> > > > What about following patch
On Thu, 13 Mar 2025 23:46:49 +0100
Corinna Vinschen wrote:
> On Mar 13 17:30, Corinna Vinschen via Cygwin wrote:
> > On Mar 13 21:31, Takashi Yano via Cygwin wrote:
> > > What about following patch instead of your sigdelayed patch?
> > > [...]
> >
On Thu, 13 Mar 2025 20:42:52 +0900
Takashi Yano wrote:
> Hi Corinna,
>
> On Thu, 13 Mar 2025 10:40:48 +0100
> Christian Franke wrote:
> > Corinna Vinschen via Cygwin wrote:
> > > On Mar 12 17:06, Corinna Vinschen via Cygwin wrote:
> > >> On Mar 12 1
l. Apparently I haven't thought
> >> long enough about this.
> >>
> >> I have a patch for sigdelayed() in the loop, stay tuned.
> > Just pushed. Try cygwin-3.6.0-0.430.ga942476236b5 in a bit.
>
> Problem does no longer occur. Also tested with 'kill -INT PID && sleep
> 0.01' in a loop.
After the commit:
commit a942476236b5e39bf30c533d08df7392e326a4c6 (origin/master, origin/main,
origin/HEAD)
Author: Corinna Vinschen
Date: Wed Mar 12 17:17:31 2025 +0100
Cygwin: sigdelayed: pop return address from signal stack earlier
Christians test case: timersig.c no longer works even with my v3 patches.
I suspect it is because pop(), retaddr() are not working as intended in
call_signal_handler() with this commit.
Could you please have a look?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
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):
> &
arent process issues SIGSTOP
> SIGALRM SIGCONT ... sequences.
Thanks for the report, especially for the test case. I was able to
easily reproduce the issue. However, I haven't found the cause until
today. I spent 3 days investigating and discovered three bugs that
prevent the test case
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 Wed, 19 Feb 2025 17:22:53 +0100
ASSI wrote:
> Takashi Yano via Cygwin writes:
> > I think I have found the cause. It is an upstream bug of libtool.
> > The function check_executable() generated by ltmain.sh returns 1
> > for directory, but this is not correct behaviour,
Hi Achim,
On Wed, 19 Feb 2025 21:58:49 +0900
Takashi Yano wrote:
> On Wed, 19 Feb 2025 20:42:05 +0900
> Takashi Yano wrote:
> > On Wed, 19 Feb 2025 07:38:13 +0900
> > Takashi Yano wrote:
> > > On Tue, 18 Feb 2025 21:59:36 +0100
> > > Marco Atzeriwrote:
>
On Wed, 19 Feb 2025 20:42:05 +0900
Takashi Yano wrote:
> On Wed, 19 Feb 2025 07:38:13 +0900
> Takashi Yano wrote:
> > On Tue, 18 Feb 2025 21:59:36 +0100
> > Marco Atzeriwrote:
> > > On 18/02/2025 12:56, Takashi Yano via Cygwin wrote:
> > > > Hi Marco,
> &
On Wed, 19 Feb 2025 07:38:13 +0900
Takashi Yano wrote:
> On Tue, 18 Feb 2025 21:59:36 +0100
> Marco Atzeriwrote:
> > On 18/02/2025 12:56, Takashi Yano via Cygwin wrote:
> > > Hi Marco,
> > >
> > > On Mon, 17 Feb 2025 09:28:11 +0100
> > > Marco
, and if I
> compile the same sources against Cygwin and pipe it into a Cygwin
> program it works.
Do you mean the result is as expected with cygwin 3.5.7?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentat
ces against Cygwin and pipe it into a Cygwin
> program it works.
Do you mean the result is as expected 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
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
. 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
On Tue, 18 Feb 2025 21:59:36 +0100
Marco Atzeriwrote:
> On 18/02/2025 12:56, Takashi Yano via Cygwin wrote:
> > Hi Marco,
> >
> > On Mon, 17 Feb 2025 09:28:11 +0100
> > Marco Atzeri wrote:
> >> Hi Takashi,
> >>
> >> I think there is still
FAILED
> (gdbmtool02.at:20)
> 33: Initialization file FAILED
> (gdbmtool03.at:19)
> --
This is not a pipe problem, but just a path problem for gdbmtool.
Please try the patch attached.
--
Takashi Yano
--- origsrc/gdbm
Hi Marco,
On Wed, 29 Jan 2025 16:23:03 +0100
Marco Atzeri wrote:
> On 29/01/2025 16:02, Takashi Yano via Cygwin wrote:
> > Hi Achim,
> >
> > On Wed, 29 Jan 2025 13:30:16 +0100
> > ASSI wrote:
> >> Marco Atzeri via Cygwin writes:
> >>> It wo
w. Probably, removing ~/.viminfo affects somehow?
However, I think /usr/bin/vi does not read .viminfo, does it?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info
was introduced between 2.x.x and 3.7.x.
Any idea?
If you need more information from pty side, please let me know.
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubs
gt; 3.6.0-0.338.ge0bc8172712(2 runs)
>
> 3.6.0-0.343.gbf94b87f54de(2 runs)
Thanks for testing!
> If you have a release candidate, I can run more thorough tests, but it
> should be stable then for 2 days.
We have no plan for release candidate, but will release 3.5.6
in a few da
On Wed, 22 Jan 2025 10:42:39 -0800 (PST)
Jeremy Drake wrote:
> On Tue, 14 Jan 2025, Takashi Yano via Cygwin wrote:
>
> > Personally, I personally prefer releasing 3.5.6 ASAP.
>
> Is this the plan, now that the hangs seem to be resolved? (Maybe after
> additional confirmati
dditional patches.
Please test cygwin test version 3.6.0-0.337.ga880e0dffbe6 or later,
which will be available soon. I hope the hang no longer occurs.
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:
action, use allow-test-packages like:
- name: Install Cygwin
uses: egor-tensin/setup-cygwin@v4
with:
packages: cmake gcc-g++
install-dir: C:\\tools\\cygwin64
allow-test-packages: true # <=
In other case, what kind of CI are you using?
--
Taka
Hi Michael,
On Tue, 14 Jan 2025 09:17:23 +0900
Takashi Yano wrote:
> On Mon, 13 Jan 2025 16:10:17 -0800 (PST)
> Jeremy Drake wrote:
> > On Tue, 14 Jan 2025, Takashi Yano via Cygwin wrote:
> >
> > > Hi Michael,
> > >
> > > Personally, I person
On Mon, 13 Jan 2025 16:10:17 -0800 (PST)
Jeremy Drake wrote:
> On Tue, 14 Jan 2025, Takashi Yano via Cygwin wrote:
>
> > Hi Michael,
> >
> > Personally, I personally prefer releasing 3.5.6 ASAP. However, we
> > are not sure that we have already fixed all t
On Tue, 14 Jan 2025 08:57:36 +0900
Takashi Yano wrote:
> Hi Michael,
>
> On Fri, 10 Jan 2025 08:48:00 +0100
> Michael Soegtrop wrote:
> > sending again, since this did not appear in the archives ...
> >
> > Dear Cygwin Team,
> >
> > I wanted to discuss
have already fixed all the major problems in
3.5.5.
Can you please test latest cygwin 3.6.0 (TEST) whether the your
CI issue still happens?
If the CI problem still happen even with 3.6.0 (TEST), we should
consider rolling back to 3.5.4. Otherwise, releasing 3.5.6 is
the proper way to go, I think.
--
On Tue, 31 Dec 2024 18:59:03 +0100
Marco Atzeri wrote:
> On 31/12/2024 17:28, Marco Atzeri wrote:
> > On 31/12/2024 14:36, Takashi Yano via Cygwin wrote:
> >> On Wed, 18 Dec 2024 09:54:24 +0100
> >> Marco Atzeri wrote:
> >>> Version 1.3.45-1 of
> >
>
tions or comments, please send them to the
> cygwin mailing list at: cygwin (at) cygwin (dot) com .
With GraphicsMagick-1.3.45-1, octave cannot start.
The error:
Procedure entry point heif_deinit could not be located in the
tye dynamic link libraryc:\cygwin64\bin\cygGraphicsMagick-3.dll
so
1 - 100 of 997 matches
Mail list logo
