From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31163 invoked by alias); 18 Dec 2006 05:46:10 -0000 Received: (qmail 31155 invoked by uid 22791); 18 Dec 2006 05:46:09 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.netapp.com (HELO mx2.netapp.com) (216.240.18.37) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 18 Dec 2006 05:46:05 +0000 Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2.netapp.com with ESMTP; 17 Dec 2006 21:46:04 -0800 X-IronPort-AV: i="4.12,181,1165219200"; d="scan'208"; a="12878207:sNHT14943082" Received: from siml12.eng.netapp.com (siml12-fe.eng.netapp.com [10.56.9.163]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id kBI5k3Xl029531; Sun, 17 Dec 2006 21:46:03 -0800 (PST) Received: from siml12.eng.netapp.com (localhost.localdomain [127.0.0.1]) by siml12.eng.netapp.com (8.12.5/8.12.5) with ESMTP id kBI5k3HR032507; Sun, 17 Dec 2006 21:46:03 -0800 Received: (from steverod@localhost) by siml12.eng.netapp.com (8.12.5/8.12.5/Submit) id kBI5jw3R032503; Sun, 17 Dec 2006 21:45:58 -0800 Date: Mon, 18 Dec 2006 05:46:00 -0000 From: Steve Rodrigues To: Eli Zaretskii , steverod@netapp.com, gdb-patches@sources.redhat.com Subject: Re: [patch] Indirect access to GDB history variables Message-ID: <20061218054558.GB27035@siml12.eng.netapp.com> References: <20061215024050.GA8750@linden.netapp.com> <20061216171025.GB14012@nevyn.them.org> <20061216184508.GA17120@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061216184508.GA17120@nevyn.them.org> User-Agent: Mutt/1.4i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-12/txt/msg00227.txt.bz2 Daniel Jacobowitz wrote on Sat, Dec 16, 2006 at 01:45:08PM -0500: > > > I think that we should take the long-postponed jump to embedding > > > scripting languages, rather than adding more complexity to the existing > > > CLI. > > ...[further discussion]... I assume that with the embedded scripting language, you'd allow input in a 'interpreted' fashion; i.e. at the gdb prompt I could enter a Perl or Python or Guile command directly, accessing (for example, with Perl) @history or $history[$i]? Would the embedded language support current CLI scripts or not? I.e. if I have Perl-GDB, can I run my existing GDB scripts or only Perl-ized versions of them? (We have quite a large pile and migrating them to something else probably won't happen, at least in any reasonable timeframe.) > -- > Daniel Jacobowitz > CodeSourcery Thanks, --Steve -- Steven Rodrigues | Lost, yesterday, somewhere between sunrise and Member of Technical Staff | sunset, two golden hours, each set with sixty Network Appliance Corp. | diamond minutes. No reward is offered, for they steverod@netapp.com | are gone forever. -- Horace Mann