From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7826 invoked by alias); 18 Jul 2005 18:30:07 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7812 invoked by uid 22791); 18 Jul 2005 18:30:03 -0000 Received: from mta03.pge.com (HELO mta03.pge.com) (131.89.129.73) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 18 Jul 2005 18:30:03 +0000 Received: from mta13.comp.pge.com (mta13.comp.pge.com [10.245.211.128]) by mta03.pge.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j6IIU0T6001369 for ; Mon, 18 Jul 2005 11:30:00 -0700 (PDT) Received: from mdssdev05.comp.pge.com (mdssdev05.comp.pge.com [10.244.96.61]) by mta13.comp.pge.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j6IIU0ZZ019925 for ; Mon, 18 Jul 2005 11:30:00 -0700 (PDT) Received: (from esp5@localhost) by mdssdev05.comp.pge.com (8.11.7p1+Sun/8.11.7) id j6IITwp17137 for gdb@sources.redhat.com; Mon, 18 Jul 2005 11:29:59 -0700 (PDT) Date: Mon, 18 Jul 2005 18:30:00 -0000 From: Ed Peschko To: gdb@sources.redhat.com Subject: intelligent history and memory for gdb Message-ID: <20050718182958.GA17100@mdssdev05.comp.pge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-SW-Source: 2005-07/txt/msg00192.txt.bz2 hey all, I've been playing around with gdb, noticed a couple of things that I'd really like to have, and was wondering if they'd been implmented. First, I have the setting: bindkey -k up history-search-backward bindkey -k down history-search-backward in my .tcshrc, and was wondering if gdb has an equivalent. This allows me to type: mak then up arrow, to see all the list of commands that I've typed in my history that start with 'mak', instead of just forgetting that I've typed 'mak' and going back to the last typed command (like gdb does by default). Second, I'd like the ability of gdb to 'remember' the programs that I've edited, so the next time I run gdb with that executable, all the commands/definitions that I've typed in previous sessions with that executable are retrieved. I'm thinking that this could be done by md5'ing the executable and its name, and then storing the commands in a buffer that gets recalled when a new session with that executable starts. A list of these stored sessions could be gotten by a catalog command (something like 'ls') and an import command could be used to retrieve any prior session to tie it to the current session, ie: (gdb) ls stored sessions: 1) mutt: 2) perl: (gdb) import 1 importing history from session #1... (gdb) Now I'm not really up on my gdb development, but how much of this has been implemented? And what do people think? I know that this would at least make me about 5 times as efficient with gdb... Thanks much, Ed (ps - this may be a dup, if so please bear with me and ignore it...)