Re: [Bug check/report] UnDocumented call to ntdll.dll!NtAssignProcessToJobObject in msys2.0.dll / cygwin - included in mingit/Git for Windows

Hi Veronica & Cygwin list (please keep me Cc:ed, I am not subscribed), On Sat, 11 Jan 2025, Veronica Giaudrone wrote: > I'm part of the Visual Studio team at Microsoft which includes > mingit/Git for Windows in our product for Git tooling integration (I'm > copying a couple of folks from my team

[Bug check/report] UnDocumented call to ntdll.dll!NtAssignProcessToJobObject in msys2.0.dll / cygwin - included in mingit/Git for Windows

Hello Cygwin list, I'm part of the Visual Studio team at Microsoft which includes mingit/Git for Windows in our product for Git tooling integration (I'm copying a couple of folks from my team in this email too). One of our API scanning tools has identified msys2.0.dll calling undocumented Window

top, who, w no longer report users

Following an update which included the latest versions of mintty (3.7.4-1) and openssh (v. 9.8p1-1), I noticed that tools like top, who, and w no longer report either local or remote (ssh'd in) users. When running X, these tool do report pty* users (in an xterm). Cygwin is version 3.

jq bug report: jq errors trigger assertion errors rather than being handled

Hi, I'm seeing consistent behaviour when running `jq` on Cygwin, where commands that should trigger jq to produce an error message instead cause it to assert and die. Simple test case: run `jq -n 'error("oh no!")'`, which should raise a jq error with the text "oh no!". Output on Cygwin: $ j

Re: MULTIPLE VULNERABILITY REPORT: Multiple DLL Hijacking Vulnerability in CygWin setup-x86_64.exe

On 06/02/2024 23:10, Kaz Kylheku via Cygwin wrote: On 2024-02-04 21:22, Suman Chakraborty via Cygwin wrote: 1. Executive Summary: The vulnerability pertains to not finding the profapi.dll, CFGMGR32.dll, edputil.dll, urlmon.dll, SspiCli.dll, Wldp.dll, MPR.dll, ServicingCommon.dll, TextShaping.d

Re: MULTIPLE VULNERABILITY REPORT: Multiple DLL Hijacking Vulnerability in CygWin setup-x86_64.exe

On 2024-02-06 15:10, Kaz Kylheku via Cygwin wrote: On 2024-02-04 21:22, Suman Chakraborty via Cygwin wrote: 1. Executive Summary: The vulnerability pertains to not finding the profapi.dll, CFGMGR32.dll, edputil.dll, urlmon.dll, SspiCli.dll, Wldp.dll, MPR.dll, ServicingCommon.dll, TextShaping.d

Re: MULTIPLE VULNERABILITY REPORT: Multiple DLL Hijacking Vulnerability in CygWin setup-x86_64.exe

On 2024-02-04 21:22, Suman Chakraborty via Cygwin wrote: > 1. Executive Summary: > > The vulnerability pertains to not finding > the profapi.dll, CFGMGR32.dll, edputil.dll, urlmon.dll, SspiCli.dll, > Wldp.dll, MPR.dll, ServicingCommon.dll, TextShaping.dll, CRYPTBASE.DLL, > PROPSYS.dll and insecu

MULTIPLE VULNERABILITY REPORT: Multiple DLL Hijacking Vulnerability in CygWin setup-x86_64.exe

Hey Cygwin Team, I hope this email finds you well. As an independent security researcher, I often explore open-source projects to identify and report potential security vulnerabilities. During my recent exploration of Cygwin, I came across a critical vulnerability in setup-x86_64.exe <ht

VULNERABILITY REPORT: DLL Hijacking Vulnerability in CygWin setup-x86_64.exe

Hey Cygwin Team, I hope this email finds you well. As an independent security researcher, I often explore open-source projects to identify and report potential security vulnerabilities. During my recent exploration of Cygwin, I came across a critical vulnerability in setup-x86_64.exe <ht

VULNERABILITY REPORT: DLL Hijacking Vulnerability in CygWin setup-x86_64.exe

Hey Cygwin Team, I hope this email finds you well. As an independent security researcher, I often explore open-source projects to identify and report potential security vulnerabilities. During my recent exploration of Cygwin, I came across a critical vulnerability in setup-x86_64.exe <ht

VULNERABILITY REPORT: DLL Hijacking Vulnerability in CygWin setup-x86_64.exe

Hey Cygwin Team, I hope this email finds you well. As an independent security researcher, I often explore open-source projects to identify and report potential security vulnerabilities. During my recent exploration of Cygwin, I came across a critical vulnerability in setup-x86_64.exe <ht

Re: bug report

On 2023-09-06 16:20, Asad Ali via Cygwin wrote: On Fri, Dec 30, 2022 at 5:46 AM Asad Ali wrote: I'm a penetration tester and bug bounty hunter. I have found a potential vulnerability in the site. Please review the report below. Is there any update on this ? I'm hoping to receive a

Re: bug report

t; vulnerability in the site. Please review the report below. > > > > Vulnerability: Broken Authentication & Session Management > We have observed that when we change "password" from one browser in place > of session expiration from another browser it just updates the pass

Re: error report

>bin/iperf3.exe -c 192.168.1.233 -P 1 -i 1 -p 5201 -f g -t 10      0 [main] >iperf3 17636 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.  >Please report this problem tothe public mailing list cygwin@cygwin.com https://cygwin.com/faq.html#faq.using.fixing

error report

bin/iperf3.exe -c 192.168.1.233 -P 1 -i 1 -p 5201 -f g -t 10      0 [main] iperf3 17636 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.  Please report this problem tothe public mailing list cygwin@cygwin.com -- Problem reports: https://cygwin.com/problems.htm

Re: Problem Report

>b_gettext 9004 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. >Please report this problem to >the public mailing list cygwin@cygwin.com<mailto:cygwin@cygwin.com> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings -- Problem reports:

Problem Report

b_gettext 9004 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com<mailto:cygwin@cygwin.com> -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Do

Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

(which was fixed over a decade ago). > On Sat, Apr 2, 2022 at 8:28 AM James wrote: >> Hi there, >> >> >> I just got that error message, asking me to report it here. >> >> 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute >&g

Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

On 2022-04-02 01:37, Backwoods BC wrote: https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings I've only been on this list a few months, but I've seen these "find_fast_cwd" questions about twice a month so far. Might I suggest that replacing the "Plea

Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

On 4/2/2022 3:37 AM, Backwoods BC wrote: https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings I've only been on this list a few months, but I've seen these "find_fast_cwd" questions about twice a month so far. Might I suggest that replacing the "Plea

Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings I've only been on this list a few months, but I've seen these "find_fast_cwd" questions about twice a month so far. Might I suggest that replacing the "Please report this problem to the public ma

Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

Voila, thanks! Have a nice weekend ya'all On Sat, Apr 2, 2022 at 8:31 AM wrote: > >Hi there, > > > >I just got that error message, asking me to report it here. > > > 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute > FAST_CWD > &

Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

st got that error message, asking me to report it here. > > 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute > FAST_CWD pointer. Please report this problem to the public mailing list > cygwin@cygwin.com > > Not sure if it's interesting? > > > Ki

Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

>Hi there, >I just got that error message, asking me to report it here. > 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD >pointer. Please report this problem to the public mailing list >cygwin@cygwin.com >Not sure if it's interest

1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com

Hi there, I just got that error message, asking me to report it here. 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com Not sure if it's interesting? Kind regards, James -

Re: Bug report for cygwin X server (or xterm)

Am 10.03.2022 um 10:37 schrieb n952162: xterm*VT100.Translations only when mouse is over the window with focus Discovered with click-to-focus, in FVWM In particular, I'm talking about the function keys. In this case, these are NOT mapped in fvwm, but in xterm. Pressing a function key, like F1,

Bug report for cygwin X server (or xterm)

xterm*VT100.Translations only when mouse is over the window with focus Discovered with click-to-focus, in FVWM In particular, I'm talking about the function keys. In this case, these are NOT mapped in fvwm, but in xterm. Pressing a function key, like F1, always writes to the window with focus,

Re: Bug Report

On Tue, Feb 8, 2022 at 3:02 PM julie77793 wrote: Cygwin doesn't create an environment variable in bash to indicate that the > platform is Cygwin under Windows. > FYI, as a point of decorum: The subject line of this thread is rather undiplomatic. (Bug usually means "software should do X but fails

Re: Bug Report

On 2/8/22 2:01 PM, julie77...@gmail.com wrote: Cygwin doesn't create an environment variable in bash to indicate that the platform is Cygwin under Windows. This causes compatibility problems when running various tools. Most of my issues have been with Python tools running Windows Python. I have

RE: [EXTERNAL] Bug Report

> Please add some way of identifying that programs are running under Cygwin. Have you tried to use the "uname" command for the identification purposes? $ uname CYGWIN_NT-6.1 $ uname CYGWIN_NT-10.0 Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: https://cygwin.com/problems.h

Bug Report

Cygwin doesn't create an environment variable in bash to indicate that the platform is Cygwin under Windows. This causes compatibility problems when running various tools. Most of my issues have been with Python tools running Windows Python. I have been addressing this issue by grepping PATH for

Re: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem

>0 [main] chmod 10200 find_fast_cwd: WARNING: Couldn't compute FAST_CWD >pointer. Please report this problem to >the public mailing list cygwin@cygwin.com https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings -- Problem reports: https://cygwin.com/pro

WARNING: Couldn't compute FAST_CWD pointer. Please report this problem

0 [main] chmod 10200 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:

Delivery report

Hello, this is the mail server on server.hiteutomotive.com. I am sending you this message to inform you on the delivery status of a message you previously sent. Immediately below you will find a list of the affected recipients; also attached is a Delivery Status Notification (DSN) report in

Delivery report

Hello, this is the mail server on mta0.connevate.com. I am sending you this message to inform you on the delivery status of a message you previously sent. Immediately below you will find a list of the affected recipients; also attached is a Delivery Status Notification (DSN) report in standard

Delivery report

Hello, this is the mail server on nodset3.westsarproperty.com. I am sending you this message to inform you on the delivery status of a message you previously sent. Immediately below you will find a list of the affected recipients; also attached is a Delivery Status Notification (DSN) report in

Re: CNTLM: INSTALLATION MESSAGE TO REPORT

>Hi Team, >Getting error as below on CNTLM setup as per documentation of on boardking: >"C:\Program Files (x86)\Cntlm>cntlm -v > 4925 [main] cntlm 13644 find_fast_cwd: WARNING: Couldn't compute FAST_CWD > pointer. Please report this problem to >the public

CNTLM: INSTALLATION MESSAGE TO REPORT

Hi Team, Getting error as below on CNTLM setup as per documentation of on boardking: "C:\Program Files (x86)\Cntlm>cntlm -v 4925 [main] cntlm 13644 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygw

Re: Error Report

On 27.05.2021 01:50, Jaime Arseneault via Cygwin wrote: Hi, I got an error and it says in the error to report it to this email address. This happened while I was using WiiBaFu to patch Rhythm Heaven Fever with custom textures. Thanks Hi Jaime, the warning is explained at https://cygwin.com

Error Report

Hi, I got an error and it says in the error to report it to this email address. This happened while I was using WiiBaFu to patch Rhythm Heaven Fever with custom textures. Thanks (Wed May 26 19:45:31 2021) Wii Backup Fusion 1.1 started. wit: Wiimms ISO Tool v2.00b r2855 cygwin - Dirk Clemens

Re: Error Report

>1 [main] rsync 3280 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. >Please report this problem to >the public mailing list cygwin@cygwin.com >sending incremental file list >M. Wortmann Elektrotechnik GmbH & Co. KG >Horst 13 >48301 Nottuln >02502/

Error Report

1 [main] rsync 3280 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com sending incremental file list -- M. Wortmann Elektrotechnik GmbH & Co. KG Horst 13 48301 Nottuln 02502/2243821 i...@wortmann-e

Re: BUG Report (SOLVED): rlwrap + cygwin (dll) + Windows 10

Alberto Moral Beneitez escribió: Hi, everybody First of all, this is my first bug report, so I don't know if I am doing correctly... I don't know if one must be registered to summit this type of repport. And be patient with my English. The problem is that rlwrap has stopped work

Re: BUG Report: rlwrap + cygwin (dll) + Windows 10

On 12/13/2020 9:41 AM, Marco Atzeri via Cygwin wrote: On 13.12.2020 13:43, Takashi Yano via Cygwin wrote: On Sat, 12 Dec 2020 20:05:05 + (UTC) Alberto Moral Beneitez via Cygwin  wrote: Hi, everybody Please try: env CYGWIN=disable_pcon rlwrap cmd Also, you can use alias like: alias rlwra

Re: BUG Report: rlwrap + cygwin (dll) + Windows 10

On 13.12.2020 13:43, Takashi Yano via Cygwin wrote: On Sat, 12 Dec 2020 20:05:05 + (UTC) Alberto Moral Beneitez via Cygwin wrote: Hi, everybody Please try: env CYGWIN=disable_pcon rlwrap cmd Also, you can use alias like: alias rlwrap="env CYGWIN=disable_pcon rlwrap" I had the impressi

Re: BUG Report: rlwrap + cygwin (dll) + Windows 10

On Sat, 12 Dec 2020 20:05:05 + (UTC) Alberto Moral Beneitez via Cygwin wrote: > Hi, everybody > First of all, this is my first bug report, so I don't know if I am doing > correctly... I don't know if one must be registered to summit this type of > repport. And be p

BUG Report: rlwrap + cygwin (dll) + Windows 10

Hi, everybody First of all, this is my first bug report, so I don't know if I am doing correctly... I don't know if one must be registered to summit this type of repport. And be patient with my English. The problem is that rlwrap has stopped working in combination with: - Win

bug report: tty/termios flags weirdness

After thrashing with my own bugs for a while, I think I've found a minor bug in Cygwin's tty/termios handling-- seen in 3.1.7 on Windows 10 20H2.  Among other things, this causes tmux to fail on non-pty sessions. STC: Start Cygwin in conhost or Windows Terminal. Execute 'stty -isig' You will pr

Re: Please report this problem to

On Monday, September 7, 2020, 04:04:58 PM EDT, alberto parra via Cygwin wrote: > Eso es rodo ese  es el titulo ¡Pero no informaste del problema! Prueba esto: https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings This is the most common error that asks you to report h

Please report this problem to

Eso es rodo ese es el titulo -- 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

Delivery report

Hello, this is the mail server on qu.quackerservapi.live. I am sending you this message to inform you on the delivery status of a message you previously sent. Immediately below you will find a list of the affected recipients; also attached is a Delivery Status Notification (DSN) report in

Delivery report

Hello, this is the mail server on qu.quackerservapi.live. I am sending you this message to inform you on the delivery status of a message you previously sent. Immediately below you will find a list of the affected recipients; also attached is a Delivery Status Notification (DSN) report in

Re: bug report: shell expansion in argv[] processing sensitive to LANG, e.g. "ls: cannot access '*.pdf': No such file or directory", but works okay in bash

On 2020/04/02 06:43, Andrey Repin wrote: That's not what actually happens. ...\Documents> ls -1 *.pdf 21927-ticket.pdf 'Stars! Universe Map.pdf' --- Thank you for your update. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentatio

Re: bug report: shell expansion in argv[] processing sensitive to LANG, e.g. "ls: cannot access '*.pdf': No such file or directory", but works okay in bash

Greetings, L A Walsh! > On 2020/03/24 00:18, Jay Libove via Cygwin wrote: >> Problem: >> Under certain circumstances (see Steps to Reproduce, below) Cygwin programs' >> built-in argv[] globbing will produce unexpected: >> "{programName}: cannot access '{glob pattern}: No such file or directory" >

Re: bug report: shell expansion in argv[] processing sensitive to LANG, e.g. "ls: cannot access '*.pdf': No such file or directory", but works okay in bash

On 2020/03/24 00:18, Jay Libove via Cygwin wrote: Problem: Under certain circumstances (see Steps to Reproduce, below) Cygwin programs' built-in argv[] globbing will produce unexpected: "{programName}: cannot access '{glob pattern}: No such file or directory" e.g. "ls: cannot access '*.pdf': No

Re: bug report: shell expansion in argv[] processing sensitive to LANG, e.g. "ls: cannot access '*.pdf': No such file or directory", but works okay in bash

Maybe it can simply be fixed by changing the order of setting up locale stuff and applying the expansion in cygwin? (I would look into the code if I had a clue where to find the respective things.) I would guess dcrt0.cc, the Cygwin DLL runtime initialization. ..mark -- Problem reports:

Re: bug report: shell expansion in argv[] processing sensitive to LANG, e.g. "ls: cannot access '*.pdf': No such file or directory", but works okay in bash

Am 24.03.2020 um 08:18 schrieb Jay Libove via Cygwin: Hi Cygwin team, Here is a consolidated bug report based on the discussion in recent days which I'd started under the subject " shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory&q

bug report: shell expansion in argv[] processing sensitive to LANG, e.g. "ls: cannot access '*.pdf': No such file or directory", but works okay in bash

Hi Cygwin team, Here is a consolidated bug report based on the discussion in recent days which I'd started under the subject " shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash "

Re: 1 [main] bash 3048 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to

>1 [main] bash 3048 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointe= >r. Please report this problem to the public mailing list cygwin@cygwin.com= ><mailto:cygwin@cygwin.com> >Cygwin wurde neu installiert. https://cygwin.com/faq.html#faq.using.fixing-find_fast_c

1 [main] bash 3048 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to

1 [main] bash 3048 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com<mailto:cygwin@cygwin.com> Cygwin wurde neu installiert. -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: cntlm error report 10904

>Hello, >I am using CNTLM on my Bosch machine and it has been working fine until a f= >ew days ago. >Now I get this error >1 [main] cntlm 10904 find_fast_cwd: WARNING: Couldn't compute FAST_CWD poin= >ter. Please report this problem to >the public mailing list cygwi

cntlm error report 10904

Hello, I am using CNTLM on my Bosch machine and it has been working fine until a few days ago. Now I get this error 1 [main] cntlm 10904 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com<mailto:cygwin@cy

Re: report security problem

at least be > triggered by git(https://git-scm.com/download/win). Just create program.exe > and put it to C:\problem.exe, git-bash.exe creates process mintty.exe, > mintty.exe loads msys-2.0.dll which contains the vulnerable code and > program.exe get executed(I will inform git too).

report security problem

fhandler_console::create_invisible_console_workaround in newlib-cygwin\winsup\cygwin\fhandler_console.cc will call CreateProcessW to create a new hidden process. According to CreateProcessW documention: The lpApplicationName parameter can be NULL. In that case, the module name must be the first wh

Re: Fwd: Report

>1 [main] cntlm 14392 find_fast_cwd: WARNING: Couldn't compute FAST_CWD=20 >pointer. Please report this problem to >the public mailing list cygwin@cygwin.com >cygwin warning: > MS-DOS style path detected: C:\Program Files (x86)\Cntlm\cntlm.ini > Preferred POSI

Fwd: Report

1 [main] cntlm 14392 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com cygwin warning: MS-DOS style path detected: C:\Program Files (x86)\Cntlm\cntlm.ini Preferred POSIX equivalent is: /Cntlm/cntl

Re: Bug report: Killing a native process may not actually kill it

On Thu, 29 Aug 2019, 02:38 Steven Penny, wrote: > On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote: > > My original post contained a link to a patch allowing for Cygwin to > > correctly terminate native Windows processes. I understand it is not > the > > position of the Cygwin project to

Re: Bug report: Killing a native process may not actually kill it

On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote: My original post contained a link to a patch allowing for Cygwin to correctly terminate native Windows processes. I understand it is not the position of the Cygwin project to deal with situation, so I think we can just let it drop. I w

Re: Bug report: Killing a native process may not actually kill it

--On Wednesday, August 28, 2019 2:33 PM -0700 Kaz Kylheku <920-082-4...@kylheku.com> wrote: Cygwin can't introduce Unix-like shutdown mechanisms (like the handling a non-fatal signal) into non-Cygwin processes which have no concept of that. It makes no sense. My original post contained a link

Re: Bug report: Killing a native process may not actually kill it

On 2019-08-28 08:59, Quanah Gibson-Mount wrote: --On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen wrote: Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only works reliably with Cygwin processes. There's $ /bin/kill -f to call the Win32 function TerminateProce

Re: Bug report: Killing a native process may not actually kill it

On Aug 28 08:59, Quanah Gibson-Mount wrote: > > > --On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen > wrote: > > > Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only > > works reliably with Cygwin processes. There's > > > > $ /bin/kill -f > > > > to call the

Re: Bug report: Killing a native process may not actually kill it

--On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen wrote: Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only works reliably with Cygwin processes. There's $ /bin/kill -f to call the Win32 function TerminateProcess(pid) on a non-Cygwin process or an unresp

Re: Bug report: Killing a native process may not actually kill it

On Aug 28 08:18, Quanah Gibson-Mount wrote: > > > --On Thursday, July 25, 2019 11:32 AM -0700 Quanah Gibson-Mount > wrote: > > > As found and reported to the MSYS team back in 2006 by Howard Chu, if a > > native process is spawned, control-C, the kill command, etc, may not > > actually kill the

Re: Bug report: Killing a native process may not actually kill it

--On Thursday, July 25, 2019 11:32 AM -0700 Quanah Gibson-Mount wrote: As found and reported to the MSYS team back in 2006 by Howard Chu, if a native process is spawned, control-C, the kill command, etc, may not actually kill the process. Details are here: I haven't seen a reply to this

openldap on Cygwin (was: Bug report: Killing a native process may not actually kill it)

Quanah Gibson-Mount writes: […] Sorry for wedging in sideways, but I've looked into building a more up-to-date openldap and there's missing detection / configuration for Cygwin. Specifically, there's code trying to use robust POSIX mutexes, which Cygwin doesn't have. As there is no configure opt

Bug report: Killing a native process may not actually kill it

As found and reported to the MSYS team back in 2006 by Howard Chu, if a native process is spawned, control-C, the kill command, etc, may not actually kill the process. Details are here: as well as here:

Re: Bug report. Clang sqrtl(-1) causes access violation

On May 10 14:57, Agner Fog wrote: > Bug description: > > The sqrtl function under Clang causes an access violation when the argument > is negative. > > This error occurs only under Cygwin. > > This error occurs only with the sqrtl function, not with sqrt or sqrtf > > Attached: > > sqrt.cpp: pr

Re: Bug report. Clang sqrtl(-1) causes access violation

Agner Fog, on Friday, May 10, 2019 04:55 PM, wrote... >$ uname -a >CYGWIN_NT-10.0 DESKTOP-08PNUTF 3.0.6(0.338/5/3) 2019-04-06 16:18 x86_64 >Cygwin > > >$ clang --version >clang version 5.0.1 (tags/RELEASE_501/final) >Target: x86_64-unknown-windows-cygnus >Thread model: posix >InstalledDir: /usr/

Re: Bug report. Clang sqrtl(-1) causes access violation

$ uname -a CYGWIN_NT-10.0 DESKTOP-08PNUTF 3.0.6(0.338/5/3) 2019-04-06 16:18 x86_64 Cygwin $ clang --version clang version 5.0.1 (tags/RELEASE_501/final) Target: x86_64-unknown-windows-cygnus Thread model: posix InstalledDir: /usr/bin On 10/05/2019 21.54, Jose Isaias Cabrera wrote: Agner F

Re: Bug report. Clang sqrtl(-1) causes access violation

Agner Fog, on Friday, May 10, 2019 03:44 PM, wrote... > >On 10/05/2019 15.50, Jose Isaias Cabrera wrote: > >> It works for me. > >Now it turns out that all the long double math functions cause access >violations. > >If you can't reproduce the error, what can I do to trace it? > > >Exception: STAT

Re: Bug report. Clang sqrtl(-1) causes access violation

On 10/05/2019 15.50, Jose Isaias Cabrera wrote: It works for me. Now it turns out that all the long double math functions cause access violations. If you can't reproduce the error, what can I do to trace it? Exception: STATUS_ACCESS_VIOLATION at rip=00180173164 Sam Habiel wrote: Wow

Re: Bug report. Clang sqrtl(-1) causes access violation

Am 10.05.2019 um 15:38 schrieb Sam Habiel: > Wow I can't believe that The Agner Fog posted on the Cygwin mailing list! > > https://www.agner.org/ > > On Fri, May 10, 2019 at 8:58 AM Agner Fog wrote: >> >> Bug description: >> >> The sqrtl function under Clang causes an access violation when the >

Re: Bug report. Clang sqrtl(-1) causes access violation

Agner Fog, on Friday, May 10, 2019 08:57 AM, wrote... > >Bug description: > >The sqrtl function under Clang causes an access violation when the >argument is negative. > >This error occurs only under Cygwin. > >This error occurs only with the sqrtl function, not with sqrt or sqrtf > It works for me.

Re: Bug report. Clang sqrtl(-1) causes access violation

Wow I can't believe that The Agner Fog posted on the Cygwin mailing list! https://www.agner.org/ On Fri, May 10, 2019 at 8:58 AM Agner Fog wrote: > > Bug description: > > The sqrtl function under Clang causes an access violation when the > argument is negative. > > This error occurs only under C

Bug report. Clang sqrtl(-1) causes access violation

Bug description: The sqrtl function under Clang causes an access violation when the argument is negative. This error occurs only under Cygwin. This error occurs only with the sqrtl function, not with sqrt or sqrtf Attached: sqrt.cpp: program to reproduce the error. Compile clang sqrt.cpp an

Re: Report Holloworld Example

>Dear Sir , i am using Eclipse mit dem deo0 nano board und have a Problem >which i Report to your Company. >i aktuelly downloaded Cygwin new Vision 64bit (i am using 64 bit Window 10) >and under D:\altera13_0\quartus\bin64\cygwin but i have still Problem.do i >Need to download som

Report Holloworld Example

Dear Sir , i am using Eclipse mit dem deo0 nano board und have a Problem which i Report to your Company. i aktuelly downloaded Cygwin new Vision 64bit (i am using 64 bit Window 10) and under D:\altera13_0\quartus\bin64\cygwin but i have still Problem.do i Need to download something für bin file

Re: Report

adding the original sender as unlikely he is subscribed to this mailing list Am 28.03.2019 um 19:43 schrieb Björn Stabel: Had you pasted the message like a normal human being, you would have a reply by now since there's a bot for that. And an faq entry: https://cygwin.com/faq.html#faq.using.fix

Re: Report

Had you pasted the message like a normal human being, you would have a reply by now since there's a bot for that. And an faq entry: https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings And you could just throw the whole thing into google and it'll probably lead you to the faq entry

Report

Screen: https://ctrlv.cz/Kdic -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

Re: gost.dll required but missing after latest Cygwin update (was: Error report: could not load the shared library)

> 21-Mar-2019 13:42:16.408 error:2606A074:engine routines:ENGINE_by_id:no such > engine:crypto/engine/eng_list.c:334:id=gost > host: dst_lib_init: crypto failure > In the attachment you find the cygcheck report. > Here a post from another user that describes the same problem: > https://

Error report: could not load the shared library

attachment you find the cygcheck report. Here a post from another user that describes the same problem: https://www.mail-archive.com/search?l=cygwin@cygwin.com&q=subject:%22gost.dll+required+but+missing+after+latest+Cygwin+update%22&o=newest&f=1 thank you for fixing this or providin

Re: Make Error Report

#x27;t compute FAST_CWD >pointer. Please report this problem to >the public mailing list cygwin@cygwin.com >mkdir -p obj >make: mkdir: Command not found >Makefile:95: recipe for target `obj' failed >make: *** [obj] Error 127" >Looking forward to hearing from you!

Make Error Report

Hey, I was trying to run the "make" command when installing darknet through the conda prompt. Below is the error message "(NAME) C:\Users\ngingihy\test\test2\imagetool\labelImg\darknet>make 1 [main] make 23544 find_fast_cwd: WARNING: Couldn't compute FAST_CWD point

Re: report of 3 [main] make 17564 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.

>To Whom it may concern, >I am asked to report the problem below and I would like to look for a >solution. >I am using anaconda python 3.6 on my window 10 computer >i have this error when i input the command make >3 [main] make 17564 find_fast_cwd: WARNING: Couldn't co

report of 3 [main] make 17564 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.

To Whom it may concern, I am asked to report the problem below and I would like to look for a solution. I am using anaconda python 3.6 on my window 10 computer i have this error when i input the command make 3 [main] make 17564 find_fast_cwd: WARNING: Couldn't compute FAST_CWD po

Re: Couldn't compute FAST_CWD pointer. Please report this problem to

Sent: Tuesday, February 5, 2019 5:38 PM To: Sierk, Dietmar; cygwin@cygwin.com Subject: Re: Couldn't compute FAST_CWD pointer. Please report this problem to Greetings, Sierk, Dietmar! > 1 [main] sh 19920 find_fast_cwd: WARNING: Couldn't compute FAST_CWD > pointer. Please report this

Re: Couldn't compute FAST_CWD pointer. Please report this problem to

Greetings, Sierk, Dietmar! > 1 [main] sh 19920 find_fast_cwd: WARNING: Couldn't compute FAST_CWD > pointer. Please report this problem to > the public mailing list cygwin@cygwin.com This indicates that you are using a very old Cygwin installation. The issue leading to this war

Couldn't compute FAST_CWD pointer. Please report this problem to

1 [main] sh 19920 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com CES@Med startscript revision_12 (2017-08-23) 66605 [main] sh 34256 C:\ecad\cygwin\bin\sh.exe: *** fatal error - fork: can't reserve

Re: Report a Gale 2.01 problem

Am 19.12.2018 um 02:11 schrieb Shi-Chao Li: Dear Sir/Madam, Sorry to bother you with such an abrupt email. I am Li shichao from Jilin University, China, >> I write this mail to report a problem to you. When I run Gale-2_0_1 on my Windows 10, I got the following error message: 1

  1   2   3   4   5   6   >