Re: [PATCH] Fix poll/select signal socket as write ready on connect failure

On Jul 17 21:33, Marc Hoersken via Cygwin wrote: > Hi Corinna, > > Am 17.07.2020 um 21:21 schrieb Corinna Vinschen: > > I don't agree here. The sole purpose for connect_errorcode is to set > > SOL_SOCKET/SO_ERROR in case a caller requests FD_CONNECT and FD_CONNECT > > is available. After being s

Re: [PATCH] Fix poll/select signal socket as write ready on connect failure

Hi Corinna, Am 17.07.2020 um 21:21 schrieb Corinna Vinschen: I don't agree here. The sole purpose for connect_errorcode is to set SOL_SOCKET/SO_ERROR in case a caller requests FD_CONNECT and FD_CONNECT is available. After being set once, SOL_SOCKET/SO_ERROR should not be rewritten, given the d

Re: [PATCH] Fix poll/select signal socket as write ready on connect failure

p;= ~FD_CONNECT; + /* Since FD_CONNECT is only given once, we have to keep FD_CONNECT + for connection failed sockets to have consistent behaviour in +programs calling poll/select multiple times. Example test to +non-listening port: curl -v 127

Re: [PATCH] Fix poll/select signal socket as write ready on connect failure

ong &events, } else wsock_events->events |= FD_WRITE; - wsock_events->events &= ~FD_CONNECT; + /* Since FD_CONNECT is only given once, we have to keep FD_CONNECT +for connection failed sockets to have consistent behaviour in + pro

Re: [PATCH] Fix poll/select signal socket as write ready on connect failure

ike the code does not handle the fact that those events are > returned only once for a socket and if not acted upon by the calling program > may not be received again. This means poll and select are currently not > consistend about the socket still being writable after a connect failure. >

[PATCH] Fix poll/select signal socket as write ready on connect failure

and if not acted upon by the calling program may not be received again. This means poll and select are currently not consistend about the socket still being writable after a connect failure. The first call to poll or select would signal the socket as writable, but not any following call. The

Re: Cygwin-3.1.3: read(2) from /dev/consN returns unexpected EOF after select(2) and redirection

nal > side), the combination of select(2) (for read) and redirection > causes the next attempt of read(2) to return EOF [i.e., read(0, buf, > sz) = 0] even though the TTY is still alive. Because of this > behavior, the shell session unexpectedly closes because the shell >

Cygwin-3.1.3: read(2) from /dev/consN returns unexpected EOF after select(2) and redirection

Hi, this is another report related to Cygwin console. Description: In a noncanonical mode of console (where tty is /dev/consN), if there is some unprocessed inputs from the user side (i.e., terminal side), the combination of select(2) (for read) and redirection causes the next attempt of

RE: Cygwin installer does not select the packages specified by the -P option

> Brian Inglis writes: > > The OP's package list include sudo, which does not exist, diffutils > > and tar, which are part of base. Should the first not fail setup, and > > all be omitted for a retest? > > Well, I actually tested the very list the OP gave and it worked as intended > (minus the una

Re: Cygwin installer does not select the packages specified by the -P option

Brian Inglis writes: > The OP's package list include sudo, which does not exist, diffutils and tar, > which are part of base. Should the first not fail setup, and all be omitted > for > a retest? Well, I actually tested the very list the OP gave and it worked as intended (minus the unavilable pac

Re: Cygwin installer does not select the packages specified by the -P option

On 2019-08-07 12:42, Achim Gratz wrote: > KAVALAGIOS Panagiotis (EEAS-EXT) writes: >> I have tried the -A option, the -B option as single user to no >> avail. There is no antivirus running. Well, there is in general in our >> PCs, but no installed on my test machine. I have also tried another >> mi

Re: Cygwin installer does not select the packages specified by the -P option

KAVALAGIOS Panagiotis (EEAS-EXT) writes: > I have tried the -A option, the -B option as single user to no > avail. There is no antivirus running. Well, there is in general in our > PCs, but no installed on my test machine. I have also tried another > mirror to re-download the packages in a local re

RE: Cygwin installer does not select the packages specified by the -P option

>You might want to go down one directory level and try again, even though >I don't see at the moment how that would be involved. Also, maybe check >the permissions / ACL on the files in the repo, which may be too >restrictive depending on how you downloaded them. You might also try to >run the in

Re: Cygwin installer does not select the packages specified by the -P option

KAVALAGIOS Panagiotis (EEAS-EXT) writes: > I have also switched the order of the mentioned options to no avail. Hmm. I tried that again today and it worked correctly regardless of the order of options. Funky… :-( > I am including the "setup.log.full" with --verbose option for further > investi

Re: Cygwin installer does not select the packages specified by the -P option

m,wget,xinit,xlaunch,xorg-server,xorg-server-common,xorg-server-xorg,xorg-x11-fonts-dpi100,xorg-x11-fonts-dpi75,xorg-x11-fonts-Type1,xorg-x11-fonts-misc,xterm,zip >> >> There is no issue if I select manually the packages. They are >> installed just fine from the local repositor

Re: Cygwin installer does not select the packages specified by the -P option

,unzip,vim,wget,xinit,xlaunch,xorg-server,xorg-server-common,xorg-server-xorg,xorg-x11-fonts-dpi100,xorg-x11-fonts-dpi75,xorg-x11-fonts-Type1,xorg-x11-fonts-misc,xterm,zip There is no issue if I select manually the packages. They are installed just fine from the local repository. The problem is

RE: Cygwin installer does not select the packages specified by the -P option

...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of KAVALAGIOS Panagiotis (EEAS-EXT) Sent: Monday, July 29, 2019 12:14 PM To: 'cygwin@cygwin.com' Subject: Cygwin installer does not select the packages specified by the -P option Dear all, I am trying to prepare an offline insta

Cygwin installer does not select the packages specified by the -P option

,xorg-server-xorg,xorg-x11-fonts-dpi100,xorg-x11-fonts-dpi75,xorg-x11-fonts-Type1,xorg-x11-fonts-misc,xterm,zip There is no issue if I select manually the packages. They are installed just fine from the local repository. The problem is that they are not selected at all when the above command is

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 2018-03-23 10:59, Ken Brown wrote: > On 3/23/2018 12:42 PM, Achim Gratz wrote: >> Ken Brown writes: I think there's no actual dependency of libfontconfig-common on xmlcatalog, but we lack a triggering mechanism to say "run this script when this other package is installed" >>> >>>

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 3/23/2018 12:42 PM, Achim Gratz wrote: Ken Brown writes: I think there's no actual dependency of libfontconfig-common on xmlcatalog, but we lack a triggering mechanism to say "run this script when this other package is installed" /etc/postinstall/fontconfig_dtd.sh could check whether /etc/p

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

Ken Brown writes: >> I think there's no actual dependency of libfontconfig-common on >> xmlcatalog, but we lack a triggering mechanism to say "run this >> script when this other package is installed" > > /etc/postinstall/fontconfig_dtd.sh could check whether > /etc/postinstall/libxml2.sh exists. I

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 3/7/2018 3:15 PM, Jon Turney wrote: Yeah, this looks like an ordering problem between libxml2 and libfontconfig-common. $ cat /etc/postinstall/fontconfig_dtd.sh if [ -x /usr/bin/xmlcatalog ] ; then     /usr/bin/xmlcatalog --noout --add "system" "fonts.dtd" /usr/share/xml/fontconfig/fonts.d

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 07/03/2018 17:22, Robert Cohen wrote: I did get one postinstall script error: Package: _/libfontconfig-common fontconfig_dtd.sh exit code 2 Here's the related error from setup.log.full, along with info on the command that ran just before that one: 2018/03/06 17:57:14 running: C:\c

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

>From: Jon Turney >Sent: Wednesday, March 7, 2018 07:08 >To: The Cygwin Mailing List >Cc: Robert Cohen >Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded >packages when installing from local directory ... > >This looks like a problem wit

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

you? [...] Thanks for the fixes. I tested setup-2.889-12-g1cf567.x86_64.exe, and after selecting category view on the installer and changing "Default" to "Install" at the top of the list, it appeared to select both the pre-selected and my own selected packages for installatio

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

>From: Jon Turney >Sent: Tuesday, March 6, 2018 17:13 >To: The Cygwin Mailing List >Cc: Robert Cohen >Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded >packages when installing from local directory >  ... > >I built an updated set

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

under Category view says "No packages found<->Default". Continuing the install only installs the packages preselected by setup. Thanks for reporting this problem. Details: To install a fresh version of Cygwin, I usually do this: Run setup-x86_64.exe using "Download Withou

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 3/3/2018 11:01 PM, Robert Cohen wrote: 2018/03/03 22:13:12 Starting cygwin install, version 2.889 2018/03/03 22:13:12 User has backup/restore rights 2018/03/03 22:13:12 Current Directory: C:\Updates\cygwin_download\http%3a%2f%2fcygwin.mirror.constant.com%2f\x86_64 vs. 2017/06/20 18:42:33 St

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 2018-03-03 21:01, Robert Cohen wrote: >> On March 3, 2018 22:11, Ken Brown wrote: >> On 3/3/2018 10:01 PM, Robert Cohen wrote: >>>    Thanks for finding that. However, I am using the same "Local Package >>> Directory" that I used >>> when I ran it to do the download. For example, here's where t

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

>From: cygwin-ow...@cygwin.com on behalf of Ken Brown > >Sent: Saturday, March 3, 2018 22:11 >To: cygwin@cygwin.com >Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded >packages when installing from local directory >  >[Please don't

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

[Please don't top-post on this list.] On 3/3/2018 10:01 PM, Robert Cohen wrote:  Thanks for finding that. However, I am using the same "Local Package Directory" that I used when I ran it to do the download. For example, here's where things were for all the steps: 1. Directory C:\Updates\cygw

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

n.com Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory   On 3/3/2018 6:00 PM, Robert Cohen wrote: > Summary of problem: > When installing Cygwin from a local directory, setup-x86_64.exe version 2.889 > doesn&#

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 2018-03-03 19:16, Ken Brown wrote: > On 3/3/2018 6:00 PM, Robert Cohen wrote: >> Summary of problem: >> When installing Cygwin from a local directory, setup-x86_64.exe version 2.889 >> doesn't >> list the packages that I additionally selected for download when previously >> downloading >> to tha

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

On 3/3/2018 6:00 PM, Robert Cohen wrote: Summary of problem: When installing Cygwin from a local directory, setup-x86_64.exe version 2.889 doesn't list the packages that I additionally selected for download when previously downloading to that directory, and the top line of the GUI under Categor

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

intentionally removed from setup, or might this be a bug? Regards, Robert From: cygwin-ow...@cygwin.com on behalf of Brian Inglis Sent: Saturday, March 3, 2018 18:54 To: cygwin@cygwin.com Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing fr

Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

f the GUI > under Category view says "No packages found<->Default". > Continuing the install only installs the packages preselected by setup. > > Details: > To install a fresh version of Cygwin, I usually do this: Run > setup-x86_64.exe using "Download Wit

setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory

<->Default". Continuing the install only installs the packages preselected by setup. Details: To install a fresh version of Cygwin, I usually do this: Run setup-x86_64.exe using "Download Without Installing", select some additional packages, and then after everything finished,

Re: Bug in poll/select readable state on write end of pipe

consider this a bug in Twisted since I can't find anything in POSIX > which states this behavior (though I could be missing it). > > Nevertheless, on Linux this *is* the behavior: > > >>> import os > >>> import select > >>> r, w = os.pipe() >

Bug in poll/select readable state on write end of pipe

s behavior (though I could be missing it). Nevertheless, on Linux this *is* the behavior: >>> import os >>> import select >>> r, w = os.pipe() >>> poller = select.poll() >>> os.close(r) >>> poller.register(w, select.POLLIN) >>> print(p

Re: cygwin.dll: bug with select on Windows console / 2.4.0-0.19

On Jan 14 16:01, Thomas Wolff wrote: > I have retested some past problems of select with -0.19 and found no > regression issues. Thank you, that's good to know! Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer

Re: cygwin.dll: bug with select on Windows console / 2.4.0-0.19

I have retested some past problems of select with -0.19 and found no regression issues. Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml

Re: cygwin.dll: bug with select on Windows console

ix. Please give any of them a > >>>> try. > >> I built from git master. Both the test program and mosh appear > >> to be seeing correct behavior from select() now. > > > > Thanks for testing. Can you re-test with current git master? I > > reverted o

Re: cygwin.dll: bug with select on Windows console

days ago. >>>> >>>> I've just uploaded new developer snapshots >>>> tohttps://cygwin.com/snapshots/ and a new test release >>>> 2.4.0-0.17 which contain this fix. Please give any of them a >>>> try. >> I built from git mast

Re: cygwin.dll: bug with select on Windows console

snapshots tohttps://cygwin.com/snapshots/ > >>and a new test release 2.4.0-0.17 which contain this fix. Please give any > >>of them a try. > I built from git master. Both the test program and mosh appear to be seeing > correct behavior from select() now. Thanks for testing.

Re: cygwin.dll: bug with select on Windows console

2.4.0-0.17 which contain this fix. Please give any >of them a try. I built from git master. Both the test program and mosh appear to be seeing correct behavior from select() now. Thanks, --jh -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.co

Re: cygwin.dll: bug with select on Windows console

had a bug). I've attached it here. This takes a single > > >> argument, the timeout value for select() in microseconds. A value of > > >> 100 is fine for testing this issue. Type at it, or just bang on the > > >> keyboard with random keystrokes,

Re: cygwin.dll: bug with select on Windows console

>> argument, the timeout value for select() in microseconds. A value of > >> 100 is fine for testing this issue. Type at it, or just bang on the > >> keyboard with random keystrokes, and it will report the results from > >> select() and the characters read

Re: cygwin.dll: bug with select on Windows console

john hood writes: > It appears I had not installed all the packages because I didn't have > the setup command line syntax right, and didn't know it. setup > apparently does not do any validation of its command line arguments: > > setup-x86.exe -M -P "docbook-xsl xmlto" > > fails to install any p

Re: cygwin.dll: bug with select on Windows console

On 1/8/16 11:29 AM, Corinna Vinschen wrote: > On Jan 7 13:18, John Hood wrote: >> Sorry about forgetting the testcase (which was good, actually, that >> version had a bug). I've attached it here. This takes a single >> argument, the timeout value for select() in

Re: cygwin.dll: bug with select on Windows console

On Jan 7 13:18, John Hood wrote: > Sorry about forgetting the testcase (which was good, actually, that > version had a bug). I've attached it here. This takes a single > argument, the timeout value for select() in microseconds. A value of > 100 is fine for testing this i

Re: cygwin.dll: bug with select on Windows console

Sorry about forgetting the testcase (which was good, actually, that version had a bug). I've attached it here. This takes a single argument, the timeout value for select() in microseconds. A value of 100 is fine for testing this issue. Type at it, or just bang on the keyboard with r

Re: cygwin.dll: bug with select on Windows console

john hood wrote: I've attached a little demo program for the bug. Compile, run as "socket-t 1000" (the argument is the number of microseconds select() should wait), and mash keys on the keyboard for a little while. It should report errors within 100 keystrokes. I think t

Re: cygwin.dll: bug with select on Windows console

<http://pubs.opengroup.org/onlinepubs/9699919799/functions/pselect.html> clearly states that select() must zero out all FD_SET bits when it returns 0. * Moving the mouse cursor around over the console window (at a bash prompt, without mouse modes enabled) makes this issue happen *much* more frequen

Re: cygwin.dll: bug with select on Windows console

roup.org/onlinepubs/9699919799/functions/pselect.html> clearly states that select() must zero out all FD_SET bits when it returns 0. * Moving the mouse cursor around over the console window (at a bash prompt, without mouse modes enabled) makes this issue happen *much* more frequently. I&#x

cygwin.dll: bug with select on Windows console

Hi all, I'm one of the Mosh maintainers. Recently a user reported a problem where Mosh exits suddenly soon after startup while he is typing at it, see <https://github.com/mobile-shell/mosh/issues/705>. The problem turns out to be that occasionally, select() times out, returns 0 a

Re: Cygwin installer: "Next" button should not be default on "Select Packages" page

On Tue, Nov 17, 2015 at 5:21 PM, Andrey Repin wrote: > Greetings, Brian Mathis! > >> Current behavior: >> I have, many times, started typing something into the Search box at >> the top of the page and instinctively press Enter. Because the Next >> button is default, this causes the installer to a

Re: Cygwin installer: "Next" button should not be default on "Select Packages" page

Greetings, Brian Mathis! > Current behavior: > I have, many times, started typing something into the Search box at > the top of the page and instinctively press Enter. Because the Next > button is default, this causes the installer to advance to the > installation stage (which may take a while as

Cygwin installer: "Next" button should not be default on "Select Packages" page

Current behavior: I have, many times, started typing something into the Search box at the top of the page and instinctively press Enter. Because the Next button is default, this causes the installer to advance to the installation stage (which may take a while as the actual installation occurs, so

Re: feature request: easier "auto select a close mirror for me"

On Aug 29, 2015, at 12:14 PM, Andrey Repin wrote: > >> somebody >> has already written a script (Perl) to determine fastest Cygwin >> mirror: https://sourceforge.net/p/cygwinmirrortest > >> Perhaps this could become part of the base install? > > No Perl in base. …but someone sufficiently motiv

Re: feature request: easier "auto select a close mirror for me"

Greetings, Philip Daniels! > As noted, speed is more important than proximity. Luckily, somebody > has already written a script (Perl) to determine fastest Cygwin > mirror: https://sourceforge.net/p/cygwinmirrortest > Perhaps this could become part of the base install? Perl script. No Perl in ba

Re: feature request: easier "auto select a close mirror for me"

28, 2015, at 2:04 PM, Jack wrote: >> >> On 2015.08.28 14:23, Andrey Repin wrote: >>> Greetings, Roger Pack! >>> > It would be awesome if the top option for servers were "auto select >>> > closest" or something like that. >> >> I

Re: feature request: easier "auto select a close mirror for me"

On Aug 28, 2015, at 2:04 PM, Jack wrote: > > On 2015.08.28 14:23, Andrey Repin wrote: >> Greetings, Roger Pack! >> > It would be awesome if the top option for servers were "auto select >> > closest" or something like that. > > I wouldn't make i

Re: feature request: easier "auto select a close mirror for me"

On 2015.08.28 14:23, Andrey Repin wrote: Greetings, Roger Pack! > It would be awesome if the top option for servers were "auto select > closest" or something like that. How would it know where you are located and how do you define "closest"? The mirrors that ar

Re: feature request: easier "auto select a close mirror for me"

Greetings, Roger Pack! > It would be awesome if the top option for servers were "auto select > closest" or something like that. How would it know where you are located and how do you define "closest"? The mirrors that are "close" to me give worst speed co

feature request: easier "auto select a close mirror for me"

It would be awesome if the top option for servers were "auto select closest" or something like that. Possibly a web server that would do the redirects for you [?] (or you could do local pings and see which one answers quickest). Possibly like what VLC does for its distro's [1

Alternative implementation of select()?

Hello all, If I've read the code right, the implementation of select() in select.cc sets up a thread per file descriptor. Each of these threads polls their file descriptor looking for events that might have occurred. I also remember reading a long time ago (I cannot find it now) comments

Re: select() fails on multi-byte input in cygwin console (since 1.7.10)

On Dec 10 08:03, Thomas Wolff wrote: > Hi Corinna, > > Am 09.12.2014 um 12:19 schrieb Corinna Vinschen: > >Hi Thomas, > > > >On Dec 9 08:02, Thomas Wolff wrote: > >>Calling select() to check whether input from the terminal is available > >>fails for

Re: select() fails on multi-byte input in cygwin console (since 1.7.10)

Hi Corinna, Am 09.12.2014 um 12:19 schrieb Corinna Vinschen: Hi Thomas, On Dec 9 08:02, Thomas Wolff wrote: Calling select() to check whether input from the terminal is available fails for all but the first byte in the cygwin console if multiple bytes are entered at once, like function or

Re: select() fails on multi-byte input in cygwin console (since 1.7.10)

Hi Thomas, On Dec 9 08:02, Thomas Wolff wrote: > Calling select() to check whether input from the terminal is available > fails for all but the first byte in the cygwin console if multiple bytes > are entered at once, like function or cursor keys or non-ASCII UTF-8 > characters. >

select() fails on multi-byte input in cygwin console (since 1.7.10)

Calling select() to check whether input from the terminal is available fails for all but the first byte in the cygwin console if multiple bytes are entered at once, like function or cursor keys or non-ASCII UTF-8 characters. Actually, the issue is volatile, sometimes it works for characters and

Re: setup: how to select all src packages too?

Greetings, Luke Kendall! >>> It's great that Cygwin has so many packages. And setup.exe makes it >>> easy to select the packages you want. >>> But it seems quite difficult to also select all the corresponding source >>> packages as well, simply b

Re: setup: how to select all src packages too?

On 2/20/2014 5:50 PM, Luke Kendall wrote: On 02/18/2014 08:26 PM, Andrey Repin wrote: Greetings, Luke Kendall! It's great that Cygwin has so many packages. And setup.exe makes it easy to select the packages you want. But it seems quite difficult to also select all the corresponding s

Re: setup: how to select all src packages too?

On 02/18/2014 08:26 PM, Andrey Repin wrote: Greetings, Luke Kendall! It's great that Cygwin has so many packages. And setup.exe makes it easy to select the packages you want. But it seems quite difficult to also select all the corresponding source packages as well, simply because there a

Re: setup: how to select all src packages too?

Greetings, Luke Kendall! > It's great that Cygwin has so many packages. And setup.exe makes it > easy to select the packages you want. > But it seems quite difficult to also select all the corresponding source > packages as well, simply because there are so many packages! In

setup: how to select all src packages too?

It's great that Cygwin has so many packages. And setup.exe makes it easy to select the packages you want. But it seems quite difficult to also select all the corresponding source packages as well, simply because there are so many packages! In the worst case, where you want every package

Re: gcc - Is the C function select thread safe??

Snapshot tried successfully.. Magic! -- View this message in context: http://cygwin.1069669.n5.nabble.com/gcc-Is-the-C-function-select-thread-safe-tp100994p101050.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ

Re: gcc - Is the C function select thread safe??

On Fri, Jul 19, 2013 at 03:25:51PM +0100, trefor.2.edwa...@bt.com wrote: >I have a very recent version of Cygwin (see cygcheck.out attached) and >an test application (attached) which has been extracted from the SIPP >application. Try a snapshot: http://cygwin.com/ml/cygwin/2013-07/msg00392.html -

gcc - Is the C function select thread safe??

I have a very recent version of Cygwin (see cygcheck.out attached) and an test application (attached) which has been extracted from the SIPP application. What it does in a loop is * Creates a thread * In the thread: Calls "select" to wait for just under 1 s

Re: Free Select Mode in latest Cygwin

On 3/28/2013 1:40 PM, Bixler, Mark wrote: Thanks, Larry...I will try to be more descriptive. In previous versions (that I have used) of cygwin installed on a windows box, the terminal is based on a cmd window. With this being said, you could choose from the Cygwin shell -> right click header ->

Re: Free Select Mode in latest Cygwin

Thanks, Larry...I will try to be more descriptive. In previous versions (that I have used) of cygwin installed on a windows box, the terminal is based on a cmd window. With this being said, you could choose from the Cygwin shell -> right click header -> Properties -> Options Tab (upper left co

Re: Free Select Mode in latest Cygwin

On 2/27/2013 12:21 PM, Bixler, Mark wrote: I recently got a new setup at work and installed the latest version of Cygwin. I can no longer find where to do the Edit Mode for free selection of test. I used to be able to just click and highlight anything I wanted, both columns and full body. Now t

Re: select() not interrupted by signals

Am 12.01.2013 20:14, schrieb Christopher Faylor: On Sat, Jan 12, 2013 at 06:41:27PM +0100, Thomas Wolff wrote: Am 11.01.2013 16:38, schrieb Christopher Faylor: On Fri, Jan 11, 2013 at 09:41:37AM +0100, Thomas Wolff wrote: ... ... select() is not restartable like read() or write(). That

Re: select() not interrupted by signals

On Sat, Jan 12, 2013 at 06:41:27PM +0100, Thomas Wolff wrote: >Am 11.01.2013 16:38, schrieb Christopher Faylor: >> On Fri, Jan 11, 2013 at 09:41:37AM +0100, Thomas Wolff wrote: >>> I had previously reported "select() hanging after terminal killed" >>> (http://

Re: select() not interrupted by signals

Am 11.01.2013 16:38, schrieb Christopher Faylor: On Fri, Jan 11, 2013 at 09:41:37AM +0100, Thomas Wolff wrote: I had previously reported "select() hanging after terminal killed" (http://cygwin.com/ml/cygwin/2011-05/msg00418.html). It turns out that select() does not get interr

Re: select() not interrupted by signals

On Fri, Jan 11, 2013 at 09:41:37AM +0100, Thomas Wolff wrote: >I had previously reported "select() hanging after terminal killed" >(http://cygwin.com/ml/cygwin/2011-05/msg00418.html). >It turns out that select() does not get interrupted by a SIGWINCH signal >either (with

Re: select() not interrupted by signals

On Jan 11 13:55, Thomas Wolff wrote: > On 11.01.2013 09:52, Corinna Vinschen wrote: > >On Jan 11 09:41, Thomas Wolff wrote: > >>I had previously reported "select() hanging after terminal killed" > >>(http://cygwin.com/ml/cygwin/2011-05/msg00418.html). > &

Re: select() not interrupted by signals

On 11.01.2013 09:52, Corinna Vinschen wrote: On Jan 11 09:41, Thomas Wolff wrote: I had previously reported "select() hanging after terminal killed" (http://cygwin.com/ml/cygwin/2011-05/msg00418.html). It turns out that select() does not get interrupted by a SIGWINCH signal either (w

Re: select() not interrupted by signals

On Jan 11 09:41, Thomas Wolff wrote: > I had previously reported "select() hanging after terminal killed" > (http://cygwin.com/ml/cygwin/2011-05/msg00418.html). > It turns out that select() does not get interrupted by a SIGWINCH > signal either (with likely the same cause).

select() not interrupted by signals

I had previously reported "select() hanging after terminal killed" (http://cygwin.com/ml/cygwin/2011-05/msg00418.html). It turns out that select() does not get interrupted by a SIGWINCH signal either (with likely the same cause). This raises problems with interactive programs that wan

new in 1.7.17: select returning -1 with errno equal to zero

Since upgrading to Cygwin 1.7.17, I've seen Emacs occasionally print "select error: no error", indicating that select returned -1 while leaving errno set to zero. I haven't come up with a repro or simple testcase yet, but I figured I'd make someone aware of the

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

Larry Hall (Cygwin cygwin.com> writes: > So you're saying the snapshot exhibits the above behavior? > No, this was happening pre and post snapshot. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 6:24 PM, Robert F wrote: Larry Hall (Cygwin cygwin.com> writes: Your advice did solve the problem, thanks! I wonder which specific entry in the changelog did it... Great! I thought you might at least see some different behavior. There has been a fair bit of work done in th

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 5:34 PM, Robert F wrote: This has me stumped. I'd suggest trying a snapshot - If that doesn't help, a full problem report might help someone on the list spot an issue. Problem reports: http://cygwin.com/problems.html I might give the

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

Larry Hall (Cygwin cygwin.com> writes: > Your advice did solve the problem, thanks! I wonder which specific entry in the changelog did it... The unwillignness to show any text until it finds a newline seems it could be a cygwin issue. Taking the following code: #ifndef __CYGWIN__ #define SLEE

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

Robert F hotmail.co.uk> writes: > > > > I might give the snapshot a shot. Do you know how far from the release > > build > > the latest snapshot is and when the next one is planned? > > > > Update: I did a flat replacement of cygwin1.dll with the latest snapshot of it > and all my cygwin ap

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

> I might give the snapshot a shot. Do you know how far from the release build > the latest snapshot is and when the next one is planned? > Update: I did a flat replacement of cygwin1.dll with the latest snapshot of it and all my cygwin apps go apesh*t. Is it because I didn't update the whole

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

> > This has me stumped. > > I'd suggest trying a snapshot - > > If that doesn't help, a full problem report might help someone on the list > spot an issue. > > > Problem reports: http://cygwin.com/problems.html > I might give the snapshot a shot. Do

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 5:25 PM, Larry Hall (Cygwin) wrote: On 1/17/2012 5:16 PM, Robert F wrote: This could be a cygwin bug, but I'm not 100% sure. It may even be a weird interaction with the windows console. I have a single threaded app that loops, polls network activity with a 'select

Re: Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

On 1/17/2012 5:16 PM, Robert F wrote: This could be a cygwin bug, but I'm not 100% sure. It may even be a weird interaction with the windows console. I have a single threaded app that loops, polls network activity with a 'select' function and interrupts the flow of the loop

Madness with the 'select' function, sigalrm, and stdout. (CYGWIN_NT-6.1-WOW64)

This could be a cygwin bug, but I'm not 100% sure. It may even be a weird interaction with the windows console. I have a single threaded app that loops, polls network activity with a 'select' function and interrupts the flow of the loop when a SIGALRM signal is ran, the handler

  1   2   3   4   5   >