bash env parse broken

bash env parse broken

[Eric Mills]

on NT4.0sp3 gnu-win32 B18 ... sourcing the following 12 lines into bash:

HOMEPATH="\"
export HOMEPATH
UNAME="NT 4.0"
export UNAME
NEW_RELEASE="28/08/97"
export NEW_RELEASE
TCL_LIBRARY="C:/gnuwin32/b18/tcl/lib/tcl7.6"
export TCL_LIBRARY
PATH=".:/bin:/gnuwin32/b18/H-i386-cygwin32/bin:/gnuwin32/b18/tcl/bin:/WINNT/system32:/WINNT:/msdev/bin:/fax/dev:/fax/dev"
export PATH
GCC_EXEC_PREFIX="C:\gnuwin32\b18\H-i386-cygwin32\lib\gcc-lib\"
export GCC_EXEC_PREFIX

Gives the following:

(C:\bin\sh.exe 5869) In cygwin_except_handler
(C:\bin\sh.exe 5869) Exception trapped!
(C:\bin\sh.exe 5869) exception C0000005 at 10029AD0
(C:\bin\sh.exe 5869) exception: ax 244E234 bx 336E6977 cx 244E2C4 dx 1004762
(C:\bin\sh.exe 5869) exception: si FFFFFFFF di 244E2C4 bp 244E198 sp 244E194
(C:\bin\sh.exe 5869) exception is: STATUS_ACCESS_VIOLATION
(C:\bin\sh.exe 5869) Stack trace:
(C:\bin\sh.exe 5869) frame 0: sp = 0x244DFC8, pc = 0x1000CEC2
(C:\bin\sh.exe 5869) frame 1: sp = 0x244DFE4, pc = 0x77F94512
(C:\bin\sh.exe 5869) frame 2: sp = 0x244E008, pc = 0x77F88EEB
(C:\bin\sh.exe 5869) frame 3: sp = 0x244E094, pc = 0x77F76266
(C:\bin\sh.exe 5869) frame 4: sp = 0x244E198, pc = 0x10016211
(C:\bin\sh.exe 5869) frame 5: sp = 0x244E3C8, pc = 0x433D5849
(C:\bin\sh.exe 5869) In cygwin_except_handler
(C:\bin\sh.exe 5869) Error while dumping state (probably corrupted stack)

If you delete some lines of the above 12 bash gets confused and complains
about unmatched "... and also seems to get in a mode where it ignores and
strips " and tries to run serveral lines as a command name....

I could not see any reference to similar problems anywhere else...

2. Using ^C while make is running produced the following message:
"fork_helper: child died before initialization with win32 error -1073741510"
and sent make into an infinite loop. This seems fairly repeatable.
Perhaps new exception handling in b19 will help... how long to?

Thanks,
Eric Mills.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: bash env parse broken

[Aaron P. Siri]

My first guess is that you aren't escaping your backslashes.  So, for
example, the first line below doesn't see the ending " and all your
variables are running together.  Change all of your \ to \\.  Seems
almost too obvious that maybe I'm overlooking something or misunderstood
the question.

-Aaron


Eric Mills wrote:
> 
> on NT4.0sp3 gnu-win32 B18 ... sourcing the following 12 lines into bash:
> 
> HOMEPATH="\"
> export HOMEPATH
> UNAME="NT 4.0"
> export UNAME
> NEW_RELEASE="28/08/97"
> export NEW_RELEASE
> TCL_LIBRARY="C:/gnuwin32/b18/tcl/lib/tcl7.6"
> export TCL_LIBRARY
> PATH=".:/bin:/gnuwin32/b18/H-i386-cygwin32/bin:/gnuwin32/b18/tcl/bin:/WINNT/system32:/WINNT:/msdev/bin:/fax/dev:/fax/dev"
> export PATH
> GCC_EXEC_PREFIX="C:\gnuwin32\b18\H-i386-cygwin32\lib\gcc-lib\"
> export GCC_EXEC_PREFIX
> 
> Gives the following:
> 
> (C:\bin\sh.exe 5869) In cygwin_except_handler
> (C:\bin\sh.exe 5869) Exception trapped!
> (C:\bin\sh.exe 5869) exception C0000005 at 10029AD0
> (C:\bin\sh.exe 5869) exception: ax 244E234 bx 336E6977 cx 244E2C4 dx 1004762
> (C:\bin\sh.exe 5869) exception: si FFFFFFFF di 244E2C4 bp 244E198 sp 244E194
> (C:\bin\sh.exe 5869) exception is: STATUS_ACCESS_VIOLATION
> (C:\bin\sh.exe 5869) Stack trace:
> (C:\bin\sh.exe 5869) frame 0: sp = 0x244DFC8, pc = 0x1000CEC2
> (C:\bin\sh.exe 5869) frame 1: sp = 0x244DFE4, pc = 0x77F94512
> (C:\bin\sh.exe 5869) frame 2: sp = 0x244E008, pc = 0x77F88EEB
> (C:\bin\sh.exe 5869) frame 3: sp = 0x244E094, pc = 0x77F76266
> (C:\bin\sh.exe 5869) frame 4: sp = 0x244E198, pc = 0x10016211
> (C:\bin\sh.exe 5869) frame 5: sp = 0x244E3C8, pc = 0x433D5849
> (C:\bin\sh.exe 5869) In cygwin_except_handler
> (C:\bin\sh.exe 5869) Error while dumping state (probably corrupted stack)
> 
> If you delete some lines of the above 12 bash gets confused and complains
> about unmatched "... and also seems to get in a mode where it ignores and
> strips " and tries to run serveral lines as a command name....
> 
> I could not see any reference to similar problems anywhere else...
> 
> 2. Using ^C while make is running produced the following message:
> "fork_helper: child died before initialization with win32 error -1073741510"
> and sent make into an infinite loop. This seems fairly repeatable.
> Perhaps new exception handling in b19 will help... how long to?
> 
> Thanks,
> Eric Mills.
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".

