On Jan 30 06:12, Eric Blake wrote:
> This sounds like a problem in cygwin 1.5.24 with forking in general on
> xp64 [...]
Yes, my fault. I just uploaded a fixed 1.5.24-2 Cygwin release.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader
Good morning,
Christopher Faylor wrote:
On Tue, Jan 30, 2007 at 08:21:39AM -0800, Glenn Serre wrote:
bash -c /bin/pwd
appears to cause the problem. I have attached strace.out.bz2 that was
created like this:
C:\cygwin\bin>strace bash -c /bin/pwd > strace.out
using the snapshot cygwin1-2006
On Tue, Jan 30, 2007 at 08:21:39AM -0800, Glenn Serre wrote:
>bash -c /bin/pwd
>
>appears to cause the problem. I have attached strace.out.bz2 that was
>created like this:
>
>C:\cygwin\bin>strace bash -c /bin/pwd > strace.out
>
>using the snapshot cygwin1-20061211.dll version of cygwin1.dll.
>
>P
Good morning,
Christopher Faylor wrote:
On Tue, Jan 30, 2007 at 07:12:02AM -0800, Glenn Serre wrote:
Good morning,
Lev Bishop wrote:
On 1/30/07, Glenn Serre wrote:
I have no working patch, I was going to use this problem as an
opportunity for
my first attempt to build and debug the cygwin D
On Tue, Jan 30, 2007 at 07:12:02AM -0800, Glenn Serre wrote:
>Good morning,
>
>Lev Bishop wrote:
>>On 1/30/07, Glenn Serre wrote:
>>>I have no working patch, I was going to use this problem as an
>>>opportunity for
>>>my first attempt to build and debug the cygwin DLL (while maybe even
>>>chargi
Good morning,
Lev Bishop wrote:
On 1/30/07, Glenn Serre wrote:
I have no working patch, I was going to use this problem as an
opportunity for
my first attempt to build and debug the cygwin DLL (while maybe even
charging a
client for it) but it looked to me as if it may already be being
addre
On 1/30/07, Glenn Serre wrote:
I have no working patch, I was going to use this problem as an opportunity for
my first attempt to build and debug the cygwin DLL (while maybe even charging a
client for it) but it looked to me as if it may already be being addressed.
Looking again, I see that this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Daniel Brockman on 1/30/2007 12:20 AM:
>>
>> I installed a new version of cygwin yesterday, and find that bash starts up
> and
>> builtins seem to execute, but when I try the first command, cygwin exits
>> silently.
>> [...]
>> Any hint
Hello again
Sorry to ask for explainations, but since English is not my mother tongue, I
think I may be misunderstanding the point you made :
> 4a. For a single affected script, add this line just after the she-bang:
> (set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
> 4b. For a s
Glenn Serre spiresoftware.com> writes:
>
> Good morning,
>
> I installed a new version of cygwin yesterday, and find that bash starts up
and
> builtins seem to execute, but when I try the first command, cygwin exits
> silently.
> [...]
> Any hints? Should I wait until I can try 3.2.9-11 from
Good evening,
[EMAIL PROTECTED] wrote:
Good morning.
I'm quite happy to find this thread - I thought I was the one who messed things
up... ;^)
I experience exactly the same problem : XP64, recently updated cygwin -> bash
exits with code 128 when trying to execute anything (except builtins, of
Good morning.
I'm quite happy to find this thread - I thought I was the one who messed things
up... ;^)
I experience exactly the same problem : XP64, recently updated cygwin -> bash
exits with code 128 when trying to execute anything (except builtins, of
course). Same thing for gcc (tried from em
Good morning,
Christian Jullien wrote:
I installed a new version of cygwin yesterday, and find that bash starts
up and
builtins seem to execute, but when I try the first command, cygwin exits
This is not related to the new bash version but related to new cygwin
1.5.24-1.
As soon I installed
On Mon, Jan 29, 2007 at 07:31:37AM +0100, Christian Jullien wrote:
> > I installed a new version of cygwin yesterday, and find that bash starts
> up and
> builtins seem to execute, but when I try the first command, cygwin exits
>
>
> This is not related to the new bash version but related to new
> I installed a new version of cygwin yesterday, and find that bash starts
up and
builtins seem to execute, but when I try the first command, cygwin exits
This is not related to the new bash version but related to new cygwin
1.5.24-1.
As soon I installed this new version alone without bash or an
Good afternoon,
Christopher Faylor wrote:
On Sun, Jan 28, 2007 at 02:53:03PM -0800, Glenn Serre wrote:
Good afternoon,
My original email wasn't explicit about the fact that I'm running on 64-bit
XP, but I am.
Also, more info:
- updating to bash 3.2.9-11 didn't help
- using binmode instead o
On Sun, Jan 28, 2007 at 02:53:03PM -0800, Glenn Serre wrote:
>Good afternoon,
>
>My original email wasn't explicit about the fact that I'm running on 64-bit
>XP, but I am.
>
>Also, more info:
>- updating to bash 3.2.9-11 didn't help
>- using binmode instead of textmode as default (and checking mou
Good afternoon,
My original email wasn't explicit about the fact that I'm running on 64-bit XP,
but I am.
Also, more info:
- updating to bash 3.2.9-11 didn't help
- using binmode instead of textmode as default (and checking mounts for /usr/bin
etc) didn't help.
- Bash exit code is 128 (as re
Good morning,
I installed a new version of cygwin yesterday, and find that bash starts up and
builtins seem to execute, but when I try the first command, cygwin exits
silently. By "exits silently" I mean that if I have a cygwin window, it just
disappears. If I am executing bash from a command p
19 matches
Mail list logo
