Re: Changing Home Directory

2011-07-25 Thread Jason Curl
On 25/7/2011 05:00, ScKaSx wrote: Hi All, I just installed Cygwin and found that my home directory is defined by Windows HOME environment variable. My question is how I can change my cygwin home directory without changing the Windows HOME variable, in other words to use /etc/mkpasswd?

Re: I want to use DLL compiled with Cygwin with VC(VS2008).

2011-02-19 Thread Jason Curl
On 14/02/2011 05:03, Y.Hosoi wrote: Thank you. However, it did not move well. If test.dll is done in LoadLibrary, Access Violation is generated. Are you still amused something? [main source code] #include stdafx.h #include windows.h #ifdef __cplusplus extern C{ #endif typedef int

Re: Difference in behaviour between getifaddrs() and ioctl(SIOCGIFCONF)

2010-12-02 Thread Jason Curl
Jason Curl jcurlnews at arcor.de writes: Hello, I've seen an issue when using getifaddrs() using Cygwin 1.7.x (snapshot build from 2010-11-24, shortly after the ARP fixes from Corinna). Operating System is Windows 7 x64_86 Ultimate. When I use getifaddrs() I get a list of interface

Re: Difference in behaviour between getifaddrs() and ioctl(SIOCGIFCONF)

2010-12-02 Thread Jason Curl
Corinna Vinschen corinna-cygwin at cygwin.com writes: I think there's a potential solution to this problem. It just depends on how important it is. snip So here's the idea. If we remove the braces from the GUID name, we drop 2 chars, so we have 6 chars left. 6 chars are enough to

Re: Difference in behaviour between getifaddrs() and ioctl(SIOCGIFCONF)

2010-12-02 Thread Jason Curl
Jason Curl jcurlnews at arcor.de writes: Corinna Vinschen corinna-cygwin at cygwin.com writes: So, for the above interface we get 371D57D9-0FF3-402C-AB69-E88FF9D85BC3:f36e.1 as the unique alias name for the given IPv4 address. The solution that I do prefer, is one similar

Re: Difference in behaviour between getifaddrs() and ioctl(SIOCGIFCONF)

2010-12-02 Thread Jason Curl
On 02/12/2010 18:59, Corinna Vinschen wrote: On Dec 2 14:23, Jason Curl wrote: One of my use cases is to test a particular interface if it has an IP address or not (due to DHCP, AutoIP, etc.). Then on definition of an address, I can trigger a process. This assumes that the interface names

Difference in behaviour between getifaddrs() and ioctl(SIOCGIFCONF)

2010-12-01 Thread Jason Curl
Hello, I've seen an issue when using getifaddrs() using Cygwin 1.7.x (snapshot build from 2010-11-24, shortly after the ARP fixes from Corinna). Operating System is Windows 7 x64_86 Ultimate. When I use getifaddrs() I get a list of interface names, some are appended with :1. Getting the

Re: ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-24 Thread Jason Curl
Corinna Vinschen corinna-cygwin at cygwin.com writes: I tried to understand what this flag is for. As far as I can understand, windows will always reply to ARP requests. There's a registry entry for gratuitous arp. So doesn't that imply IFF_NOARP will be set for all interfaces? You

Re: ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-23 Thread Jason Curl
René Berber r.berber at computer.org writes: On 11/22/2010 2:29 PM, Jason Curl wrote: [snip] And the interface that is failing: D4B7FEA9 = 169.254.183.212 doesn't appear by a call to ipconfig /all. I'm guessing that Windows is [snip] I'm not sure where this IP is currently coming from

Re: ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-23 Thread Jason Curl
Corinna Vinschen corinna-cygwin at cygwin.com writes: On Nov 22 21:29, Jason Curl wrote: The actual delays are caused by SendARP() called from get_xp_ifs(). Interestingly enough, it isn't always slow, only sometimes. [...] First of all, thanks for looking deeper into this. Thanks

Re: ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-23 Thread Jason Curl
On 23/11/2010 16:38, Corinna Vinschen wrote: On Nov 23 14:10, Jason Curl wrote: Actually, after reading a bit about this flag, the usage in Cygwin seems to be wrong anyway. I applied a patch so that IFF_NOARP is only set for PPP and SLIP devices, so the call to SendARP is gone. Please test CVS

Re: ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-22 Thread Jason Curl
On 22/11/2010 14:17, Corinna Vinschen wrote: On Nov 20 18:25, Jason Curl wrote: On 15/11/2010 17:22, Corinna Vinschen wrote: On Nov 9 09:20, Jason Curl wrote: 166 65418 [main] ipcheck 5580 ioctl: fd 3, cmd 80087364 --- Process 5580, exception C005 at 610C8C86 Crash in Cygwin

Re: ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-22 Thread Jason Curl
On 22/11/2010 14:17, Corinna Vinschen wrote: Can you retry with the next developer snapshot? Are the ioctl calls still slow? If so, I'm wondering if the GetAdaptersAddresses call is rather slow if a lot of interfaces exist. Every single ioctl in your application calls GetAdaptersAddresses

