From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-40759-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 17489 invoked by alias); 11 Sep 2005 21:37:01 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 17474 invoked by uid 22791); 11 Sep 2005 21:36:57 -0000
Received: from gateway-1237.mvista.com (HELO av.mvista.com) (12.44.186.158)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 11 Sep 2005 21:36:57 +0000
Received: from [10.0.10.99] (av [127.0.0.1])
	by av.mvista.com (8.9.3/8.9.3) with ESMTP id OAA32067;
	Sun, 11 Sep 2005 14:36:23 -0700
Message-ID: <4324A32B.3010002@mvista.com>
Date: Sun, 11 Sep 2005 21:37:00 -0000
From: Qunying Pan <qpan@mvista.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@false.org>, Michael Snyder <msnyder@redhat.com>
CC: gdb-patches@sources.redhat.com, qunyingpan@gmail.com
Subject: Re: Patch: fix gdb_gcore.sh failure in ash/dash
References: <432240C1.9000308@mvista.com> <4323846C.3090303@redhat.com> <20050911043439.GA20313@nevyn.them.org>
In-Reply-To: <20050911043439.GA20313@nevyn.them.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2005-09/txt/msg00073.txt.bz2

 >> That's creative.  I assume it tests out OK with bash?
Yes, it is OK with bash.

 > Anybody know how portable /dev/stdin is?  I've got no idea, but I'm a
 > bit worried that it won't be portable enough.

It is important to consider the portable. But I am wondering if /dev/null
is having the same portable issue. If /dev/null is okay, then /dev/stdin 
should
be okay too? But I am not very sure about that. Need an expert for an 
advice.

 > It may be simpler to remove the clever bits and use a temporary file.

/dev/stdin here cannot be replaced with a temporary file.
     gdb -batch -x tmpfile >/dev/null<<EOF
     ...
     EOF

gdb reads the input stream from the end-of-file, not from the start 
position.

If /dev/stdin is replaced with tmpfile, the script should be divided into
two parts:
     cat >tmpfile <<EOF
      ...
     EOF
     gdb -batch -x tmpfile >/dev/null

Looks a little bit complicated.

 > I don't suppose you know which fixes the ash problem - the -batch or
the -x?

It only works with the combination of both -batch and -x.