Message-ID:	<350C33D5.6298@EnchantedLearning.com>
Date:	Sun, 15 Mar 1998 12:02:30 -0800
From:	Mitchell Spector <spector AT EnchantedLearning DOT com>
Reply-To:	spector AT EnchantedLearning DOT com
Organization:	Enchanted Learning Software
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	HANRIGOU Philippe <HANRIGOU AT cgste DOT mq>, djgpp AT delorie DOT com
Subject:	Re: Problem with bash
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980315150435 DOT 9708J-100000 AT is>

Eli Zaretskii wrote:
> 
> On Thu, 12 Mar 1998, Mitchell Spector wrote:
> 
> > I just downloaded bash, and I'm having exactly the same problem.
> > (I've had no difficulties at all with djgpp.)  I'm running
> > Windows 95 version 4.00.950a, with "Microsoft Plus! for Windows 95".
> > bash hangs for me in the same way as has been described here.  If I
> > start up in DOS, though, bash seems to work fine.
> 
> Please post the same system information that Philippe posted.  I would
> like to look for common peculiarities in your two configurations.

See below.  I appreciate your looking at this.


> > What I noticed was that if I type 16 characters
> > (getting no apparent response at all), the system then starts to beep
> > at each character typed, as if I had exceeded the length of an
> > input buffer.
> 
> That would mean that Bash is busy-waiting, stuck in some endless loop
> waiting for something.  But the BIOS keyboard handler still works,
> which is why you get the beeps when the keyboard typeahead buffer
> fills.

Yes, but what I found slightly strange was that the buffer filled
up after only 16 characters.

bash does seem to be busy-waiting.  If I launch System Monitor in
Windows 95 and view the processor usage, it zooms up to 100% when
bash hangs, and it stays at 100% until I hit ctrl-break.

One thing is different from what Philippe described.  After I terminate
bash via ctrl-break, I find that my DOS box (within which I entered
bash) has also hung.  On his machine, DOS hung for a few seconds
and then was back to normal, but on my machine it's just dead; it's
not busy-waiting since the processor usage goes back down to a low
level.  On the other hand, Windows 95 appears to be OK.  Even while
bash is just sitting there, I can switch to other windows in Win95.
(And I was able to copy the traceback information displayed after
the ctrl-break, pasting it into another document, even though the DOS
box it was in was completely unresponsive to input.) 

> 
> > The other thing that might be related is that I'm quite low on
> > hard drive space.  go32-v2 executed within bash reports:
> > DPMI memory available: 9335 Kb
> > DPMI swap space available: 13065 Kb
> 
> This is not low enough to expect problems in Bash.

As for the other things you asked about, I tried bash both
with LFN=n and with LFN=y, with the same effect.  I compiled
a simple C program to read from the keyboard and write to the
screen using getchar and printf, and it ran under DOS with no
problem.  (I've used gcc extensively with no problems, but I
did want to be sure that nothing had changed.)

Someone else mentioned that they were running Retrospect and COPStalk.
I'm not running these.  I just have a stock Windows 95 installation
(4.00.950a -- I gather the "a" means that Service Pack 1 was included
-- with Microsoft "Plus!"), together with the DJGPP package and a set
of the Unix-style utilities that I downloaded at the same time I
downloaded bash.  (These utilities seem to work fine from DOS.
I've tried sed and gawk, which are probably the most complex of
the utilities.)

Within bash, I can run both built-in commands and regular DOS
executables (like XCOPY) without difficulty.  It seems to be
just djgpp executables that cause bash to hang.



Here are the tracebacks.  I ran bash three different times, doing
different things each time, so I have three different tracebacks
that can be compared.


Traceback 1:

bash$ Exiting due to signal SIGSEGV
General Protection Fault at eip=000420e5
eax=000000ae ebx=00004050 ecx=0000ffff edx=0003ffe8 esi=00000928
edi=00067414
ebp=0016092e esp=00000fec program=C:\DJGPP\BIN\BASH.EXE
cs: sel=00a7  base=83074000  limit=ff147fff
ds: sel=0000
es: sel=00b7  base=83074000  limit=ff147fff
fs: sel=00bf  base=00000000  limit=ffffffff
gs: sel=00bf  base=00000000  limit=ffffffff
ss: sel=01ab  invalid

Call frame traceback EIPs:
  0x000420e5


Traceback 2:

bash$ Exiting due to signal SIGSEGV
General Protection Fault at eip=000420e5
eax=000000ae ebx=00004050 ecx=0000ffff edx=0003ffe8 esi=00000928
edi=00067414
ebp=00fd092e esp=00000fec program=C:\DJGPP\BIN\BASH.EXE
cs: sel=00a7  base=8219c000  limit=ffff4fff
ds: sel=0000
es: sel=00b7  base=8219c000  limit=ffff4fff
fs: sel=00bf  base=00000000  limit=ffffffff
gs: sel=00bf  base=00000000  limit=ffffffff
ss: sel=01ab  invalid

Call frame traceback EIPs:
  0x000420e5


Traceback 3:

bash$ Exiting due to signal SIGSEGV
General Protection Fault at eip=000420e5
eax=000000ae ebx=00004050 ecx=0000ffff edx=0003ffe8 esi=00000928
edi=00067414
ebp=011d092e esp=00000fec program=C:\DJGPP\BIN\BASH.EXE
cs: sel=00a7  base=8219c000  limit=fffeafff
ds: sel=0000
es: sel=00b7  base=8219c000  limit=fffeafff
fs: sel=00bf  base=00000000  limit=ffffffff
gs: sel=00bf  base=00000000  limit=ffffffff
ss: sel=022b  invalid

Call frame traceback EIPs:
  0x000420e5


Thanks again for your willingness to check this out.

Mitchell
--
Mitchell Spector, Enchanted Learning Software
E-mail: spector AT EnchantedLearning DOT com
Visit http://www.EnchantedLearning.com --
our award-winning children's web site.

- Raw text -