Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Sat, 10 Jun 2000 22:16:39 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: Is this a resolution for the GDB problem? Message-ID: <20000610221639.E4821@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <20000610180038.A4484@cygnus.com> <000101bfd32b$5535b1e0$1737ba8c@nhv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <000101bfd32b$5535b1e0$1737ba8c@nhv>; from nhv@cape.com on Sat, Jun 10, 2000 at 06:29:17PM -0400 On Sat, Jun 10, 2000 at 06:29:17PM -0400, Norman Vine wrote: >Chris Faylor writes: >>I've created a new cygtcl80.dll file here: >> >>ftp://ftp.cygnus.com/private/home/cgf/cygtcl80.dll >> >>If you replace the version of this file in your "/bin" directory >>you should be able to use gdb. > >Bingo !! Phew. Thanks for all of the feedback. The strace, cygcheck, and tcl trace were all essential in tracking this down. It's nice to deal with people who are willing to run gdb. :-) cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com