From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4477 invoked by alias); 29 Apr 2005 19:01:20 -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 2427 invoked from network); 29 Apr 2005 18:59:57 -0000 Received: from unknown (HELO cgf.cx) (66.30.17.189) by sourceware.org with SMTP; 29 Apr 2005 18:59:57 -0000 Received: by cgf.cx (Postfix, from userid 201) id DF34113C1C8; Fri, 29 Apr 2005 14:59:56 -0400 (EDT) Date: Fri, 29 Apr 2005 19:08:00 -0000 From: Christopher Faylor To: mark@codesourcery.com, paul@codesourcery.com, gdb@sourceware.org Subject: Re: Windows support in GDB Message-ID: <20050429185956.GB17283@trixie.casa.cgf.cx> Mail-Followup-To: mark@codesourcery.com, paul@codesourcery.com, gdb@sourceware.org References: <200504291513.j3TFDhjx021040@elgar.sibelius.xs4all.nl> <20050429153146.GA27362@nevyn.them.org> <20050429160040.GH10017@trixie.casa.cgf.cx> <20050429164508.GA30548@nevyn.them.org> <20050429171631.GH12864@trixie.casa.cgf.cx> <20050429175745.GA753@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050429175745.GA753@nevyn.them.org> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-04/txt/msg00240.txt.bz2 On Fri, Apr 29, 2005 at 01:57:45PM -0400, Daniel Jacobowitz wrote: >On Fri, Apr 29, 2005 at 01:16:31PM -0400, Christopher Faylor wrote: >>It seems like my point wasn't clear here. I know that cygwin is slow. >> >>I'm talking about just using gdb for debugging. If your customers are >>routinely rebuilding gdb, then the slowness would be an issue. If they >>are not, then unless cygwin was adding some kind of 10x slowdown to >>debugging, I don't see why it would be an issue. > >OK, I see your point. I think we're talking past each other, though - >this comes back to Kris's point about consistency. Shipping a mingw >GCC and a cygwin GDB is error-prone, especially if we otherwise do not >need the cygwin DLL. I don't see why this is an issue. It would take a little bit of work to make sure you didn't stomp on an existing cygwin installation but putting a cygwin1.dll in the same directory as gdb.exe is a pretty time-tested way of releasing packages on Windows. Many packages release executables + dlls. Cygwin is problematic because it is constantly evolving and adding new features and, so, there will be issues if you try to use an old DLL with a newer binary but, again, this is not an insurmountable problem. cgf