From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-82216-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 27222 invoked by alias); 12 Jul 2011 19:25:51 -0000
Received: (qmail 27214 invoked by uid 22791); 12 Jul 2011 19:25:50 -0000
X-SWARE-Spam-Status: No, hits=-6.9 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 12 Jul 2011 19:25:36 +0000
Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23])	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p6CJPYnG027324	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);	Tue, 12 Jul 2011 15:25:34 -0400
Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199])	by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p6CJPX9O028757;	Tue, 12 Jul 2011 15:25:34 -0400
Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1])	by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p6CJPWlO003834;	Tue, 12 Jul 2011 15:25:33 -0400
From: Tom Tromey <tromey@redhat.com>
To: Abhijit Halder <abhijit.k.halder@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH
References: <CAOhZP9x4GS=_3ShU3=0tKuqGL8K8H=iijh-gHHwRMQETOwhC-Q@mail.gmail.com>	<m37h7od2fk.fsf@fleche.redhat.com>	<CAOhZP9xxssgyoUuv05CVcA8RGkE1sDch+7fBet4dPiqk9fkejw@mail.gmail.com>	<CAOhZP9w83=FF6khgRnmhV8ZfwiNgkhgitJX3tJsk_-=MLG=-4g@mail.gmail.com>
Date: Tue, 12 Jul 2011 19:49:00 -0000
In-Reply-To: <CAOhZP9w83=FF6khgRnmhV8ZfwiNgkhgitJX3tJsk_-=MLG=-4g@mail.gmail.com>	(Abhijit Halder's message of "Tue, 12 Jul 2011 09:54:15 +0530")
Message-ID: <m3liw3gv2r.fsf@fleche.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2011-07/txt/msg00311.txt.bz2

>>>>> "Abhijit" == Abhijit Halder <abhijit.k.halder@gmail.com> writes:

Abhijit> How if we just put a condition check whether the entered string after
Abhijit> pipe (|) is numeric. [...]

(This was dealt with, but I just wanted to find a decent spot to insert
a reply.)

I was too terse yesterday.  The big problem with any generic approach is
that GDB syntax is free-form: each command defines its own syntax.  So,
for any syntax you think up, there is a decent chance that it already
means something to some command, or could.

This doesn't mean it is impossible, just difficult.

We already have "set logging".  This isn't as convenient to use, but it
could certainly be extended to allow pipes.

There is also at least one PR about this in bugzilla.

Tom