From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21356 invoked by alias); 2 Jan 2003 19:13:23 -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 21311 invoked from network); 2 Jan 2003 19:13:20 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by 209.249.29.67 with SMTP; 2 Jan 2003 19:13:20 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 545ED3DE5; Thu, 2 Jan 2003 19:13:09 +0000 (GMT) Message-ID: <3E148F45.5020502@redhat.com> Date: Thu, 02 Jan 2003 19:13:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Felix Lee Cc: gdb@sources.redhat.com Subject: Re: target-dependent .gdbinit References: <200301021851.h02IpaZ24996@paper-wolf-solo.tigerfood.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00024.txt.bz2 > Andrew Cagney : > >> how about something like: >> (gdb) eval source ~/.gdbinit-$target > > > well, there's still the standardization point. if gdb did > this automatically, then people could rely on that behavior > in arbitrary installations. otherwise, people will > synthesize this behavior themselves in different ways. one > installation might have .gdb.$target, another > .gdbinit.$target, or .vxgdbinit, etc. It should be kept simple. A GDB install should only read `.gdbinit' (the vx hacks, I think, should just go). A user is then free to customize their .gdbinit to do things like read .gdbinit-$target, or even conditionally interpret sections of the init file. If GDB's scripting language isn't powerful enough to handle this then the scripting language needs to be fixed. Andrew