From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4496 invoked by alias); 2 Jan 2003 18:53:03 -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 4470 invoked from network); 2 Jan 2003 18:53:01 -0000 Received: from unknown (HELO hug.dreamhost.com) (66.33.197.18) by 209.249.29.67 with SMTP; 2 Jan 2003 18:53:01 -0000 Received: from paper-wolf-solo.tigerfood.org (localhost [127.0.0.1]) by hug.dreamhost.com (Postfix) with ESMTP id 1A93F17E94 for ; Thu, 2 Jan 2003 10:52:49 -0800 (PST) Received: from tigerfood.org (flee@localhost) by paper-wolf-solo.tigerfood.org (8.11.6/8.11.6) with ESMTP id h02IpaZ24996 for ; Thu, 2 Jan 2003 10:51:37 -0800 Message-Id: <200301021851.h02IpaZ24996@paper-wolf-solo.tigerfood.org> X-Authentication-Warning: paper-wolf-solo.tigerfood.org: flee owned process doing -bs From: Felix Lee Subject: Re: target-dependent .gdbinit To: gdb@sources.redhat.com In-reply-to: <3E1455D9.2010009@redhat.com> on Thu, 02 Jan 2003 15:08:09 GMT. Date: Thu, 02 Jan 2003 18:53:00 -0000 X-SW-Source: 2003-01/txt/msg00021.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. --