From:	Martin Ambuhl <mambuhl AT earthlink DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	bash 2.03 & segfaults
Date:	Thu, 01 Apr 1999 20:37:43 -0500
X-Posted-Path-Was:	not-for-mail
X-Accept-Language:	en
X-ELN-Date:	2 Apr 1999 01:36:59 GMT
X-ELN-Insert-Date:	Thu Apr 1 17:45:06 1999
Organization:	Nocturnal Aviation
Lines:	22
Mime-Version:	1.0
NNTP-Posting-Host:	2cust41.tnt11.nyc3.da.uu.net
Message-ID:	<37041F67.C423693D@earthlink.net>
X-Mailer:	Mozilla 4.51 [en] (Win95; I)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I don't know ehat relevant information to include here, but I will
describe the basic problem.  I'm sure someone will direct me properly
about what I have omitted that might be useful.

bash1.47 executable is in /djgpp/bin/bash.exe
bash2.03 executable is in /djgpp/bin/bash2.exe

There are 2 batch files, boot.bat to start bash1.47
boot203.bat which is identical to boot.bat, but with 
'bash2.exe --login' replacing 'bash.exe -login'

If I start bash1.47 from Win95 through boot.bat, I have no problems.
If I start bash1.47 from Win95 through boot.bat, then invoke bash2.03
through boot203.bat, I have no problem.
If I start bash2.03 from Win95 through boot203.bat, any djgpp program --
for example ls -- immediately segfaults and aborts bash.

Does anyone have a clue here?

-- 
Martin Ambuhl (mambuhl AT earthlink DOT net)
Note: mambuhl AT tiac DOT net will soon be inactive

- Raw text -