Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 5 May 2004 15:23:17 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: Joshua Kolden cc: cygwin AT cygwin DOT com Subject: Re: intel ddd cygwin In-Reply-To: <012601c4321e$586358d0$0200a8c0@id5> Message-ID: References: <012601c4321e$586358d0$0200a8c0 AT id5> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Just some WAGs: On Tue, 4 May 2004, Joshua Kolden wrote: > When attempting to start debugging on a simple helloWorld program ddd > seems to hang waiting for a responds from idb (the intel's debugger) > > > ddd --debugger "idb -gdb" helloWorld.exe > > I get: > > "Reading Symbols from helloWorld.exe...done." > > ...then nothing. If I try any other action in ddd, such as "run" I get: > > "Run: waiting until GDB gets ready" IIRC, ddd uses ttys to talk to the inferior debugger. Try CYGWIN=tty, but since idd is not a Cygwin application, it may not help any. > Which never does get ready. However, when I run idb by hand it responds > like gdb. Anyone have any experience with this? Are you sure that idb's gdb emulation is exact? Just a couple guesses... -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/