Re: ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-20 Thread Jason Curl
On 15/11/2010 17:22, Corinna Vinschen wrote: On Nov 9 09:20, Jason Curl wrote: 166 65418 [main] ipcheck 5580 ioctl: fd 3, cmd 80087364 --- Process 5580, exception C005 at 610C8C86 Crash in Cygwin, but the address doesn't help much, unfortunately. Interestingly enough, the program

ioctl() on socket fd's take 3 seconds on 1.7.7

2010-11-09 Thread Jason Curl
Hello, Cygwin 1.7.7 is definitely an improvement over 1.5.x but I see a regression on 1.7.7 (on Win7 x64) that ioctl() on a socket FD takes 3 seconds. I'm writing my own ifconfig replacement and I do the following: #define IFC_BUF 10 * sizeof(struct ifreq) #define MAX_IFC_BUF

Re: Stack dumps from sh.exe (from within make)

2010-11-09 Thread Jason Curl
Jim Reisert AD1C jjreisert at alum.mit.edu writes: Here is some of the console output: # make wintest g++ -g -Wall -c -o writelog.o writelog.c g++ ctyfiles.o library.o csv.o ct8.o ct9.o mwl.o n3fjp.o na.o wintest.o wpxloc.o writelog.o -o ctyfiles pushd .. ; make cty/entities.csv

Re: Bug in fork() while in a thread

2010-08-21 Thread Jason Curl
Corinna Vinschen corinna-cygwin at cygwin.com writes: On Aug 15 14:53, Christopher Faylor wrote: On Sun, Aug 15, 2010 at 07:42:01PM +0200, Jason Curl wrote: Is it allowed to issue the fork() system call while not in the main thread? When I read the OpenGroup specifications I don't seem

Bug in fork() while in a thread

2010-08-15 Thread Jason Curl
Hello, Is it allowed to issue the fork() system call while not in the main thread? When I read the OpenGroup specifications I don't seem to find anything against allowing this. In particular, if I create a thread, then issue a fork(), data that exists on the stack is corrupted after the

Re: Bug in fork() while in a thread

2010-08-15 Thread Jason Curl
On 15/08/2010 20:53, Christopher Faylor wrote: On Sun, Aug 15, 2010 at 07:42:01PM +0200, Jason Curl wrote: In particular, if I create a thread, then issue a fork(), data that exists on the stack is corrupted after the fork() is in the child. Using data on the heap doesn't show any issues

Re: emacs in its own window

2009-05-21 Thread Jason Curl
Gus K wrote: cygcheck gave the following: Found: C:\cygwin\bin\emacs.exe C:\cygwin\bin\emacs.exe C:\cygwin\bin\cygncurses7.dll C:\cygwin\bin\cygwin1.dll C:\Windows\system32\ADVAPI32.DLL C:\Windows\system32\ntdll.DLL C:\Windows\system32\KERNEL32.DLL

Re: Bash process remains after I close rxvt in certain ways

2006-12-20 Thread Jason Curl
Charles Wilson wrote: rxvt-20050409-4 (e.g. the test version now on the mirrors) also has a common behavior across all three cases, but that behavior is different than the behavior described above. The new rxvt exits and sighups the child (which obligingly goes ahead and dies; no zombies) in

Re: bash, rxvt and interactive shells not exiting as expected

2006-12-20 Thread Jason Curl
Dave Korn wrote: On 19 December 2006 23:43, Jason Curl wrote: Now, AFAICT rxvt should be starting bash as a login shell in interactive mode. When I close the window from RXVT, a SIGHUP should be sent to bash, and according to the manpages from bash this should also cause SIGHUPs to all

bash, rxvt and interactive shells not exiting as expected

2006-12-19 Thread Jason Curl
Dear Cygwin users, I've come across a behaviour that doesn't appear to match the description in the man pages, at least for bash. I have a shell script that starts some non-interactive tasks in the background. This shell script is then executed on startup when a user double clicks on an

Re: read bug in Cygwin xterm window only

2005-06-11 Thread Jason Curl
Christopher Faylor wrote: On Wed, Jun 08, 2005 at 09:22:08PM +0200, Jason Curl wrote: On Fri, Apr 29, 2005 at 05:54:35PM -0700, Peter Farley wrote: The following program demonstrates what looks to me like a bug in the read function in an xterm (as opposed to a Cygwin console window). To run

Re: read bug in Cygwin xterm window only