-- 
Aaron Siri                          mailto:siri@sgi.com
Cosmo Software                       phone:   (415) 933-3967
A Silicon Graphics Company             fax:   (415) 932-3967
******************* http://cosmo.sgi.com *******************
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: bash env parse broken

[Chet Ramey]

> on NT4.0sp3 gnu-win32 B18 ... sourcing the following 12 lines into bash:
> 
> HOMEPATH="\"
> export HOMEPATH
> UNAME="NT 4.0"
> export UNAME
> NEW_RELEASE="28/08/97"
> export NEW_RELEASE
> TCL_LIBRARY="C:/gnuwin32/b18/tcl/lib/tcl7.6"
> export TCL_LIBRARY
> PATH=".:/bin:/gnuwin32/b18/H-i386-cygwin32/bin:/gnuwin32/b18/tcl/bin:/WINNT/system32:/WINNT:/msdev/bin:/fax/dev:/fax/dev"
> export PATH
> GCC_EXEC_PREFIX="C:\gnuwin32\b18\H-i386-cygwin32\lib\gcc-lib\"
> export GCC_EXEC_PREFIX

You have an unmatched double quote.  The assignment to HOMEPATH
doesn't end until the first double quote after the `UNAME='. 
Backslashes quote double quotes inside double-quoted strings.  I don't
know why bash throws an exception on cygwin32, but on Unix the error
messages are correct.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, Case Western Reserve University	Internet: chet@po.CWRU.Edu
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: bash env parse broken

[Eric Mills]

B18 on NT4.0sp3 NTFS:

Thanks folks for the helpful hint re backslashes: all I can say is
"blind as a bat!" Sorry. I guess on seeing the equivalent of a 'core dump'
from cygwin32.dll I didn't look any further. There still must be a problem
that is not at all obvious with bash that caused the exception....

I would like to follow up on the second point re ^C and make. If you try the
following make file and hit ^C:

all:
	for x in *;\
	do sh -c echo;\
	done >/dev/null

then you will notice a few things:
1.  It never seems to work properly.
2.  More than 50% of the time you get fork_helper: child died message
3.  Less frequently one gets a cygwin_exception_handler message and everything
stops - some sort of deadlock situation - just keep killing bashes till
the world comes back.
4. If you run the same loop straight from bash you get an NT exception poppup
- not caught by cygwin_exception_handler! (or the child died message).

5. Lastly one notices just how SLOW this thing runs - on investigation I 
find that the power up time for bash is somewhere between 5 and 10 times longer
on NT + cygwin32 than UNIX for the identical hardware.
For us new NT users coming from the UNIX environment there should be a warning
statemant in the README file saying that shell script performance is much
less than one is accustomed to!

Would anyone care to comment on where the cycles are going?

Thanks, Eric Mills.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: bash env parse broken

[Alex]

On Tue, 9 Sep 1997, Eric Mills wrote:

> B18 on NT4.0sp3 NTFS:
> 
> Thanks folks for the helpful hint re backslashes: all I can say is
> "blind as a bat!" Sorry. I guess on seeing the equivalent of a 'core dump'
> from cygwin32.dll I didn't look any further. There still must be a problem
> that is not at all obvious with bash that caused the exception....
> 
> I would like to follow up on the second point re ^C and make. If you try the
> following make file and hit ^C:
> 
> all:
> 	for x in *;\
> 	do sh -c echo;\
> 	done >/dev/null
> 
> then you will notice a few things:
> 1.  It never seems to work properly.
> 2.  More than 50% of the time you get fork_helper: child died message
> 3.  Less frequently one gets a cygwin_exception_handler message and everything
> stops - some sort of deadlock situation - just keep killing bashes till
> the world comes back.
> 4. If you run the same loop straight from bash you get an NT exception poppup
> - not caught by cygwin_exception_handler! (or the child died message).

Are you using binary mounts?
 
> 5. Lastly one notices just how SLOW this thing runs - on investigation I 
> find that the power up time for bash is somewhere between 5 and 10 times longer
> on NT + cygwin32 than UNIX for the identical hardware.
> For us new NT users coming from the UNIX environment there should be a warning
> statemant in the README file saying that shell script performance is much
> less than one is accustomed to!
> 
> Would anyone care to comment on where the cycles are going?

Well, I know for one each program (like each instance of sh/bash) has to
do a lot of initalization of different things like Winsock, read the
registry settings and the like.  Trying to configure sendmail will show
how slow shell scripts are, or using GNU's autoconf will do the same.

- alex

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: bash env parse broken

[dahms]

: Has anyone benchmarks for the same H/W running cygwin/UWIN/OpenNT/NutCracker?

Sorry, I forgot to include a real Unix like Linux!


Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: bash env parse broken

[dahms]

Hi Eric, you wrote:

: find that the power up time for bash is somewhere between 5 and 10 times
: longer on NT + cygwin32 than UNIX for the identical hardware.

: Would anyone care to comment on where the cycles are going?

Sacrificed to Bill G's because of the unusable Posix subsystem 8-)
Has anyone benchmarks for the same H/W running cygwin/UWIN/OpenNT/NutCracker?


Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: bash env parse broken

[Bryan T. Schmersal]

At 11:32 AM 9/9/97 est, Eric Mills wrote:
>Would anyone care to comment on where the cycles are going?

I have a quarter that a bunch of the time is going into setting
the window title.  One of the first things I learned about
programming was that output is the most expensive operation.

Bryan
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".