Message-Id: <3.0.16.19980212114013.2bf77afe@hem1.passagen.se> Date: Thu, 12 Feb 1998 11:40:18 -0500 To: Eli Zaretskii From: Peter Palotas Subject: Re: Bash crashing! Cc: djgpp AT delorie DOT com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Precedence: bulk At 11.53 1998-02-12 +0200, you wrote: > >On Wed, 11 Feb 1998, Peter Palotas wrote: > >> I have a problem with BASH. Very often when I try to run configure scripts >> from within BASH it crashes (SIGSEGV), however it works fine if I run it >> from the DOS command prompt like "bash configur". > >There is no significant differences in Bash operation between batch >and interactive modes. Although I mostly run Bash in batch mode, it >does work for me to run configure scripts interactively as well. Okay, guess some more information would be neccessary then. DOS version is 6.2 and windows version is 3.11. Enough space IS available on the directory pointed to by TEMP (both in environment and in DJGPP.ENV). Bash version reports: GNU bash, version 1.14.7(1) r3 w/multibyte extension (The size and date are the same as you mentioned in another post a couple of days ago). Okay, now from the GNU Hello 1.3 package (as downloaded from a the simtel mirror at ftp.sunet.se today) when trying to run configure from within bash in a DOS box from withing windows I get the following: bash$ ./configure bash: (null): Invalid argument (EINVAL) When trying to run configure from within bash in plain DOS I get the following (not so nice) message: bash$ ./configure Exiting due to signal SIGSEGV Page fault at eip=0000a1ba, error=0004 eax=00181900 ebx=00181900 ecx=ffffffff edx=00000000 esi=00000000 edi=00000000 ebp=0016b6e8 esp=0016b6d4 program=D:\CODING\DJGPP\BIN/bash.exe cs: sel=00e7 base=10060000 limit=0019ffff ds: sel=00ef base=10060000 limit=0019ffff es: sel=00ef base=10060000 limit=0019ffff fs: sel=00ff base=00000000 limit=ffffffff gs: sel=00ff base=00000000 limit=ffffffff ss: sel=00ef base=10060000 limit=0019ffff Call frame traceback EIPs: 0x0000a1ba 0x0000e55c 0x0000e6cf 0x0000e30e 0x0000d9b5 0x0000c6cb 0x0000bd9d 0x000027b8 0x000020f2 0x00041dc6 However, if I from the DOS prompt in plain DOS do the following, everything seems to work fine; [d:\coding\djgpp\gnu\hello-1.3>]bash ./configure checking for gcc checking how to run the C preprocessor checking for install checking for ANSI C header files checking for string.h checking for fcntl.h checking for sys/file.h checking for working alloca.h checking for alloca checking stack direction for C alloca checking whether cross-compiling creating config.status creating Makefile > - does Bash crash every time you run that script, or only > sometimes? I guess the answer to this must be NO, since it doesn't CRASH under windows 3.11. > - are you sure all programs invoked by Bash (like `sed', `grep', > `mv' etc.) are DJGPP ports? I haven't installed anything else, so I'm as sure as one can get I suppose! >Of course, configure scripts cannot usually run on DOS (or on Windows >95, for that matter) without some editing. That is why I asked which >script(s) did you run. But Bash shouldn't crash even if you didn't >edit the script, it will just fail in several places. Yes, maybe the script won't work anyway, but I still don't think bash should crash!