Re: Bad address error with redirection (stdout and stderr) in background process
Greetings, Heiko Elger! looks like there was a second snapshot later the same day that replaced the one you had installed. That's it! Thanks a lot .. I never see a snapshot released twice a day Just one question: How can I figure out whether a snapshot is released more than once a day? Date... md5... -- WBR, Andrey Repin (anrdae...@freemail.ru) 16.01.2012, 17:45 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On 16/01/2012 06:47, Heiko Elger wrote: Dave Korn gmail.com writes: looks like there was a second snapshot later the same day that replaced the one you had installed. That's it! Thanks a lot .. I never see a snapshot released twice a day Just one question: How can I figure out whether a snapshot is released more than once a day? Well, if ... - you download a snapshot - you find a bug - you report it and discuss it on the list - cgf says he's just created a snapshot to fix your bug ... you can infer by pure logic alone that he's not talking about the snapshot that was uploaded *before* you reported your bug. You can also look at the hours and minutes in the timestamp listed on http://cygwin.com/snapshots/ as well as the date and compare it to the one you downloaded earlier in the day. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On Mon, Jan 16, 2012 at 06:47:51AM +, Heiko Elger wrote: Dave Korn gmail.com writes: looks like there was a second snapshot later the same day that replaced the one you had installed. That's it! Thanks a lot .. I never see a snapshot released twice a day It happens all of the time. Sometimes it happens several times a day. Just one question: How can I figure out whether a snapshot is released more than once a day? http://cygwin.com/ml/cygwin/2012-01/msg00181.html cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
Dave Korn gmail.com writes: looks like there was a second snapshot later the same day that replaced the one you had installed. That's it! Thanks a lot .. I never see a snapshot released twice a day Just one question: How can I figure out whether a snapshot is released more than once a day? regards Heiko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
Christopher Faylor writes: If you are saying that the problem is not fixed in the most recent snapshot then please clearly say that. Otherwise, I don't understand what you are asking. I sent my email on January 11 shortly before the January 11 snapshot was uploaded. There is no reason for you to expect a newer snapshot than that. In my first posting concerning this problem I posted tne used snapshot too (20110111) I'm using latest snapshot and updated cygwin installation. $ uname -a CYGWIN_NT-6.1-WOW64 PCFX166 1.7.10s(0.259/5/3) 20120111 01:45:50 i686 Cygwin I've done rebaseall and peflagsall. So I already used teh snapshot of January 11th. best regards Heiko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On 15/01/2011 19:41, Heiko Elger wrote: Christopher Faylor writes: If you are saying that the problem is not fixed in the most recent snapshot then please clearly say that. Otherwise, I don't understand what you are asking. I sent my email on January 11 shortly before the January 11 snapshot was uploaded. There is no reason for you to expect a newer snapshot than that. In my first posting concerning this problem I posted tne used snapshot too (20110111) I'm using latest snapshot and updated cygwin installation. $ uname -a CYGWIN_NT-6.1-WOW64 PCFX166 1.7.10s(0.259/5/3) 20120111 01:45:50 i686 Cygwin I've done rebaseall and peflagsall. So I already used teh snapshot of January 11th. http://cygwin.com/snapshots/ currently says 2012-01-11 22:44:48 UTC, so it looks like there was a second snapshot later the same day that replaced the one you had installed. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
Christopher Faylor writes: ? The snapshot that I was referring to was created shortly after my above email went out. oops - but the only snapshot I see on the cygwin page http://cygwin.com/snapshots/ is dated 20120111. I cannot see a newer snapshot? Heiko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On Fri, Jan 13, 2012 at 12:28:19PM +, Heiko Elger wrote: Christopher Faylor writes: ? The snapshot that I was referring to was created shortly after my above email went out. oops - but the only snapshot I see on the cygwin page http://cygwin.com/snapshots/ is dated 20120111. I cannot see a newer snapshot? If you are saying that the problem is not fixed in the most recent snapshot then please clearly say that. Otherwise, I don't understand what you are asking. I sent my email on January 11 shortly before the January 11 snapshot was uploaded. There is no reason for you to expect a newer snapshot than that. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
Christopher Faylor writes: No need to answer that. The upcoming snapshot should fix the problem. I forgot to say: Thanks for the simple test case. Those are always much appreciated. thanks a lot for your great work. Is it possible to create a new snapshot til monday? best regards Heiko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On Fri, Jan 13, 2012 at 05:32:02AM +, Heiko Elger wrote: Christopher Faylor writes: No need to answer that. The upcoming snapshot should fix the problem. I forgot to say: Thanks for the simple test case. Those are always much appreciated. thanks a lot for your great work. Is it possible to create a new snapshot til monday? ? The snapshot that I was referring to was created shortly after my above email went out. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bad address error with redirection (stdout and stderr) in background process
Hello, I'm using latest snapshot and updated cygwin installation. $ uname -a CYGWIN_NT-6.1-WOW64 PCFX166 1.7.10s(0.259/5/3) 20120111 01:45:50 i686 Cygwin I've done rebaseall and peflagsall. I've found the following problem using make in parallel (-j) with multiple commands joined with semicolon (;) using cygwin and non-cygwin(cross compiler) commands. # just an example test.o: test.c echo compile ; cross-gcc -c test.c -o test.o Having multiple targets like this and using for example $ make -j8 | tee make.log you will get a bad address error. /bin/sh: cross-gcc.exe: Bad address makefile:10: recipe for target `test.o' failed I stripped down the problem to the following testcase: $ cat ./testcase.sh #!/bin/sh (( echo 123 ; cmd /c echo 456 ) | tee tee.log ) executing the testcase will produce thr following output: $ ./testcase.sh $ 123 ./testcase.sh: line 2: /cygdrive/c/Windows/system32/cmd: Bad address If only redirecting stdout to tee all works fine. The problem occurs ony while mixing cygwin and non cygwin programs. Using snapshot 20110829 all works fine. Any ideas? best regards heiko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On Wed, Jan 11, 2012 at 03:05:26PM +, Heiko Elger wrote: Hello, I'm using latest snapshot and updated cygwin installation. $ uname -a CYGWIN_NT-6.1-WOW64 PCFX166 1.7.10s(0.259/5/3) 20120111 01:45:50 i686 Cygwin I've done rebaseall and peflagsall. I've found the following problem using make in parallel (-j) with multiple commands joined with semicolon (;) using cygwin and non-cygwin(cross compiler) commands. # just an example test.o: test.c echo compile ; cross-gcc -c test.c -o test.o Having multiple targets like this and using for example $ make -j8 | tee make.log you will get a bad address error. /bin/sh: cross-gcc.exe: Bad address makefile:10: recipe for target `test.o' failed I stripped down the problem to the following testcase: $ cat ./testcase.sh #!/bin/sh (( echo 123 ; cmd /c echo 456 ) | tee tee.log ) executing the testcase will produce thr following output: $ ./testcase.sh $ 123 ./testcase.sh: line 2: /cygdrive/c/Windows/system32/cmd: Bad address If only redirecting stdout to tee all works fine. The problem occurs ony while mixing cygwin and non cygwin programs. Using snapshot 20110829 all works fine. Any ideas? Do I infer from the above that you rigorously tried all snapshots through August and that was the first that worked or (more likely) you haven't tried a snapshot since August and now noticed a problem? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On Wed, Jan 11, 2012 at 10:20:21AM -0500, Christopher Faylor wrote: On Wed, Jan 11, 2012 at 03:05:26PM +, Heiko Elger wrote: Hello, I'm using latest snapshot and updated cygwin installation. $ uname -a CYGWIN_NT-6.1-WOW64 PCFX166 1.7.10s(0.259/5/3) 20120111 01:45:50 i686 Cygwin I've done rebaseall and peflagsall. I've found the following problem using make in parallel (-j) with multiple commands joined with semicolon (;) using cygwin and non-cygwin(cross compiler) commands. # just an example test.o: test.c echo compile ; cross-gcc -c test.c -o test.o Having multiple targets like this and using for example $ make -j8 | tee make.log you will get a bad address error. /bin/sh: cross-gcc.exe: Bad address makefile:10: recipe for target `test.o' failed I stripped down the problem to the following testcase: $ cat ./testcase.sh #!/bin/sh (( echo 123 ; cmd /c echo 456 ) | tee tee.log ) executing the testcase will produce thr following output: $ ./testcase.sh $ 123 ./testcase.sh: line 2: /cygdrive/c/Windows/system32/cmd: Bad address If only redirecting stdout to tee all works fine. The problem occurs ony while mixing cygwin and non cygwin programs. Using snapshot 20110829 all works fine. Any ideas? Do I infer from the above that you rigorously tried all snapshots through August and that was the first that worked or (more likely) you haven't tried a snapshot since August and now noticed a problem? No need to answer that. The upcoming snapshot should fix the problem. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Bad address error with redirection (stdout and stderr) in background process
On Wed, Jan 11, 2012 at 02:14:41PM -0500, Christopher Faylor wrote: On Wed, Jan 11, 2012 at 10:20:21AM -0500, Christopher Faylor wrote: On Wed, Jan 11, 2012 at 03:05:26PM +, Heiko Elger wrote: I stripped down the problem to the following testcase: $ cat ./testcase.sh #!/bin/sh (( echo 123 ; cmd /c echo 456 ) | tee tee.log ) executing the testcase will produce thr following output: $ ./testcase.sh $ 123 ./testcase.sh: line 2: /cygdrive/c/Windows/system32/cmd: Bad address If only redirecting stdout to tee all works fine. Do I infer from the above that you rigorously tried all snapshots through August and that was the first that worked or (more likely) you haven't tried a snapshot since August and now noticed a problem? No need to answer that. The upcoming snapshot should fix the problem. I forgot to say: Thanks for the simple test case. Those are always much appreciated. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
