recvfrom bug

Dear mailing list: The following code works well on a Linux platform, int sockfd; char buf[1024]; struct sockaddr fromaddr; int fromlen; if ( (retv = recvfrom( sockfd, buf, sizeof(buf), 0, &fromaddr,&fromlen )) < 0 ) { perror( "udpclient: recvfrom" ); } However, in cygw

Re: recvfrom bug

Thank you. I will try that. - Original Message - From: "Thomas Pfaff" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, November 14, 2002 7:28 AM Subject: Re: recvfrom bug > Dr. M. C. Nelson wrote: > > Dear mai

Strange group name

I have installed cygwin 1.5.6(0.108/3/2) and I notice that the files in my home directory have a group ownership of "mkgroup-l-d". I'm new to cygwin, and have installed it as a domain user on a workstation running Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4. Please could someone s

New user question

I discovered Cygwin last week and I like what I see so far. I have one question in regards to installing gcc. Can I go with 3.0.3 or do I have to use an older version? This is for installing on Win98 and WinNT 4.0 systems. Bill Gallip CDSA Dam Neck Virginia Beach, VA -- Unsubscribe info:

Your request for Express Transfer - attn: cygwin@cygwin.com

Your request for Express Transfer from your SIERRA CENTRAL C.U. account to your bank account ending in 6297, has been received and is in process. This process usually takes 6-8 working hours to complete but is dependent on your account preferences. See, Change or Cancel this Transfer at:

cygwin setup error

After a new install of cygwin, the following errors are reported the first time a bash shell console or xterm is opened.  The same error message is displayed after trying to run any application. After this the console window or xterm can be closed and then reopened, and the error is gone. After log

cygwin setup error

After a new install of cygwin, the following errors are reported the first time a bash shell console or xterm is opened.  The same error message is displayed after trying to run any application. After this the console window or xterm can be closed and then reopened, and the error is gone. After log

Wide Character support in Cygwin

Hi All, Is the wide character support for GCC available in Cygwin We have tried to compile a piece of code which works on SLES 9 LINUX But the same code throws errors when compiled on cygwin. Can any one please suggest how to solve this problem The following is the code : #include #

[no subject]

have some issue using cygwin to access the network drive. I have three VM(A, B, C). Environment: VM A(11.11.11.1) is used as NAS and I also created a share folder inside VM A. I Installed cygwin on window VM B(11.11.11.2) and map a network drive(the share folder) from VM A. I used another Linux

Re:

hi If i didnt ssh-copy-id , i can access the share folder On Sun, 23 Aug 2020 at 01:20, Andrey Repin wrote: > Greetings, C Goh! > > > have some issue using cygwin to access the network drive. I have three > > VM(A, B, C). Environment: VM A(11.11.11.1) is used as NAS and I

Cannot access network drive or shares

Method 1: Map drive I have some issue using cygwin to access the network drive. I have three VM(A, B, C). Environment: VM A(11.11.11.1) is used as NAS and I also created a share folder inside VM A. I Installed cygwin on window VM B(11.11.11.2) and map a network drive(the share folder) from VM A

RE: CPU usage issue with bash

