From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10889 invoked by alias); 13 Nov 2001 18:07:25 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10860 invoked from network); 13 Nov 2001 18:07:22 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sourceware.cygnus.com with SMTP; 13 Nov 2001 18:07:22 -0000 Received: from redhat.com (rtl.cygnus.com [205.180.230.21]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id KAA26981; Tue, 13 Nov 2001 10:07:19 -0800 (PST) Message-ID: <3BF1612E.94883F9A@redhat.com> Date: Thu, 01 Nov 2001 16:50:00 -0000 From: Fernando Nasser Organization: Red Hat Canada X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-12 i686) X-Accept-Language: en MIME-Version: 1.0 To: gdb , Eli Zaretskii Subject: Re: gdb.ini vs. .gdbinit on Cygwin References: <3BF14E50.7E55FC0C@redhat.com> <20011113180434.Y2618@cygbert.vinschen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2001-11/txt/msg00032.txt.bz2 Corinna Vinschen wrote: > > We're talking about the Cygwin version. A native DOS/Windows version > can keep gdb.ini. It doesn't matter. > As per Eli note, it can go as well. > > And the Windows Explorer issue, has it gone on the XP version? > > Of course not. However, we should use .gdbinit the same way as for > any other host on Cygwin. There's no reason to treat the Cygwin GDB > special in that case. OK. > If you think it's really necessary, we can > keep supporting gdb.ini as well We need it for backward compatibility. Users may have a gdb.ini right now and may not be aware of the change. >but a Cygwin GDB doesn't have to > take care for Explorer disabilities, IMO. OK with me. > As a resort we could > begin to support an environment variable GDBINIT or similar which > contains the name/path of the GDB init file. That would have the > advantage to be mostly host independent. > That would have to go through a public gdb discussion as it would affect other platforms as well. And what we need is to accommodate users with an older setup and give them an incentive to switch. The warning message (if no .gdbinit was fond and a gdb.ini was found instead) accomplishes both goals. Eli, what do you think of that solution? Does it address your concerns? -- Fernando Nasser Red Hat Canada Ltd. E-Mail: fnasser@redhat.com 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9