From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18281 invoked by alias); 16 May 2006 03:32:24 -0000 Received: (qmail 17655 invoked by uid 22791); 16 May 2006 03:30:23 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 16 May 2006 03:29:51 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 5333E48CD99; Mon, 15 May 2006 23:29:49 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22258-01-4; Mon, 15 May 2006 23:29:49 -0400 (EDT) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 076CD48CCB2; Mon, 15 May 2006 23:29:49 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 4F14847E7F; Mon, 15 May 2006 20:29:47 -0700 (PDT) Date: Tue, 16 May 2006 12:39:00 -0000 From: Joel Brobecker To: Jim Blandy Cc: pgilliam@us.ibm.com, Eli Zaretskii , Fabio De Bona , gdb@sources.redhat.com Subject: Re: conditional breakpoint with (char* ) string condition Message-ID: <20060516032947.GR6718@adacore.com> References: <44645774.8060503@gmx.net> <20060512124527.GB3460@nevyn.them.org> <20060512135420.GA6349@nevyn.them.org> <1147446332.3672.51.camel@dufur.beaverton.ibm.com> <20060515145842.GB28447@nevyn.them.org> <20060515191808.GB5918@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00233.txt.bz2 > I guess I feel like we're encroaching on the user's space no matter > what we do, so we might as well make it terse. And there are are $_ > variables defined by GDB already, I think. But I'd be happy with '_' > or 'gdb_'. I prefer $gdb_ to $_. It's not so much more typing and I find it clearer. -- Joel