X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B2A7731.3040309@gmail.com> Date: Thu, 17 Dec 2009 18:23:45 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Fwd: 1.5.25: Tools to diagnose unresponsive pre-compiled executables? References: <4B2A6CA9 DOT 8060206 AT cygwin DOT com> In-Reply-To: <4B2A6CA9.8060206@cygwin.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Larry Hall (Cygwin) wrote: > On 12/17/2009 12:24 PM, Gilles Lehoux wrote: >> Some of my executables are unresponsive. What tools exist in cygwin >> (other than gdb) to diagnose what is going on? There is no output from >> the executable (ex. error msg) and these are pre-compiled executables. >> No graphics. Strictly command line executables. > > Sounds like you're missing some DLLs the executables depend on. Try > running 'cygcheck arm-elf-c++.exe' and see if it complains about not > finding some DLLs. Also, in answer to the generic "what tools exist" question, a basic one is "echo $?", which prints the exit status of the previous bash command. (Not always informative, but often enough to be worth checking.) cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple