RE: cygpath hangings: A fix - bash patch enclosed -- bash maintai ner please note!
> -Original Message- > From: Hannu E K Nevalainen > Sent: 18 October 2003 13:22 > Subject: RE: cygpath hangings: A fix - bash patch enclosed -- bash > maintainer please note! > > The simple test works flawlessly. > ditto > I've run my setup-based test with success too. > My gratulations to a task well done. > ditto Nice one cgf, Steve Fairbairn. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup hangs during postinstall
> > >$ ls -l shlwapi.dll msvcrt.dll > >-rwxrwxr-x+ 1 Administ SYSTEM 300816 Oct 20 2000 shlwapi.dll > >-rwxrwxr-x+ 1 Administ SYSTEM 290869 Oct 30 2001 msvcrt.dll > > > >The properties dialogs show the following versions: > > > >File version: 5.50.4522.1800 > >Description: Shell Light-weight Utility Library > >Copyright: Copyright (C) Microsoft Corp. 1981-2000 > > > >File version: 6.1.9359.0 > >Description: Microsoft (R) C Runtime Library > >Copyright: Copyright (C) Microsoft Corp. 1981-1999 > > -rwxrwxr-x+ 1 Administ SYSTEM 395264 Jul 13 16:05 shlwapi.dll > Version 6.00.2800.1226 > > -rwxrwxr-x+ 1 Administ SYSTEM 286773 Jun 19 12:05 msvcrt.dll > Version 6.00.2800.1226 > -rwxrwx---+ 1 Administ SYSTEM 323072 Aug 29 2002 msvcrt.dll Version 6.00.2800.1226 -rwxrwx---+ 1 Administ SYSTEM 395264 Jul 13 16:05 shlwapi.dll Version 7.0.2600.1106 Recently installed, nearly up to date on Windows Update, Windows XP Pro. Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup hangs during postinstall
Again, probably going over old ground but I can't find anywhere that it has actually been stated for those that can't duplicate the problem, that TOPFOLDER="$(cygpath d:/)/Cygwin-XFree86" hangs, but cygpath d:/ doesn't hang? As Brian has noted, Executing the binary with '< /dev/null' stops the hanging, but also executing it without capturing the output to a variable also stops the hanging. Could the capturing of the output somehow give the child process an output stream but no input one? Could something be failing because (going on CreateProcess API) it was told to inherit file descriptors but there isn't a valid input one? I'm just trying to throw questions at anyone in the hope I might stumble across something that makes one of the real geniuses realise what is going on. Please tell me to be quiet if I'm being annoying ;) Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup hangs during postinstall
All, OK, so I tried a lot of things already tried, and at least one thing that hadn't been tried ;). I must admit I haven't followed everything said in the threads so didn't realise we already knew cygpath wasn't actually starting. So, getting this straight in my own head. Setup runs normally. Setup creates a new thread or process to run our bash script - Is this done with sh, then sh runs bash because of the #/bin/bash, or does setup run bash straight? Bash starts up and does some parts of the script. Bash then tries to run cygpath At this point does the cygwin DLL emulates a fork & exec (as windows only has CreateProcess) ? If cygpath isn't starting Does this mean it's still running bash/cygwin1.dll code at the point of the hang? Is it possible to put a nice big sleep into the bash script before the it gets to the cygpath. Attach gdb to bash during this sleep Add a break point to the exec or whatever the function is Continue until breakpoint is hit Step through the whole operation of launching cygpath? Is it possible? Could it potentially be useful? Would we hit Windows internal code that stops us getting to anything useful? Any comments? Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup hangs during postinstall
OK, again with simple tests... I've added a printf to the very start of
main in cygpath.cc...
---
Steve [EMAIL PROTECTED] /etc/postinstall
$ ./setup_from_win.sh
+ CYGWIN_DEBUG=/bin/cygpath
+ set CYGWIN_SLEEP=2
+ echo -e 'CYGWIN_DEBUG=/bin/cygpath\tCYGWIN_SLEEP='
CYGWIN_DEBUG=/bin/cygpath CYGWIN_SLEEP=
++ cygpath -A -P
+ TOPFOLDER=Entered cygpath
/cygdrive/c/Documents and Settings/All Users/Start
Menu/Programs/Cygwin-XFree86
+ echo Entered cygpath /cygdrive/c/Documents and Settings/All Users/Start
Menu/Programs/Cygwin-XFree86
Entered cygpath /cygdrive/c/Documents and Settings/All Users/Start
Menu/Programs/Cygwin-XFree86
---
The 'Entered cygpath' bit is my addition. When this is run via setup
however...
---
Steve [EMAIL PROTECTED] /etc/postinstall
$ tail -11 /var/log/setup.log.full
2003/10/15 13:22:50 running: D:\cygwin\bin\sh.exe -c
/etc/postinstall/setup_from_win.sh
+ CYGWIN_DEBUG=/bin/cygpath
+ set CYGWIN_SLEEP=2
+ echo -e 'CYGWIN_DEBUG=/bin/cygpath\tCYGWIN_SLEEP='
CYGWIN_DEBUG=/bin/cygpath CYGWIN_SLEEP=
++ cygpath -A -P
+ TOPFOLDER=/Cygwin-XFree86
+ echo /Cygwin-XFree86
/Cygwin-XFree86
2003/10/15 13:27:13 mbox note: Nothing needed to be installed
2003/10/15 13:27:14 Ending cygwin install
---
Which implies main isn't even being reached.
I have tried HUP and USR1 as kill signals to cygpath, but it doesn't seem to
handle any signals so all terminate the program in the same way.
I have attached strace to the process once it has hung, but there is no
output until the process recieves a signal from kill and then the output
just seems to be the signal handling/termination (attached anyway).
> -Original Message-
> From: Christopher Faylor
> Sent: 10 October 2003 01:28
> Subject: Re: setup hangs during postinstall
>
> In any event, can you set the CYGWIN_DEBUG=cygpath and maybe do some
> search and destroy debugging to see precisely where it is hanging?
>
I can't get CYGWIN_DEBUG=cygpath to do anything at all, inside bash or from
setup.
>From another email:
> Are you saying that there was no popup? That would imply that
CYGWIN_DEBUG
> is not in the environment. You could just hack on the code in dcrt0.cc to
> automatically pop up a gdb when command line contains cygpath, as a
temporary
> measure, of course.
>
Tried this as well, but I may be ammending the wrong code, or my simple
change isn't good enough...
---
static void __stdcall
build_argv (char *cmd, char **&argv, int &argc, int winshell)
{
int argvlen = 0;
int nesting = 0; // monitor "nesting" from insert_file
argc = 0;
argvlen = 0;
argv = NULL;
if (strstr(cmd, "cygpath"))
{
argvlen = argc + 10;
argv = (char **) realloc (argv, (1 + argvlen) * sizeof (argv[0]));
argv[argc++] = "gdb";
argv[argc++] = "/bin/cygpath.exe";
*cmd = 0;
}
/* Scan command line until there is nothing left. */
while (*cmd)
{
---
The rest of the function is unchanged. When I use cygpath on the command
line in bash, all works as it did before as if my addition doesn't exist. I
did make sure no cygwin processes were running, I did remake and install the
dll, I did copy it into /bin over the top of my existing debugging dll.
I'm running out of random things to prod at in random ways ;)
If any of this is being any use, please let me know. If anyone can tell me
what I'm doing wrong with my attempts above then please yell. If anyone
wants me to try anything else and can explain it well enough for me to do,
then brign it on.
Cheers,
Steve.
--
-- LONG DISCLAIMER --
***
This email has originated from Perwill plc (Registration No. 1906964)
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK
Tel: +44 (0)1420 545000
Fax: +44 (0)1420 545001
www.perwill.com
***
Privileged, confidential and/or copyright information may be contained
in this email, and is only for the use of the intended addressee.
To copy, forward, disclose or otherwise use it in any way if you are not
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately,
by using the reply facility in your email software.
We may monitor the content of emails sent and received via our network
for the purposes of ensuring compliance with policies and procedures.
This message is subject to and does not create or vary any contractual
relationships between Perwill plc and the recipient.
***
Any opinions expressed in the email are those of the sender and not
necessarily of Perwill plc.
***
This email has been scanned for known viruses using
McAfee WebShield 4.5 MR1a
***
5 5 [sig] bash 192! sig_handle: signal 1 processing
186 1
RE: cygpath hangings
> -Original Message- > From: Steve Fairbairn > Sent: 15 October 2003 09:19 > Subject: RE: cygpath hangings > > I ran this first with my normal bash shell, renamed the > output, and then ran > it again from within setup. > > I am attaching the 2 files as they are as well because of the > contents of > one of them, but here is what I see. > > --- > Steve [EMAIL PROTECTED] /cygdrive/d > $ cat path_from_normal > /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/d/v80003 > /data/work/use > rbin:/cygdrive/d/v80003/bin:/cygdrive/c/Program > Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive > /c/WINDOWS:/cy > gdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program > Files/Microsoft Visual > Studio/VC98/Bin:/usr/bin > --- > > --- > Steve [EMAIL PROTECTED] /cygdrive/d > $ cat path_from_setup > /usr/bin:/usr/bin:/usr/bin:/usr/bin:[EMAIL PROTECTED]" > --- > This is slightly false information. The above run from setup was launched using Steve [EMAIL PROTECTED] ~/obj $ cygstart -- W:/Public/Installs/Installs/Cygwin/setup-2.415.exe --no-md5 When instead I double click on 'setup-2.415.exe' I end up with a path very close to my normal bash one. --- Steve [EMAIL PROTECTED] /cygdrive/d $ cat path_from_setup /usr/bin:/usr/bin:/usr/bin:/usr/bin:/cygdrive/d/v80003/data/work/userbin:/cy gdrive/d/v80003/bin:/cygdrive/c/Program Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cy gdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/Bin:/usr/bin --- Maybe tryig to debug this issue by using cygstart is giving false leads? Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** path_from_setup Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: cygpath hangings
All, As a side note, I have 11 copies of that DLL (java dev and runtime, Visual Studio/Source Safe, ...) on my system, but only the system32 one is in my normal path. Someone mentioned something about possible issues to do with the path being different, so I thought I'd run a quick test. --- $ cat setup_from_win.sh.done #!/bin/bash -x # CYGWIN_DEBUG=/bin/cygpath # set CYGWIN_SLEEP=2 echo $PATH > /cygdrive/d/path_from_setup --- I ran this first with my normal bash shell, renamed the output, and then ran it again from within setup. I am attaching the 2 files as they are as well because of the contents of one of them, but here is what I see. --- Steve [EMAIL PROTECTED] /cygdrive/d $ cat path_from_normal /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/d/v80003/data/work/use rbin:/cygdrive/d/v80003/bin:/cygdrive/c/Program Files/j2sdk1.4.2_01/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cy gdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/Bin:/usr/bin --- --- Steve [EMAIL PROTECTED] /cygdrive/d $ cat path_from_setup /usr/bin:/usr/bin:/usr/bin:/usr/bin:[EMAIL PROTECTED]" --- Could this be something to do with it all? Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** path_from_normal Description: Binary data path_from_setup Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup hangs during postinstall
All, Just trying to either re-enforce or counter Brian's debug info, I have done the same thing Chris requested of him with my hung cygpath process. (gdb) info threads 3 thread 164.0xd88 0x77f75a59 in ntdll!DbgUiConnectToDbg () from /cygdrive/c/WINDOWS/System32/ntdll.dll 2 thread 164.0x118 0x7ffe0304 in ?? () * 1 thread 164.0x124 0x7ffe0304 in ?? () Thread 1 (gdb) l *0x61092939 0x61092939 is in muto::acquire(unsigned long) (../../../../src/winsup/cygwin/sync.cc:75). (gdb) l *0x6108da76 0x6108da76 is in WFMO (../../../../src/winsup/cygwin/sigproc.cc:1248). (gdb) l *0x61092b50 0x61092b50 is in close_all_files() (../../../../src/winsup/cygwin/syscalls.cc:102). (gdb) l *0x6108fffd 0x6108fffd is in spawn_guts(char const*, char const* const*, char const* const*, int) (../../../../src/winsup/cygwin/spawn.cc:847). Thread 2 (gdb) l *0x610f1f20 No source file for address 0x610f1f20. (gdb) l *0x6108d2f6 0x6108d2f6 is in wait_sig(void*) (../../../../src/winsup/cygwin/sigproc.cc:1089). (gdb) l *0x610a39fb 0x610a39fb is in pthread_key::set(void const*) (../../../../src/winsup/cygwin/thread.cc:1386). (gdb) l *0x610efdb8 No source file for address 0x610efdb8. (gdb) l *0x610efdb8 (Yes there was 2 of them) No source file for address 0x610efdb8. Thread 3 None. HTH, Steve Fairbairn -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup hangs during postinstall
con 11125 16:27:56 /usr/bin/rxvt 2064 4482064 20801 11125 16:27:56 /usr/bin/bash 274420642744 27561 11125 16:28:01 /usr/bin/ps -- I'm hoping this is relevant to the people in the know. As you can see, the cygpath process ID according to this ps has nothing to do with 1736. So, instead I have attached gdb to the process 164 reported here. This is giving me a prompt, and I'm sure I can type lots of commands, but my gdb knowledge is very limited and I don't know what I can request that could be of any use. My cygwin1.dll and cygpath binaries were built using 'make CFLAGS_FOR_TARGET=-g CFLAGS=-g > make.log 2>&1' so hopefully has all the debug information wanted. I'm leaving everything as is, in case anyone has a set of commands they'd like run in gdb. HTH, Steve Fairbairn Just for completeness I'll attach the cygcheck requested in the normal problem reports. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: cygpath hangings
> -Original Message- > From: Cliff Hones > Sent: 14 October 2003 15:03 > Subject: Re: cygpath hangings > > Running > cygcheck -vs (and/or some other such utility) from > a hanging and non-hanging postinstall shell might come > up with something. > As in set up a script in /etc/postinstall that runs cygcheck -vs to a file, and send that in? Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: cygpath hangings
> From: chris > Sent: 14 October 2003 13:33 > Subject: Re: cygpath hangings > > Corinna Vinschen wrote: > > > > >Nope, not for me. Are you, by any chance, still using gcc2? > > > > > Nope, using gcc 3.3.1 (cygming special) > > Just checking... have you been suffering from the "cygpath" crashing > during setup? If not I imagine that you wouldn't have any > problems with > this, as it is just a (very!) cutdown cygpath. > > Just checking (although sorry if I'm being stupid). Can > someone else who > is having the cygpath crash check they get a crash from this too? > Chris & All, I dare say Corinna has a fair idea of what the code is, and whether she has experienced the hanging problems ;). I have suffered from the hanging cygpath issue, I did a clean install (new box) and have since not changed the installation. If you could supply me with an exe for this code (private email) or the flags used when building that code and a description of how to make setup run it (as I've not actually gleaned that information from the mails on the subject), I will be glad to see if I can cause the issue to happen. I am currently getting the cygwin sources out of cvs, but due to work firewall being quite strict I'm having to get them via an ssh tunnel to my home server (ADSL) so could be quite some time. Does anyone know if I want to update my gcc before attempting to build the DLL with debug on (gcc version 3.2 20020927 (prerelease))? Cheers, Steve Fairbairn. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Setup 2.358 Hangs During Post-Install Script
> -Original Message- > From: Scott > Sent: 28 September 2003 00:08 > To: steve fairbairn > Subject: RE: Setup 2.358 Hangs During Post-Install Script > > > Thanks for the great tip. I had the exact same problem, and your solution seems to work perfectly. But being brand > new to Cygwin, what did I just accomplish by killing the cygpath PID? > > Thanks, > Scott Edwards Hi Scott, Please don't email anyone from the cygwin mailing list directly. All responses should go to the list. I am assuming from your response that you are also new to the UNIX world, but apologies if this assumption is incorrect. The way we used the cygwin kill command (kill -9 ) is just like the 'End Process' button in Windows Task Manager when you are looking at the processes tab. Kill can by used for a lot more than just stopping the process execution, but when I was trying to get around the issue I was being fairly heavy handed. Try reading man pages (man kill) to find out more. As for our specific killing of cygpath... There is some kind of issue with the post install script you identified that means it never completes. As I identified and you have confirmed, the actual part of the script that isn't completing properly is the cygpath program. As I haven't examined the script at all, I can't tell you what cygpath is being used for, why it should fail to complete in the way it does or what effect our killing it had on the general succes of that script. All I can say is that I haven't found any ill effects with my installation but have not used X11 at all yet. Hope this helps, Steve Fairbairn -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Install gets to 99% and then stops
> -Original Message- > From: Rick Price > Sent: 26 September 2003 13:17 > Subject: Install gets to 99% and then stops > > > In trying to install Cygwin on a Windows 2K laptop and an XP > Pro laptop, my > install goes well until I get to 99%. It continues to say that it is > running and the task manager agrees but nothing is happening. > The file > shown is /etc/postinstall/XFree86-bin-icons.sh with the > progress bar showing > it to be about 80% done. > > If anyone else has seen this behaviour or has any ideas on the > cause and how > serious it is, please let me know. One notebook is a Toshiba > Tecra 8100 and > the other is a new HP. > Do you google? RE: Setup 2.358 Hangs During Post-Install Script http://www.cygwin.com/ml/cygwin/2003-09/msg00747.html Steve Fairbairn. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Copying an executable from network drive without .exe extension f ails.
Friends, <-- Now there's the start of a spam mail if ever I saw one ;) I've searched archives and found a couple of potentially related messages, but none I've found seem to quite match the behaviour I'm seeing. This appears to be new behaviour in ?1.5.x? that worked as I expected it to when still on a 1.3.x version (sorry, can't remember which it was, and don't have that machine in work today to check). I have a script which is going through a list of file names and testing they exist before copying them. If the file doesn't exist, the script appends ..exe onto the end of the name and tests again (not sure if this is needed for cygwin, but certainly is for MKS Toolkit). echo "program" >> ../bins.lst $P_WINDOWS='//dev2k/d/dev/product/bin' cat ../bins.lst | while read file do if [ -f $P_WINDOWS/$file ] then cp $P_WINDOWS/$file WIN/ else if [ -f $P_WINDOWS/$file.exe ] then cp $P_WINDOWS/$file.exe WIN/ else echo "H:$P_WINDOWS/$file doesn't exist" >> WIN.res fi fi done I am actually running the script while I've cd'd onto a network share, so both source and destination drives are on the network, but two separate machines. At the time the above script is executed, the destination directory does exist and is empty. The source directory does exist and does contain an .exe version of the 'program'. The error produced is as follows... cp: `//dev2k/d/dev/product/bin/program' and `WIN/program' are the same file To get around the problem, I've checked for the .exe version first and then the non .exe version, but I thought it should be reported. The potentially related messages I found are... Re: cp -p fails with .exe files http://www.cygwin.com/ml/cygwin/2001-06/msg01210.html ACL or file locking issue? http://www.cygwin.com/ml/cygwin/2003-07/msg00950.html cp error -- oh the great sanity of *nix tools?! ... http://www.cygwin.com/ml/cygwin/2001-06/msg01364.html RE: 1.3.5 cp/permissions bug http://www.cygwin.com/ml/cygwin/2001-11/msg01423.html Cheers, Steve Fairbairn. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Setup 2.358 Hangs During Post-Install Script
> > Setup claims to be trying to run a script called > > /etc/postinstall/XFree86-bin-icons.sh, which is a symlink to > > /usr/X11R6/bin/XFree86-bin-icons.sh. > > > > After cancelling setup, I can still run Cygwin and XFree86 (phew.) > > > > Any ideas, please? Hi all, I've just installed cygwin on my new machine (WOO HOO Finally) - install from local directory, package files were downloaded yesterday morning (UK), install everything. The post install scripts hung as above, but instead of cancelling the install, I decided to see if I could just do enough to free up the issue. I went into the bin directory under the new installation, and ran bash.exe with a double click. No paths seemed to be set up, so to run ps I had to use ./ps but here is what I saw... bash-2.05b$ ./ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 1260 11260 1260 con 11125 10:25:27 /usr/bin/sh 400412601260 4004 con 11125 10:25:27 /usr/bin/sh I187640041260 1876 con 11125 10:25:27 /usr/bin/bash 217218761260 2172 con 11125 10:25:27 /usr/bin/bash 41221721260412 con 11125 10:25:27 /usr/bin/cygpath 2732 12732 2732 con 11125 10:40:49 /usr/bin/bash 344427323444 3356 con 11125 10:41:21 /usr/bin/ps As I thought the cygpath looked a little out of place, I ran ps again to ensure it was still there... bash-2.05b$ ./ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 1260 11260 1260 con 11125 10:25:27 /usr/bin/sh 400412601260 4004 con 11125 10:25:27 /usr/bin/sh I187640041260 1876 con 11125 10:25:27 /usr/bin/bash 217218761260 2172 con 11125 10:25:27 /usr/bin/bash 41221721260412 con 11125 10:25:27 /usr/bin/cygpath 2732 12732 2732 con 11125 10:40:49 /usr/bin/bash 349627323496 3468 con 11125 10:41:23 /usr/bin/ps And then killed it... bash-2.05b$ kill -9 412 The setup continued and seems to have completed successfully. Everything seems to be working OK. I thought I'd send in this report in case it's of use tracking down the issue. Cheers, Steve Fairbairn -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: mozilla displays wrong headers from uw-imap (12/31/1969, blan k subject)
> > The Mail/MIME encoding RFC's state that all headers > should be CRLF no matter what the platform. > I've just been trying to confirm the above statement and am struggling. I am certain about the MIME headers, but am less certain about the mail ones having to be CRLF (though I don't see how one can be without the other). If I am incorrect (and I will continue to try and find the right RFC) then I apologise. Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: mozilla displays wrong headers from uw-imap (12/31/1969, blan k subject)
Apologies to Hannu, I clicked reply and not reply to all... > -Original Message- > From: Hannu E K Nevalainen (garbage mail) > Subject: RE: mozilla displays wrong headers from uw-imap (12/31/1969, > blank subject) > > > > Of Mr. Ali Nabavi > > Fetchmail gets my mail via pop3 and sends them to either > tmail or dmail > > (I've used both.) The logs look just fine, but says "bare > LF only" and > > I don't know if that is a problem. The mail ends up where > the uw-imap > > readme says it will, in /var/mail/. I log in successfully > > with both Mozilla and Pegasus Mail and the messages have > blank headers > > except for the date, which is 12/31/1969. When I open the > messages, the > > headers look okay, the date and time are accurate, but moving the > > message to another folder corrupts the message and, it appears, only > > moves the body over, not the headers. > > I'm no expert, but to me this looks as fetchmail and the > other (cygwin!) > tools uses LF line endings (Unix style). While Mozilla and > Pegasus Mail > (Windows executables most likely) expect it to be the Windows > way (i.e. > CR+LF). > > IMO a Mozilla and/or Pegasus Mail bug. > Not definately true. The Mail/MIME encoding RFC's state that all headers should be CRLF no matter what the platform. It is open to dispute quite whether the RFC's should still apply once the mail has finished it's journey through the ether and has been collected from the email server by such a tool as fetchmail. It seems likely that Mozilla is expecting the CRLF's to remain on the headers which would probably be true if Mozilla was collecting the emails itself. It is my guess that fetchmail is stripping the CR's from the message as it retrieves it which could well be the accepted practice for UNIX boxes, but under a cygwin text mount it should perhaps behave differently. This is purely speculation I've not looked at the sources, but it is certainly true that the pop3 server should be presenting the headers with CRLF line endings to the client. HTH, Steve Fairbairn. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Strange setup problem. Next button disabled.
Hi All, I have a couple of strange setup problems which I cannot find ways around, so was wondering if anyone might be able to suggest solutions. The machine in question is a PIII 650MHz running a very new installation of Win2K Pro. During the machines installation, cygwin was installed from a local (network drive) directory as the network Administrator user. It was incorrectly installed to the same network drive and subdirectory of the setup files, using the default setup settings. This installation was wiped from the network drive in question. Any mention of Cygnus was wiped from the registry. A clean installation of cygwin was started. When installing as a machine administrator, but normal network user. From local directory (the same network drive), setup does all the md5 checks, offers me the package list, allows me to change the Default/Install/Reinstall/... settings, but the 'Next' button is permanently disabled and I just can't click on it. So, I tried download & install from the internet. This allows me to go all the way through, select the packages I require (set All to install, then set X11 section back to default), and then I am able to click next. The installation starts. I leave it going overnight/all day/ a few hours, and when I return to it, it has hung in the post install scripts and if I cancel installation there, the cygwin.bat file hasn't been created, and nothing seems quite right. I've cleaned cygwin off the system again, but really do need an almost full installation of cygwin on the machine and don't know how to get it. I have tried the setup.exe on the main page, as well as snapshots 2.402 and 2.407 with no improvement in either case (though the snapshots are faster to respond and the handling of the post install scripts is much nicer). The packages I have on the network drive were downloaded from ftp://ftp.mirror.ac.uk/sites/sources.redhat.com/pub/cygwin using a slightly modified version of the wget script mkcygwget (can't remember who created it) to get a complete set of packages. Any suggestions gratefully received, Steve. PS Apologies for the spam below. -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Bash 2.05 not reading my ~/.bashrc
> -Original Message- > From: Schulze, Dean > > I checked the mail archives for this problem before posting but found > nothing of any help. A search engine that uses boolean logic > (or something > like Google) would help a lot. > Dean, Use Google and restrict the searches to the cygwin.com domain then. It works wonderfully. Steve. -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Respond ASAP
> -Original Message- > From: Gary R. Van Sickle [mailto:[EMAIL PROTECTED] > Sent: 04 June 2003 15:24 > > Now, if we can only come up with a few tens of thousands in > cash, and of course > avoid attracting the attention of the Unbelievable Sucker > Euthanasia Squads, > that Nigerian scratch is practically ours! > > ;-) > She forgot the bit about sending that few tens of thousands to me though, so I thought I'd better let you know where to send it. Just drop me a private email, and I'll send you the details required to deposit money into my bank account. Thanks for continuing to keep this all quiet. Steve -- -- LONG DISCLAIMER -- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Advocacy
> -Original Message- > From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] > Sent: 03 March 2003 17:13 > > "--LONG DISCLAIMER--"?.. Seems like a wonderful solution to me... ~Steve. --LONG DISCLAIMER-- *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Why the rash of people bypassing setup.exe to install?
I can't really offer much comment on this, as I do still use setup.exe to actually install the packages. But one thing I have noticed recently, and I'm sure someone reported it as a bug, is that setup regularly fails to download all packages successfully. Once download is completed and we move on to installing from local directory (I always do the process in 2 steps due to maintaining a local copy of cygwin install set for my workplace), then setup comes up with a few errors along the lines of 'Cannot locate (NULL) package' (purely from memory, can't duplicate it without trying to download the whole lot again). My current solution is to use that wonderful wget script someone handily provided to get the packages to a local directory, and then use setup to install from there. Could it be that people have encountered the same/a similar error, and chosen to attempt a totally manual installation? HTH, Steve. *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: CygWin Installation
> -Original Message- > From: Peter A. Castro [mailto:[EMAIL PROTECTED]] > > On Fri, 31 Jan 2003, Steve Fairbairn wrote: > > > I assume you never did an early slackware linux install then. > > You considder the early Slackware installs difficult, eh?? > Hah! Those > were easy (I did many an install of the early Slackware from floppy > images (and I still like & use Slackware today!)). Try > installing some > of the early AIX's on early RS/6000 hardware, or better yet, AIX V2 on > the IBM PC/RT's (and yes, I did/do both). > I was merely trying to suggest he'd led a sheltered computer related life. I also did many slackware installs from floppy (well, the same install many times ;). Which first required vast use of gopher to download and email me the packages in small pieces so that I could get it with my Uni account. Then transfered home on double density floppies (720KB) to try and get installed on my Amiga - Bloody worked too. Kids today. They don't know they're born ;) Steve. *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: CygWin Installation
I assume you never did an early slackware linux install then. Steve. -Original Message- From: subensky [mailto:[EMAIL PROTECTED]] Sent: 31 January 2003 15:59 To: [EMAIL PROTECTED] Subject: CygWin Installation In over 30 years of computer/it experience I have never seen anything as convoluted and difficult to use as your CygWin download/installer. Sy Bensky [EMAIL PROTECTED] *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: cygwin Release process
How cliquey? I reckon us outsiders should make a mass exodus if Christopher *in-most-mother-esq-tone-I-can-manage* fails to explain himself. -Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: 24 January 2003 15:34 Actually, in a way, I guess I did say it. cgf (inside joke) *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Bug in rm -r with locked files
Just a small suggestion, but in order to avoid this problem and keep cross platform compatibility, could you not recursively chmod the files first, then use rm -r (which someone else stated isn't affected) to remove the files. Means the tree has to be parsed twice, but should produce the required results? Steve. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Subject: Re: Bug in rm -r with locked files use rm -rf in a script and must resort to the native "del" cmd because rm -rf hangs when it encounters a locked file. *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: KEIL to SDCC
I have no idea what SDCC or KEIL are, but the 3rd error is likely cause by
the lack of prototype for printf. If the implicit declaration of printf is
along the lines of printf("blah");, then the compiler will assume the
function to only take 1 parameter and not a va_args list.
Sort out error 2, and error 3 will probably vanish too.
Sorry I can't help with the more difficult parts of your email.
Steve.
-Original Message-
From: Karthik Bala Guru [mailto:[EMAIL PROTECTED]]
Sent: 17 December 2002 15:06
To: [EMAIL PROTECTED]
Subject: KEIL to SDCC
Hi all,
I think i can post about SDCC doubts here !!!
I have thought of using SDCC rather than the
KEIL cross compiler.
I have some errors that i get when i run the
KEIL program in SDCC .
1) FL.c : 96 parse error : taken -> ' ' : column 0
The above error occurs in line 96 which
is not present in the program and is indeed the
line next to the last line of my program ...
What is the problem actually ? solution plz !
2) warning : function 'printf' implicit declaration
what is this warning ? why this ?? i have
inclued stdio.h
3) error : too many paramaters .
I get the above error for the line
printf("%f", mine1) . what is it ? what is the
solution ?
Do reply and solve these tiny problems.
Thanx in advance
karthik bala guru
[EMAIL PROTECTED]
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
***
This email has originated from Perwill plc (Registration No. 1906964)
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK
Tel: +44 (0)1420 545000
Fax: +44 (0)1420 545001
www.perwill.com
***
Privileged, confidential and/or copyright information may be contained
in this email, and is only for the use of the intended addressee.
To copy, forward, disclose or otherwise use it in any way if you are not
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately,
by using the reply facility in your email software.
We may monitor the content of emails sent and received via our network
for the purposes of ensuring compliance with policies and procedures.
This message is subject to and does not create or vary any contractual
relationships between Perwill plc and the recipient.
***
Any opinions expressed in the email are those of the sender and not
necessarily of Perwill plc.
***
This email has been scanned for known viruses using
McAfee WebShield 4.5 MR1a
***
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
RE: cd accepting paths with trailing dots that don't exist (bash and tcsh)
Corinna & All, After a play with a dos command prompt, I see your point. I would however point out that there is still a difference with bash. If you have more than one trailing . in bash, the 'directory' it puts you in is empty, and you cannot create any files in there. Also bash seems to retain the trailing dots as part of your cwd, which the dos prompt doesn't do. With the dos prompt, it just seems to strip the trailing dots off, and always leave you in the directory you trailed with dots. As for "correct functionality" I meant whatever the cygwin developers define as correct. My personal preference would be for bash to complain about the trailing dots, but I understand that the shell probably just uses the Windows OS chdir function, and so it is Windows deciding the path is valid. Would there be massive overhead in bash re-reading the cwd after a successful chdir, and so not display the dots? How come ls etc doesn't work if there is more than one trailing dot? Thanks, Steve. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: 10 December 2002 15:33 To: '[EMAIL PROTECTED]' Subject: Re: cd accepting paths with trailing dots that don't exist (bash and tcsh) On Tue, Dec 10, 2002 at 09:47:10AM -, Steve Fairbairn wrote: > I've just come across some very strange (to me at least) results with the cd > command in both bash and tcsh under cygwin (1.3.17-1). I have cut and paste > from my shell as I feel it would be easier for you to read it yourself. > > I don't have any aliases set. The output is all from bash, but tcsh seemed > to do exactly the same thing. > > I apologise if this is correct functionality, but the suse box I tried this > on complained bitterly at the lack of blah... etc existing. Define "correct functionality". Honestly, it's a Windows thingy. Windows allows any number of trailing dots for a path or file name. Go figure! Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
FW: cygwin 1.3.17-1 gethostbyname() leak
Sorry, it decided not to reply to the list for some reason.
-Original Message-
From: Steve Fairbairn
Sent: 10 December 2002 08:57
To: 'Noel Gordon'
Subject: RE: cygwin 1.3.17-1 gethostbyname() leak
I can confirm it loses about 8k every sample of the Win2k Pro task manager
performance monitor - PIII 800MHz. It doesn't seem to be the scroll buffer
or anything like that, and it is all free'd by ?Windows? when the program is
terminated. Also removing the call to gethostbyname() and leaving a similar
printf doesn't give the same issue so it does appear to be gethostbyname()
that is doing it.
Cheers,
Steve Fairbairn
-Original Message-
From: Noel Gordon [mailto:[EMAIL PROTECTED]]
Sent: 10 December 2002 08:49
To: [EMAIL PROTECTED]
Subject: cygwin 1.3.17-1 gethostbyname() leak
Anyone else confirm that the following program compiled under
gcc 3.2, cygwin 1.3.17-1, on Win2k leaks memory?
/*---*/
#include
#include
int main()
{
struct hostent *host;
while ( 1 )
{
if ( ( host = gethostbyname( "localhost" ) ) != NULL )
printf( "gethostbyname(): %s\n", host->h_name );
}
}
***
This email has originated from Perwill plc (Registration No. 1906964)
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK
Tel: +44 (0)1420 545000
Fax: +44 (0)1420 545001
www.perwill.com
***
Privileged, confidential and/or copyright information may be contained
in this email, and is only for the use of the intended addressee.
To copy, forward, disclose or otherwise use it in any way if you are not
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately,
by using the reply facility in your email software.
We may monitor the content of emails sent and received via our network
for the purposes of ensuring compliance with policies and procedures.
This message is subject to and does not create or vary any contractual
relationships between Perwill plc and the recipient.
***
Any opinions expressed in the email are those of the sender and not
necessarily of Perwill plc.
***
This email has been scanned for known viruses using
McAfee WebShield 4.5 MR1a
***
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
cd accepting paths with trailing dots that don't exist (bash and tcsh)
Hi All, I've just come across some very strange (to me at least) results with the cd command in both bash and tcsh under cygwin (1.3.17-1). I have cut and paste from my shell as I feel it would be easier for you to read it yourself. I don't have any aliases set. The output is all from bash, but tcsh seemed to do exactly the same thing. I apologise if this is correct functionality, but the suse box I tried this on complained bitterly at the lack of blah... etc existing. Cheers, Steve. Steve Fairbairn@STEVE_FAIRBAIRN ~ $ ls 1.txt ERRLEVEL auto expect pbtrc01 tst.ctst2.exe 2.txt MESSAGES.txt bin makecd.sh pbtsp01 tst.exe vimfiles Downloads _viminfo ctnohup.out test.exe tst2.c work Steve Fairbairn@STEVE_FAIRBAIRN ~ $ cd ct Steve Fairbairn@STEVE_FAIRBAIRN ~/ct $ ls data Steve Fairbairn@STEVE_FAIRBAIRN ~/ct $ cd .. Steve Fairbairn@STEVE_FAIRBAIRN ~ $ cd ct. Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ ls data Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ cd ../ct. Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ ls data Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ cd ../ct.. Steve Fairbairn@STEVE_FAIRBAIRN ~/ct.. $ ls Steve Fairbairn@STEVE_FAIRBAIRN ~/ct.. $ cd ../ct....... Steve Fairbairn@STEVE_FAIRBAIRN ~/ct... $ cd .. Steve Fairbairn@STEVE_FAIRBAIRN ~ $ cd ct..... Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ cd .. Steve Fairbairn@STEVE_FAIRBAIRN ~ $ ls -lda * -rw-rw-rw-1 Steve Fa unknown 30849 Dec 5 08:28 1.txt -rw-rw-rw-1 Steve Fa unknown 29561 Dec 5 08:29 2.txt drwxrwxrwx+ 2 Administ unknown 0 Nov 18 16:07 Downloads -rwxrwxrwx1 Steve Fa unknown 4 Nov 28 14:36 ERRLEVEL -rwxrwxrwx1 Steve Fa unknown 290 Nov 28 14:36 MESSAGES.txt -rwxrwxrwx1 Administ unknown 4978 Nov 22 17:14 _viminfo drwxrwxrwx+ 2 Steve Fa unknown 4096 Oct 3 09:40 auto drwxrwxrwx+ 2 Steve Fa unknown 0 Oct 3 09:58 bin drwxrwxrwx+ 3 Steve Fa unknown 0 Oct 3 09:26 ct drwxrwxrwx+ 2 Administ unknown 0 Nov 26 10:02 expect -rwxr-xr-x1 Steve Fa unknown 131 Nov 28 10:55 makecd.sh -rw---1 Steve Fa unknown 0 Nov 25 16:10 nohup.out -rw-rw-rw-1 Steve Fa unknown 1905211 Nov 22 08:41 pbtrc01 -rw-rw-rw-1 Steve Fa unknown 1910937 Nov 22 11:20 pbtsp01 -rwxrwxrwx1 Steve Fa unknown 49152 Nov 25 09:53 test.exe -rw-rw-rw-1 Steve Fa unknown 379 Nov 29 10:20 tst.c -rwxrwxrwx1 Steve Fa unknown 19722 Nov 29 10:20 tst.exe -rw-rw-rw-1 Steve Fa unknown 158 Dec 10 08:54 tst2.c -rwxrwxrwx1 Steve Fa unknown 19071 Dec 10 08:54 tst2.exe drwxrwxrwx+ 10 Administ unknown 0 Oct 3 10:26 vimfiles lrwxrwxrwx1 Steve Fa unknown 112 Nov 22 11:38 work -> d:/w32/data/work Steve Fairbairn@STEVE_FAIRBAIRN ~ $ cd ct. Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ pwd /home/Steve Fairbairn/ct. Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ ls Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ echo blah >blah bash: blah: No such file or directory Steve Fairbairn@STEVE_FAIRBAIRN ~/ct. $ *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
FW: Problem with Cygwin DLL: 1003.15.0.0 & 1003.16.0.0
Hi all, As noone responded to this, and I have since seen minor complaints of not enough information being given, is there anything further I can do to assist in the location and repair of this problem? I have upgraded to 1003.17.0.0 and ensured the problem is also in this version of the dll. Do I have to reboot after upgrade, if the dll has been changed (Win2K)? Thanks, Steve. -Original Message- From: Steve Fairbairn [mailto:[EMAIL PROTECTED]] Sent: 25 November 2002 13:07 To: '[EMAIL PROTECTED]' Subject: Problem with Cygwin DLL: 1003.15.0.0 & 1003.16.0.0 Hi, I have come across a problem with cygwin which relates to the Windows CreateProcess() function. Tested on Cygwin DLLs: 1003.15.0.0 & 1003.16.0.0 Windows 2000 sp3 I have a Visual C++ program which uses CreateProcess to launch an executable much like the example provided in the attachment. The example has been hard coded to execute a cygwin compiled binary (ls) as this is what I was attempting to do in the real thing. When the program is run from a dos command prompt, it all works perfectly. However when the program is run from cygwin bash, the launched program (ls) fails with a read exception somewhere in the cygwin dll. If the program is changed to execute a non cygwin-built binary, it all seems to work fine. I also bring your attention to the following lines from the example... /* Something to do with bInheritHandles being FALSE, as when it is TRUE, it works. */ CreateProcess(0, cmd, 0, 0, FALSE, DETACHED_PROCESS | NORMAL_PRIORITY_CLASS, 0, cwd, &StartupInfo, &ProcessInformation); When the CreateProcess call is changed so handles are inherited, it all works perfectly. If this is the wrong place to report an issue like this, then please let me know where I should email instead. I couldn't spot any other likely candidates. Regards, Steve Fairbairn. <> PS. Full VC++ Workspace and binaries are available, I just didn't want to attach it on a mail to the whole list. PPS. Apologies for the disclaimer, nothing I can do to stop it :(. -- ^^ Vain attempt to fake a proper signature start so hopefully some people will automatically trim it off. *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Problem with Cygwin DLL: 1003.15.0.0 & 1003.16.0.0
Hi, I have come across a problem with cygwin which relates to the Windows CreateProcess() function. Tested on Cygwin DLLs: 1003.15.0.0 & 1003.16.0.0 Windows 2000 sp3 I have a Visual C++ program which uses CreateProcess to launch an executable much like the example provided in the attachment. The example has been hard coded to execute a cygwin compiled binary (ls) as this is what I was attempting to do in the real thing. When the program is run from a dos command prompt, it all works perfectly. However when the program is run from cygwin bash, the launched program (ls) fails with a read exception somewhere in the cygwin dll. If the program is changed to execute a non cygwin-built binary, it all seems to work fine. I also bring your attention to the following lines from the example... /* Something to do with bInheritHandles being FALSE, as when it is TRUE, it works. */ CreateProcess(0, cmd, 0, 0, FALSE, DETACHED_PROCESS | NORMAL_PRIORITY_CLASS, 0, cwd, &StartupInfo, &ProcessInformation); When the CreateProcess call is changed so handles are inherited, it all works perfectly. If this is the wrong place to report an issue like this, then please let me know where I should email instead. I couldn't spot any other likely candidates. Regards, Steve Fairbairn. <> PS. Full VC++ Workspace and binaries are available, I just didn't want to attach it on a mail to the whole list. PPS. Apologies for the disclaimer, nothing I can do to stop it :(. *** This email has originated from Perwill plc (Registration No. 1906964) Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK Tel: +44 (0)1420 545000 Fax: +44 (0)1420 545001 www.perwill.com *** Privileged, confidential and/or copyright information may be contained in this email, and is only for the use of the intended addressee. To copy, forward, disclose or otherwise use it in any way if you are not the intended recipient or responsible for delivering to him/her is prohibited. If you receive this email by mistake, please advise the sender immediately, by using the reply facility in your email software. We may monitor the content of emails sent and received via our network for the purposes of ensuring compliance with policies and procedures. This message is subject to and does not create or vary any contractual relationships between Perwill plc and the recipient. *** Any opinions expressed in the email are those of the sender and not necessarily of Perwill plc. *** This email has been scanned for known viruses using McAfee WebShield 4.5 MR1a *** test.c Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
