public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: "M?min A." <muminaydin06@gmail.com>
Subject: Re: Memory Barriers at pthread using CYGWIN
Date: Sat, 10 Jun 2023 13:08:04 +0900 (JST)	[thread overview]
Message-ID: <1503743851.9556.1686370084334@aps7mgn-06> (raw)
In-Reply-To: <CAPxKPA6zdV5UUdwcnhk9Sw159UQfVSsMjoiC4Sx3w-ojzw9Biw@mail.gmail.com>

"M?min A." wrote:
> //windows cmd line
> C:\cygwin64\home\maydin\test>cygcheck ./main.exe
> C:\cygwin64\home\maydin\test\main.exe
>   C:\cygwin64\bin\cygwin1.dll
>     C:\WINDOWS\system32\KERNEL32.dll
>       C:\WINDOWS\system32\ntdll.dll
>       C:\WINDOWS\system32\KERNELBASE.dll
> 
> C:\cygwin64\home\maydin\test>ldd ./main.exe
>         ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffa92350000)
>         KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL
> (0x7ffa90570000)
>         KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll
> (0x7ffa8ffb0000)
>         cygwin1.dll => /usr/bin/cygwin1.dll (0x7ffa27960000)

Looks OK.

> //When cygwin terminal closed and cmd line command. Join throw fails.
> C:\cygwin64\home\maydin\test>main.exe
> Failed to join the thread t1.
> Failed to join the thread t2.
> r1 = 1, r2 = 1
> 
> //when cygwin terminal opened. The test is passed.
> C:\cygwin64\home\maydin\test>main.exe
> r1 = 1, r2 = 1
> 
> 
> I think Cygwin terminal should be always open in order to execute a file in
> windows. Am I right ?

It should not be. Weird enough.

Could you please provide a strace log file such as:
strace -o faild.log ./main.exe
?

--
Takashi Yano <takashi.yano@nifty.ne.jp>

  parent reply	other threads:[~2023-06-10  4:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPxKPA6bRfF19pXrYT04TqbxettyYf=ypgfdySysqAJyB9BfxA@mail.gmail.com>
     [not found] ` <CAPxKPA48sKPqwGc-jU7UQvQhsbT0N6A9LJXCAZeaa1rjeRtuNg@mail.gmail.com>
     [not found]   ` <96718c68-af84-45a5-9332-337ec4b2f04a@email.android.com>
2023-06-09 12:25     ` Takashi Yano
     [not found] ` <64831a27.170a0220.1f805.81bfSMTPIN_ADDED_BROKEN@mx.google.com>
2023-06-10  4:08   ` Takashi Yano [this message]
2023-06-20 12:53     ` Takashi Yano
2023-06-22 10:19       ` Takashi Yano
2023-06-22 11:48         ` Corinna Vinschen
2023-06-22 23:49           ` Takashi Yano
2023-06-08 14:29 Mümin A.
2023-06-08 14:37 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-06-08 22:58   ` Mümin A.
2023-06-09  0:22     ` Takashi Yano
2023-06-09  1:44 ` Duncan Roe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1503743851.9556.1686370084334@aps7mgn-06 \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=muminaydin06@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).