From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Received: (qmail 13360 invoked from network); 10 Jan 2003 22:44:10 -0000 Received: from unknown (HELO hug.dreamhost.com) (66.33.197.18) by 209.249.29.67 with SMTP; 10 Jan 2003 22:44:10 -0000 Received: from paper-wolf-solo.tigerfood.org (localhost [127.0.0.1]) by hug.dreamhost.com (Postfix) with ESMTP id D407F17E96 for ; Fri, 10 Jan 2003 14:43:57 -0800 (PST) Received: from tigerfood.org (flee@localhost) by paper-wolf-solo.tigerfood.org (8.11.6/8.11.6) with ESMTP id h0AMgTl02921 for ; Fri, 10 Jan 2003 14:42:30 -0800 Message-Id: <200301102242.h0AMgTl02921@paper-wolf-solo.tigerfood.org> X-Authentication-Warning: paper-wolf-solo.tigerfood.org: flee owned process doing -bs From: Felix Lee Subject: Re: patch to use target specific .gdbinit file To: gdb@sources.redhat.com In-reply-to: <0b9e01c2b8cb$4a81fd20$0202040a@catdog> on Fri, 10 Jan 2003 12:11:18 EST. Date: Fri, 10 Jan 2003 22:44:00 -0000 X-SW-Source: 2003-01/txt/msg00181.txt.bz2 "Kris Warkentin" : > The following code will allow backend writers to define > EXTRA_GDBINIT_FILENAME to be an alternate filename for sourcing on startup. > For example, since we have gdb versions for 5 different CPU targets, we > allow users to create a $HOME/.ntoCPU-gdbinit. 1, I'd rather it be a generalized name, like maybe .gdbinit-$TARGET. making the name something chosen by the backend writer feels like it adds unnecessary irregularity. 2, this is going to make it more awkward to create a single gdb that will debug multiple targets. --