Eric, Thanks for the offer to help. I am attaching cygcheck.out If you need me to carry out some more investigations, please let me know. -- Shourya -Original Message- From: Eric Blake [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 18, 2005 8:29 PM To: Sarcar, Shourya C (GE

RE: CPU usage issue with bash

still seeing the CPU usage issue. > Relevant portions of your cygcheck: > > PWD = `/c/insite' > Found: \bin\bash.exe > Warning: C:\cygwin\bin\bash.exe hides \bin\bash.exe > > It seems like you have competing tools. If anything from > insite is ever picked up in pref

CPU usage issue with bash

Bash seems to be taking up a lot of CPU resources for me. It peaks to 100% for lengthy spans of around 20-30 seconds. On NT systems (with an older cygwin) I notice peaks to around 70-80% for shorter durations of time. Is this a known issue with bash ? I found this on the archives. http://www.cygwin

RE: http://www.cygwin.com/ml/cygwin/2001-03/msg01023.html reply

I'm not sure how this works to put up a reply, but having the same problem, I found a solution not included in the followups: Try it without the \ before the ; c:\cygwin\bin\find.exe . -name "files to search pattern" -exec c:\cygwin\bin\grep.exe "search string" &#x

Display text file using less in Cygwin terminal or xterm incorrect when lines are longer then window width

I have used Cygwin and CygwinX for many years and this problem has persisted for many of those years, I can't remember the last time this worked. Using vim in an xterm or terminal window displays text in a file properly. The problem with less is easy to reproduce, but there are several different

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote: > > Works Just Fine For Me! > > > This is Cygwin 64 on Windows 10 in a VirtualBox VM, cygcheck output attached. > > It has been a while since I up

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > On Fri, 13 Aug 2021 21:47:53 -0400 > C Linus Hicks wrote: > > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote: > > > > Works Just

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > > On Fri, 13 Aug 2021 21:47:53 -0400 > > C Linus Hicks wrote: > > > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > &

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > On Fri, 13 Aug 2021 23:46:35 -0400 > C Linus Hicks wrote: > > > On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: > > > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > > > >

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Sat, 2021-08-14 at 13:35 +0900, Takashi Yano wrote: > On Sat, 14 Aug 2021 00:05:17 -0400 > C Linus Hicks wrote: > > On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > > > On Fri, 13 Aug 2021 23:46:35 -0400 > > > C Linus Hicks wrote: > > > >

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 2021-08-13 at 22:37 -0600, Brian Inglis wrote: > On 2021-08-13 22:05, C Linus Hicks via Cygwin wrote: > > On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > > > On Fri, 13 Aug 2021 23:46:35 -0400 > > > C Linus Hicks wrote: > > > > > >

Re: Terminal occasionally shows duplicate command text when it is split over multiple lines

On Mon, 2021-08-23 at 21:52 +, Ray Satiro via Cygwin wrote: > I'm using cygwin x86 updated yesterday and when I paste in commands that are > split over multiple lines sometimes an arbitrary line will show more than > once, even though it is not actually part of the command more than once. For

Re: sshd times out and disconnects client

On the server side, you can update the sshd_config file and set the value of the ClientAliveInterval to a non-zero value, like 60 seconds. Or you can set the ServerAliveInterval option to a similar value in your client options, either on the command line or in your local config file. -Origi

RE: cp vs copy performance over local network

> There's overhead to handle POSIX permissions, etc. For one file, the effects of copying the meta-data should be negligible. Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: h

SIGKILL and TerminateProcess

Hello List, I have a question, as to why CYGWIN does not use the TerminateProcess approach when dealing with SIGKILL sent to a process (in the manner the CYGWIN's own kill utility does when invoked with -f)? Usually SIGKILL is expected to reliably terminate its victim (let alone it can't be int

fork() and NT error 0xC0000135 (STATUS_DLL_NOT_FOUND)

Hello All, I can't find a similar problem reported earlier, so please excuse the question if it looks familiar. We have a software package that installs like a miniature CYGWIN deployment (basically, only cygwin1.dll and just a few other libraries in /bin along with cygrunsrv.exe), and there are

RE: fork() and NT error 0xC0000135 (STATUS_DLL_NOT_FOUND)

path with -p "/opt/path/to/bin/server.exe", which is within the rudimentary CYGWIN tree that also has "/bin" (rooted at some Windows directory, C:\Apps\CYGWIN). > Two points: > > - cygrunsrv adds /bin to $PATH before calling the service executable. > > - ST

RE: SIGKILL and TerminateProcess

> Sorry but we aren't going to redesign the signal delivery mechanism for > your use case. It wasn't exactly a redesign I was asking about; rather an addition (or an improvement, if you will) for only the case of that one KILL signal, which is already a special thing in all aspects even on UNIX.

RE: fork() and NT error 0xC0000135 (STATUS_DLL_NOT_FOUND)

> Are you running 32 or 64 bit Cygwin? If that's ok with you, I'd PM > you an URL to a matching, patched cygrunsrv binary for testing. Thanks! I have the 32-bit CYGWIN installed, and will check the patched the cygrunsrv binary with much appreciation. Anton Lavrentiev Contractor NIH/NLM/NCBI -

RE: fork() and NT error 0xC0000135 (STATUS_DLL_NOT_FOUND)

> Add cygwin1.dll to the list of known system libraries. > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths Thanks for the suggestion. > the server SHOULD NOT unconditionally change the CWD to the ROOT of a file > system Many UNIX daemons do so not to lock up certain parts

RE: SIGKILL and TerminateProcess

> As the person who wrote the signal handling code, I Believe it or not, I'm well aware of that. > continuing to insist that you need this will avail you naught There was no intention to insist on anything; but to understand why that has been implemented the way it is. And the point has been t

RE: SIGKILL and TerminateProcess

> http://cygwin.com/ml/cygwin-patches/2009-q4/msg00028.html > Don't know if this will help in your situation, but I figured it should > be mentioned. Thank you for the follow up. The idea was to use CYGWIN (and hence UNIX scripting) to control (mainly: launch / stop) applications (whether CYGWI

RE: [ANNOUNCEMENT] Updated: cygrunsrv-1.50-1

FWIW, I was able to download it from kernel.org's mirror just fine this morning: ftp://mirrors.kernel.org/sourceware/cygwin/x86/release/cygrunsrv/ Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Doc

RE: vi stealing SYSTEM-owned permissions and ownership

> > Haha, yes. But if my students have to administer remote > production-machines, most of the time they have no other option. I want them > to succeed where others fail. Reading this thread, it looks like it digressed far away from the original point ($subject) as to why "vi" did not keep the ori

Seeking a suggestion for unattended mass install procedure

Hello All, I am trying to help my site's Systems team to straighten up CYGWIN installation process, which they will need to perform to build new PCs, and I have volunteered to ask on their behalf here.. As far as they can tell, there is no such an installation option that tells to install "everyt

Building a snapshot ("Not an ELF file" error)

Hello All, I'm using some recent (not the latest, though) CYGWIN release, and trying to build a CYGWIN snapshot (for the first time)... When I deployed the snapshot source, ran configure, then make, I saw this: checking for .preinit_array/.init_array/.fini_array support... readelf: Error: Not a

RE: Seeking a suggestion for unattended mass install procedure

> Though I haven't experimented with this myself, I'd recommend looking at > using "setup*.exe" on the command line and listing the packages to install > there. Thanks. But I P.S.'d about that option as undesirable -- as it requires to maintain quite a long list of packages, all listed individual

RE: Seeking a suggestion for unattended mass install procedure

> Just make a list from that as part of your install script. That is the problem, right there. I counted some 150 directories, many of which contain 10+ packages, easily. A manageable install command would have looked like "setup.exe -L directory -a" to get and install everything it could have f

RE: Building a snapshot ("Not an ELF file" error)

> does not cause any ill side-effects, either (just as yet, at least). Maybe I spoke too soon, or maybe it's not at all related, but my build finally failed like this: ... make[3]: Leaving directory `/home/lavr/cygwin-snapshot-20130925-1/i686-pc-cygwin/winsup/lsaauth' make[3]: Entering directory

RE: Seeking a suggestion for unattended mass install procedure

> I have an install script for Cygwin. It's not offline Thanks for the suggestion. My Systems team need to install from scratch on bare boxes, from only an image DVD (which contained all the requisites of the future machine, including CYGWIN's setup and the downloaded directory, as I previously d

RE: Seeking a suggestion for unattended mass install procedure

> Are you saying this won't work? > Or do you just not like it? A little bit of both, actually. Windows CMD.EXE has an 8K limit on the command line length, AFAICT. Even if that was not exceeded first time the package list was created, it may easily get there on a complete re-run of the install

RE: Seeking a suggestion for unattended mass install procedure

> Alternatively, you can grab the sources for setup and add an option to do what you want the way you want it. Well, that's a trivial option with open source, of course. But also it means to maintain a branch of our own setup.exe, which is the least favorable of all. Anton Lavrentiev Contractor

RE: Seeking a suggestion for unattended mass install procedure

> genini --recursive x86 > x86/setup.ini That's an interesting piece of information, thanks! Where can I get "genini" or "upset" from? Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation

RE: Seeking a suggestion for unattended mass install procedure

> you're adding additional requirements Rather revealing them... The procedure is still to grab the current setup, make package selection, download with satisfying the dependencies, then install on a bunch of boxes in the batch mode, unattended. When a new set of machines is to be built, repeat

RE: Building a snapshot ("Not an ELF file" error)

Hello List, It'd still be very interesting to know an opinion of the CYGWIN gurus about this trouble that I asked yesterday (thanks to Marco, I now know that the original ELF error is benign): > make[3]: Entering directory `/home/lavr/cygwin-snapshot-20130925-1/i686-pc- > cygwin/winsup/doc' > bui

RE: Building a snapshot ("Not an ELF file" error)

> We don't support building within the source dir. That's unclear to me. I just did "./configure" then "make" at the top snapshot directory. AFAICT, the build result was stored under ./i868-pc-cygwin. > xidepend is guaranteed to be not in. Well, that is even more confusing. If it not supposed

RE: Building a snapshot ("Not an ELF file" error)

> See the FAQ: I see, thanks Larry! There's a Readme file at the top level of the snapshot tar ball, which I glanced at, and saw the usual "./configure; make" sequence even though now when I looked more closely, the file is just somethi

RE: Building a snapshot

> > See the FAQ: Well, I guess this time I followed the instructions to a tee by using a separate "build" directory, but the snapshot build still fails at the very same spot: ... make[3]: Leaving directory `/home/lavr/build/i686-pc-cygw

RE: Building a snapshot

> The page you mentioned expressly say that these errors can be ignored. It says, > Normally, building ignores any errors in building the documentation which IIUC means it should ignore such errors on its own -- not stop with a hard failure, such as with not being able to construct a path with a

RE: Building a snapshot

> I'm not sure how you translate not building in the source directory to > "the configure file is not supposed to be used". > The configure script isn't generic. It's intended for building Cygwin. > Once again: YOU ARE NOT SUPPOSED TO BUILD IN THE SOURCE DIRECTORY. > That means you don't do thi

RE: vi stealing SYSTEM-owned permissions and ownership

> > If you are operating as a normal user on this folder, you aren't > > actually editing the files you think you see there, the whole contents > > is virtualized by UAC and redirected to your own personal copy on edit. While it does sound feasible, it does not explain the fact that the other edit

RE: Pipe syncronization and incompatibility between Cygwin and .NET Framework 4.0

MSDN does not list pipe handles as waitable with WaitForMultipleObjectsEx (only a user comment at the end does). If you trace execution without PeekNamedPipe(), you'll see that WaitForMultipleObjectsEx() returns immediately, and that it is ReadFile() that blocks and waits for the input (which will

RE: Pipe syncronization and incompatibility between Cygwin and .NET Framework 4.0

> Check line 192 for a call to the WaitForAvailableConsoleInput function. I guess they expect hFile to be a console handle (which IS waitable). And my guess that they added the Peek intentionally to prevent the WaitFor call from slipping through (as we've seen it does, otherwise) on things that w

RE: Windows 7 64 Bit - Mounting Network Drives

BTW, there is a type there, IMO: > http://cygwin.com/cygwin-ug-net/using.html#cygdrive none /cygdrive cygdrive binary 0 0 D: /cygdrive/d somefs text 0 0 will not make file access using the /mnt/d path prefix suddenly using textmode The sentence after the fstab excerpt should have referr

dircolors generates output with '\r\n' ?

Hi, I was trying to use the dircolor command on CYGWIN, and it did not work because the two lines, which this command produces are separated by CRLF (which when sourced by bash are not understood, bash seems to expect single LFs): LS_OPTIONS='...';\r\n export LS_OPTIONS\r\n Why there are Windows

RE: second call to mmap() results in error

> Adding the fixes the problem in all its iterations I must be missing a point here, so what was the problem with the original test program (which BTW worked fine on my CYGWIN installation). Seems like was not needed there? And how adding just (w/o adding ftruncate(), IIUC) has made it work?

RE: dircolors generates output with '\r\n' ?

> If you edit the file with a native Windows editor, it will typically > introduce the Windows-style EOL characters. I did not edit anything, I just ran "dircolors", and it's output contains "\r\n"s. Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.h

RE: second call to mmap() results in error

> Maybe you missed Corinna's reply? > > No, I did not. She was going after ftruncate() there. Yet, the problem seems to be in cygwin's , which does this: #ifndef __INSIDE_CYGWIN__ extern void *mmap (void *__addr, size_t __len, int __prot, int

RE: second call to mmap() results in error

> #if*n*def __INSIDE_CYGWIN__ Alright, I can't read, sorry. Still, I can't figure out why adding has fixed the initial program made it run successfully (as the OP reported). Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ:

RE: second call to mmap() results in error

> Try adding -Wall to your compile line. I did. There was no warning (and it should not have because #include is there). Why ? It's not needed to compile and run the original code. Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ:

RE: dircolors generates output with '\r\n' ?

> Then one possibility is that you redirected it to a file that is mounted on > a file system that isn't binary. There it was, indeed. Thanks. And sorry about my brain-f@rt. Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ:

RE: second call to mmap() results in error

> Forget mmap(). Why? The response was: > Adding the fixes the problem in all its iterations -- the original > mmap() > test works (without the call to ftruncate()), as well as the second one. Note *the original*. Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://c

RE: second call to mmap() results in error

> So if the question is why do you need to include ftruncate() in the code, > take a look here: No, that was not the question. W/o ftruncate(), _referencing_ the memory becomes a problem (and the original code did not do that, but simply mmap'ed two files). > > Adding the fixes the problem in a

RE: How big are your /etc/passwd and /etc/group files?

> Is anybody here who's using /etc/passwd and/or group files > of more than 16K in size? > > If so, please reply to this thread with the size of your files. /etc/passwd: 200k /etc/group: 35k Anton Lavrentiev Contractor NIH/NLM/NCBI

RE: get rid of getpwent? (Was: cygwin-1.7.28 getpwent header declaration changes ?)

> I think SAM/AD will be mostly quicker I do not want to be a party pooper here, but have you checked how the AD approach will work from the unmanaged Windows service accounts? We've been experiencing rather nasty effects of the M$ design that when a host changes its password (it is required to,

RE: get rid of getpwent? (Was: cygwin-1.7.28 getpwent header declaration changes ?)

> and I fail to see how this is related to the on-the-fly generation of passwd > and group entries Well, if a cygwin app was run under such an account, it might be affected, that's all... Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ:

RE: Invoking Cygwin vim from Windows Explorer

> If there is no simple answer, Maybe not as simple, but... What about adding a "Vim" destination to your "Send To..." folder under your Windows profile? The target command can be something like: C:\cygwin\bin\mintty.exe -e c:\cygwin\bash.exe -c C:\cygwin\bin\vim.sh Wh

RE: Invoking Cygwin vim from Windows Explorer

Correction: c:\cygwin\bash.exe should have been written as c:\cygwin\bin\bash.exe. Sorry about that. Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com

RE: Invoking Cygwin vim from Windows Explorer

you are going by on that Windows system): C:\Users\\AppData\Roaming\Microsoft\Windows\SendTo In the opened Explorer window, right click on unoccupied space on the right hand pane, select "New"->"Shortcut". As prompted for "Location", enter (I assume your Cygwin ins

RE: Invoking Cygwin vim from Windows Explorer

Oops, I copied it incompletely > cat < cat >vim.sh

RE: Invoking Cygwin vim from Windows Explorer

> an administrative password to run minty That's new to me. My PC at work (despite being secured with tons and tons of Gov't restrictive policies) does not require any additional permissions to run a command incorporated in the shortcut file... Anton Lavrentiev Contractor NIH/NLM/NCBI -- Proble

Testers needed: New passwd/group handling in Cygwin

This will not work (verified!) for code run from under an unmanaged Windows service account (NT_Service\...), once the machine changes its password per security policy (the access then becomes anonymous and will result in only first 100 entries returned): winsup\cygwin\passwd.cc: else if

RE: Testers needed: New passwd/group handling in Cygwin

> These functions are not called for domain accounts, only for local > accounts. Okay then.. Anton Lavrentiev Contractor NIH/NLM/NCBI

cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?

Hi, I need to kill a process in a way that CYGWIN's own kill utility does with an option -f, and for that, given CYGWIN's PID, I need to figure out native Windows PID of the victim. kill does basically the following (I simplified): p = (external_pinfo *) cygwin_internal (CW_GETPINFO_FULL, pid);

exe.stackdump is always empty

shell limits from their stock values, either. $ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited open files (-n) 256 pipe size(512 bytes, -p) 8 stack size

RE: exe.stackdump is always empty

> If your process crashes with a thoroughly scrambled stack, there's > a good chance that Cygwin won't be able to create a stackdump file > because it crashes again while producing the stackdump. I don't think it's all that bad -- it was merely an assert() triggering app's abort...

Tons of cygserver errors

Hi, Event Log on my PC is full (literally) of these, recorded every 5 seconds or so, and usually coming in in pairs (2 of the same, then 5 sec pause, then another 2, and so on) Could someone please explain what do they mean? I am not running with Admin privs (although, cygserver is). My apps

RE: Tons of cygserver errors

> there's really no reason to quote that at all Maybe, but how would I know that you did not need that? > It means the pointer to the "signal_arrived" event object is invalid. > "signal_arrived" is used internally to notify wait functions that a > POSIX signal arrived for the process and to imple

RE: Tons of cygserver errors

>> I can’t push this through your list spam filter. Another attempt... I was trying a few times, and finally deleted the strace attachment. Let's see if this will go through. Excuse me for being a bit straightforward, but the spam filter this list is using is *really* stupid! > Still, you're

RE: Tons of cygserver errors

> You seem to have no problem asking for help with cygserver without > insulting cygserver in the process. Possibly you're even interested in > improving cygserver. I was trying to submit a bug report in good faith (and many tries, for that matter), yet the only way to do that was through this l

RE: exe.stackdump is always empty

> Hmm, not me. In my case a stackdump is generated... There seems to be an access denied condition "C05" along the lines of the strace output that I've sent. What could have caused that? Can that be a reason for me not getting the core dump at all? Thanks, Anton Lavrentiev Contractor NIH

RE: Tons of cygserver errors

> I created a fix and I'm just building cygwin 1.7.29 with it. That's a good news, and thanks for the quick fix! I'll let you know if the issue is resolved on my end, too. Anton Lavrentiev Contractor NIH/NLM/NCBI

RE: exe.stackdump is always empty

> Does it still occur after update? Haven't tried it yet; is the new snapshot out already? -- can't see it on the website... Anton Lavrentiev Contractor NIH/NLM/NCBI

Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?

Hello, It looks like in order to effectively kill the process by Windows means (i.e. what Cygwin "kill -f" is supposed to do), the process handle must be obtained with the SYNCHRONIZE right (in addition to PROCESS_TERMINATE), otherwise WaitForSingleObject() fails with code 5, permission denied (

RE: Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?

> Nah. Maybe we'll have something when the Singularity finally occurs. I cannot supply patches for you guys because of the GPL. No need to be sarcastic all the time -- for the project lead it does not sound witty. Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygw

RE: Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?

> He's a contractor for the US Government. That makes things complicated and > sometimes seemingly nonsensical. Thanks, Barry. A patch (however small) means code, all my code must under the Public Domain Notice (and which can't be GPL'd). Thus, our legal office does not allow us contributing

RE: Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?

> The whole POINT of this thread was that we want patches. You've just killed that point, alright. The change I was about, was merely a word-long (another keyword to be added), the discussion that sparkled was just despicable. The response was so earful, with profanities and teaching me (?) leg

CYGWIN app crashes ungracefully when run from the root of a drive

Hi, Maybe it has been covered somewhere -- I could not find the answer, so please excuse the repetition. I observe that if I build an app (consider the simplest "Hello world" program below as an example), and store the executable at a standalone location (not CYGWIN tree), yet supplemented it wi

UNIX groups in CYGWIN

from Windows) and to delimit the group names in the groups' output: $ groups | od -a 000 D o m a i n sp U s e r s sp R e m 020 o t e sp D e s k t o p sp U s e r 040 s sp U s e r s sp N C B I u

GetLogicallProcessorInformation(Ex) is missing?

Hi, Is there any reason why the API is missing from the CYGWIN's headers (/usr/include/win32api/*.h)? http://msdn.microsoft.com/en-us/library/windows/desktop/ms683194(v=vs.85).aspx Thanks, Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ:

FW: GetLogicallProcessorInformation(Ex) is missing?

Thanks, but it seems like it's already there: http://sourceforge.net/tracker/?func=detail&aid=3490471&group_id=2435&atid=102435 Anton Lavrentiev Contractor NIH/NLM/NCBI > On Wed, Jun 13, 2012 at 9:18 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] > wrote: > > Hi, > &

RE: UNIX groups in CYGWIN

> Why not allow (and generate with mkgroup) URL encoding e.g. > "Domain%20Users"? Good idea that'd hopefully work, too! Anton Lavrentiev Contractor NIH/NLM/NCBI -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://c

Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results

Hi, Observed is an inconsistent result when recvmsg() is used on a UDP socket with or without ancillary control message parameters. Here's is an example: static char buf[1 << 16]; struct sockaddr_in sin; struct msghdr msg; struct iovec iov; #ifndef CYGWIN_BUG char cmsgbuf[32]

RE: Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results

> I applied a patch which should fix this problem. It always uses > WSARecvMsg now, if called from recvmsg, still provided it is possible, > of course (No SOCK_STREAM, no AF_LOCAL). > > I'm just generating a new developer snapshot. Please give the today's > snapshot from http://cygwin.com/snapsh

kbhit() in a native app run from CYGWIN console does not work?

Hi All, I have a native Windows app that is run from bash (which is in turn run in a standard Cygwin terminal window, mintty). The application's code uses kbhit() to check whether input is available from the user -- but it looks like kbhit() never indicates any input (when keys are getting presse

Installation issue with recent cygwin (1.7.16-1) (and unable to link afterwards)

Hi, I was doing a fresh install on a Windows 7 (x64) box that has its Users and ProgramData folders JUNCTIONed from C: (SSD) to D: (HDD), and CYGWIN was to be installed at D:\Cygwin. There's no issues with running any Windows app so the layout works just as expected. However, when CYGWIN

Cygserver diag typo?

Hi, in the below piece of code from cygserver sources (bsd_helper.cc): if (p->gid == (gid_t)-1) log (LOG_WARNING,"WARNING: Group not found in /etc/passwd! Using gid -1!"); Wasn't "/etc/passwd" supposed to actually be mentioned as "/etc/group"? (I gather, it is a copy-n-paste thing from th

Possible race in SYSV IPC (semaphores)

Hi, For now, I can only report the observed (mis) behavior of SYSV semop() call, which (on the client side) gets manifested as the following: transport_layer_pipes::connect: lost connection to cygserver, error = 2 (this code then does a by-hand adjustment with semctl(SETVAL)). Note that there i

SYSV semaphore bug (testcase attached)

Hi, As I previously reported, there is a weird behavior of CYGWIN implementation of SYSV semaphores, and a bug exposition for one problem is attached below (I'm still looking into some other issues in there). If the code is compiled with both BUG1 and BUG2 defined (as shown), it will abort at ite

<    1   2   3   4   5   6   7   >