2005-06-11 Thread Jason Curl
Jason Curl wrote: Christopher Faylor wrote: On Wed, Jun 08, 2005 at 09:22:08PM +0200, Jason Curl wrote: On Fri, Apr 29, 2005 at 05:54:35PM -0700, Peter Farley wrote: The following program demonstrates what looks to me like a bug in the read function in an xterm (as opposed to a Cygwin

Re: read bug in Cygwin xterm window only

2005-06-09 Thread Jason Curl
Peter Farley wrote: Hi all, The following program demonstrates what looks to me like a bug in the read function in an xterm (as opposed to a Cygwin console window). To run the test, compile with: gcc -g -o xtermbug.exe xtermbug.c When you run it in a console window, you can enter normal

Re: what's the difference between File Handle and File Descriptor?

2004-11-28 Thread Jason Curl
news.gosonic.com wrote: Thanks One is high level (streams, file handles) the other is low level (file descriptors). Have a look at the difference between fopen() and open(). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

Re: PATH and SystemRoot oddity

2004-11-27 Thread Jason Curl
Igor Pechtchanski wrote: First off, you could have actually removed the offending entries from the PATH using something like OFFENDING_ENTRY=/cygdrive/c/ClearCase/bin PATH=`echo $PATH | sed s#:$OFFENDING_ENTRY##` Alternatively, if you want to translate any Win32 path to a Cygwin (POSIX) path, use

Cygwin files and devices philosophy

2004-11-27 Thread Jason Curl
Hello, I have a general question for the developers of cygwin. When I open the file \\.\COM37 this is not opened by cygwin as a serial port, but rather as a file. The reasoning (that I'm not disputing) is cygwin should have more of a posix/unix flavour. And so specific functionality to treat

Re: PATH and SystemRoot oddity

2004-11-26 Thread Jason Curl
Brian Dessent wrote: Luke Kendall wrote: I see that by default PATH includes some entries like %SystemRoot%/System32 I also note that $SystemRoot is undefined, yet $SYSTEMROOT contains the expected C:\WINDOWS value. This of course causes problems. Would a backslash-style path work correctly if

Re: PATH and SystemRoot oddity

2004-11-26 Thread Jason Curl
Igor Pechtchanski wrote: On Fri, 26 Nov 2004, Jason Curl wrote: I have a similar question: I had to modify 'profile' to change $PATH=:$PATH to $PATH= How can I simply add $SYSTEMROOT:$SYSTEMROOT/system32 to this? It doesn't work as-is because $SYSTEMROOT = C:\Windows

Re: select() read() and write() on /dev/console

2004-11-23 Thread Jason Curl
Christopher Faylor cgf-no-personal-reply-please at cygwin.com writes: On Mon, Nov 22, 2004 at 05:18:46PM +, Jason Curl wrote: Where is fds[0] defined, so I can see exactly what functions are being called by peek_console, etc.? e.g. fh-get_readahead_valid(); fh-bg_check(SIGTTIN

Re: select() read() and write() on /dev/console

2004-11-22 Thread Jason Curl
Christopher Faylor cgf-no-personal-reply-please at cygwin.com writes: On Fri, Nov 19, 2004 at 06:46:56PM +0100, Jason Curl wrote: My question, how do I go about investigating what the root cause is? Has anybody else seen similar issues and been able to work around it? I'm stuck and I've

Re: select() read() and write() on /dev/console

2004-11-22 Thread Jason Curl
Christopher Faylor cgf-no-personal-reply-please at cygwin.com writes: In dtable::select_{read,write,except} . cgf Where is fds[0] defined, so I can see exactly what functions are being called by peek_console, etc.? e.g. fh-get_readahead_valid(); fh-bg_check(SIGTTIN). Thanks. --

Re: select() read() and write() on /dev/console

2004-11-21 Thread Jason Curl
Christopher Faylor wrote: On Fri, Nov 19, 2004 at 06:46:56PM +0100, Jason Curl wrote: My question, how do I go about investigating what the root cause is? Has anybody else seen similar issues and been able to work around it? I'm stuck and I've never seen the source code to cygwin before. If you

Re: select() read() and write() on /dev/console

2004-11-21 Thread Jason Curl
Christopher Faylor wrote: On Fri, Nov 19, 2004 at 06:46:56PM +0100, Jason Curl wrote: My question, how do I go about investigating what the root cause is? Has anybody else seen similar issues and been able to work around it? I'm stuck and I've never seen the source code to cygwin before. If you

Re: select() read() and write() on /dev/console

2004-11-21 Thread Jason Curl
Christopher Faylor cgf-no-personal-reply-please at cygwin.com writes: On Sun, Nov 21, 2004 at 07:00:42PM +0100, Jason Curl wrote: Christopher Faylor wrote: On Fri, Nov 19, 2004 at 06:46:56PM +0100, Jason Curl wrote: My question, how do I go about investigating what the root cause is? Has

select() read() and write() on /dev/console

2004-11-19 Thread Jason Curl
Hello, I think I might have found a bug with the latest version of cygwin (downloaded one night ago 18Nov2004). I am writing a small terminal emulation software package to interface with an embedded device to perform logging. I use the console (/dev/stdin, /dev/stdout) and a serial port