From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26738 invoked by alias); 14 Jan 2003 19:11:21 -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 26729 invoked from network); 14 Jan 2003 19:11:16 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 209.249.29.67 with SMTP; 14 Jan 2003 19:11:16 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id OAA16273; Tue, 14 Jan 2003 14:02:33 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id OAA23877; Tue, 14 Jan 2003 14:11:03 -0500 Message-ID: <000901c2bc00$aa564e80$0202040a@catdog> From: "Kris Warkentin" To: "Andrew Cagney" Cc: "Elena Zannoni" , "Fernando Nasser" , "Felix Lee" , References: <200301102242.h0AMgTl02921@paper-wolf-solo.tigerfood.org> <0d6601c2bb1e$70a94670$0202040a@catdog> <3E230B07.8030607@redhat.com> <0e5301c2bb36$1002c400$0202040a@catdog> <3E2315B5.8030003@redhat.com> <0e8401c2bb47$c00d89a0$0202040a@catdog> <3E2332A5.10403@redhat.com> <0ed601c2bb51$818e58d0$0202040a@catdog> <3E233DF2.6010403@redhat.com> Subject: Re: patch to use target specific .gdbinit file Date: Tue, 14 Jan 2003 19:11:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-01/txt/msg00229.txt.bz2 > > Well then a configure option isn't the answer. > > A configuration time option answers a problem. Perhaps not your problem. > Well, it answers our problem but isn't extensible to a multi-arch situation. It sounds like almost everyone agrees that some form of a target specific extension to the .gdbinit mechanism would be useful but a decision about how best to implement it hasn't been made. What I'm going to do for now is implement it in our port only. We ship separate gdb binaries and are not planning on multi-arching soon so our _initialize_nto() function is a perfect place to put it. Our documentation states that if $HOME/.gdbinit- exists, it is read instead of $HOME/.gdbinit so I'll just check for the file, source it and set inhibit_gdbinit if it's found. Thanks for all the help. It's interesting to hear from others about the possible ramifications and alternate solutions to problems. cheers, Kris