From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23986 invoked by alias); 28 Dec 2002 18:59:28 -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 23958 invoked from network); 28 Dec 2002 18:59:27 -0000 Received: from unknown (HELO hug.dreamhost.com) (66.33.197.18) by 209.249.29.67 with SMTP; 28 Dec 2002 18:59:27 -0000 Received: from paper-wolf-solo.tigerfood.org (localhost [127.0.0.1]) by hug.dreamhost.com (Postfix) with ESMTP id 72BA817EAA for ; Sat, 28 Dec 2002 10:59:14 -0800 (PST) Received: from tigerfood.org (flee@localhost) by paper-wolf-solo.tigerfood.org (8.11.6/8.11.6) with ESMTP id gBSIwJJ07676 for ; Sat, 28 Dec 2002 10:58:19 -0800 Message-Id: <200212281858.gBSIwJJ07676@paper-wolf-solo.tigerfood.org> X-Authentication-Warning: paper-wolf-solo.tigerfood.org: flee owned process doing -bs From: Felix Lee To: gdb@sources.redhat.com Subject: target-dependent .gdbinit Date: Sat, 28 Dec 2002 10:59:00 -0000 X-SW-Source: 2002-12/txt/msg00328.txt.bz2 So I'm thinking I want gdb to read ~/.gdbinit-$target after ~/.gdbinit. Does that seem like a sensible thing to do? I'm wary of making target a special case. My feeling is I'd want a single .gdbinit file that has some form of #if for target or host or gdb version or other conditions. But I'm not sure that's all that useful. The added complexity doesn't seem to be worth it. But target is already a special case sometimes, because there's .vxgdbinit and such. Also, behavior like this could be easily synthesized with a front-end script that ran gdb with the right -x options. The rationale for putting it into gdb: it's standardization. --