Path: csiph.com!feeder.erje.net!2.us.feeder.erje.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!171.64.64.130.MISMATCH!usenet.stanford.edu!not-for-mail From: Robert Elz Newsgroups: gnu.bash.bug Subject: Re: Arm machine does not execute background statement correctly Date: Thu, 01 Mar 2018 05:10:35 +0700 Lines: 51 Approved: bug-bash@gnu.org Message-ID: References: <46653602-7efa-9e3c-b477-4d22118fd22a@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: usenet.stanford.edu 1519855921 4102 208.118.235.17 (28 Feb 2018 22:12:01 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org To: chet.ramey@case.edu Envelope-to: bug-bash@gnu.org In-Reply-To: <46653602-7efa-9e3c-b477-4d22118fd22a@case.edu> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2001:3c8:9009:181::2 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:13778 Date: Wed, 28 Feb 2018 09:03:45 -0500 From: Chet Ramey Message-ID: <46653602-7efa-9e3c-b477-4d22118fd22a=40case.edu> I didn't see the proginal of this message either, but ... =7C On 2/28/18 5:31 AM, Lakshman Garlapati wrote: =7C =7C > The following snippet is working fine in x86 processor machine no= t working =7C > in arm processor machine from bash 4.3 version onwards. =7C >=20 =7C > test.sh =7C > =3D=3D=3D=3D=3D =7C > =23=21/bin/bash =7C > rm out.txt =7C > function abc() =7B =7C > =A0 if =5B 2 -eq 1 =5D; then =7C > =A0 echo =22TRUE=22 =7C > else =7C > echo =22FALSE=22 =7C > fi =7C > =7D =7C > abc & =7C >=20 =7C > bash -x test.sh =7C > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =7C > + rm -f out.txt =7C > + abc =7C > + '=5B' 2 -eq 1 '=5D' =7C > + echo TRUE <---- Here we are expecting FALSE =7C > TRUE =7C >=20 =7C > please provide some guidance on how to resolve the problem, let m= e know if =7C > problem statement is not clear. It appears as if something odd is up there, the =22rm out.txt=22 has been= executed=20 as =22rm -f out.txt=22 so either there are aliases involved somewhere, in= which case there is a =24ENV type script with unknown contents, or the script that i= s being tested isn't the script shown. In either case, whatever happened needs to be discovered and understood before looking for other possible bugs. kre