X-Authentication-Warning: new-smtp2.ihug.com.au: Host p57-max9.syd.ihug.com.au [203.173.156.249] claimed to be acceleron
Message-ID: <00d301c14f27$e42feef0$0a02a8c0@acceleron>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: <djgpp-workers AT delorie DOT com>, "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
References: <000001c14f21$6aae2fc0$578ce0d5 AT pandora DOT be>
Subject: Re: Interesting bash bug (2.04, WinME)
Date: Sun, 7 Oct 2001 22:02:07 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Reply-To: djgpp-workers AT delorie DOT com

Tim,

I just tried your example with the Bash 2.04 that I hacked to work on Win 2K
which I just re-built today using LIBC from a few days ago and it worked
without a problem. The bash that I used should be available from
http://clio.rice.edu/djgpp/win2k/main.htm in about 20 minutes if all goes
well. The bash.exe that I used is dated 07/10/2001  09:44p and is 1,568,805
bytes. You may want to download the bash binary file from clio and see if it
works, but please note that read in this version seems to NOT wait for a CR
before exiting the read function. I may still have some debug printfs in it
as I am still trying to find out why read fails.

DJGPP_204 D:\dj204>bash --version
GNU bash, version 2.04.7(1)-release (i686-pc-msdosdjgpp)
Copyright 1999 Free Software Foundation, Inc.

DJGPP_204 D:\dj204>bash -c './foo a b'
./foo a b

DJGPP_204 D:\dj204>edit foo                << Added Testing start and
Testing end lines in foo

DJGPP_204 D:\dj204>bash -c './foo a b'
Testing start
./foo a b
Testing end



Andrew

----- Original Message -----
From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Sent: Sunday, October 07, 2001 9:15 PM
Subject: Interesting bash bug (2.04, WinME)


> The simple shell script below works fine, except if run
> using
> bash -c './foo a b'
> (using more or fewer args works!)
>
> 'foo':
> echo $0 "$@"
>
> F:\Tmp>bash -c './foo a b'
> ./foo a b
> free: called with already freed block argument
> Stopping myself...Abort!
> Exiting due to signal SIGABRT
> Raised at eip=00052154
> eax=0018d538 ebx=00000120 ecx=00000000 edx=00000000 esi=001943ac
> edi=001943a0
> ebp=0018d5e4 esp=0018d51c program=F:\DJGPP\BIN\BASH.EXE
> cs: sel=00a7  base=846b7000  limit=0019ffff
> ds: sel=00af  base=846b7000  limit=0019ffff
> es: sel=00af  base=846b7000  limit=0019ffff
> fs: sel=0087  base=00016940  limit=0000ffff
> gs: sel=00bf  base=00000000  limit=0010ffff
> ss: sel=00af  base=846b7000  limit=0019ffff
> App stack: [0018d88c..0008d88c]  Exceptn stack: [0008d270..0008b330]
>
> Call frame traceback EIPs:
>   0x00052073
>   0x00052154
>   0x00056be4
>   0x00013e1f
>   0x00049d01
>   0x0000f65e
>   0x0000ecf1
>   0x0000c5b4
>   0x0002cf57
>   0x00002fd0
>   0x000023db
>   0x00051054
>
>