delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <4B2A7731.3040309@gmail.com> |
References: | <f40a5ca30912170919p35650019l326d8b53ec0fe037 AT mail DOT gmail DOT com> <f40a5ca30912170924l283fe825h7ec2b32dc6ac48a2 AT mail DOT gmail DOT com> <4B2A6CA9 DOT 8060206 AT cygwin DOT com> <4B2A7731 DOT 3040309 AT gmail DOT com> |
Date: | Thu, 17 Dec 2009 13:23:20 -0500 |
Message-ID: | <f40a5ca30912171023q24636fbcoa661dfd1533cb2cc@mail.gmail.com> |
Subject: | Re: Fwd: 1.5.25: Tools to diagnose unresponsive pre-compiled executables? |
From: | Gilles Lehoux <gcygarm AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Thu, Dec 17, 2009 at 1:23 PM, Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com> wrote: > 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. =A0Try >> running 'cygcheck arm-elf-c++.exe' and see if it complains about not >> finding some DLLs. > > =A0Also, in answer to the generic "what tools exist" question, a basic on= e is > "echo $?", which prints the exit status of the previous bash command. =A0= (Not > always informative, but often enough to be worth checking.) > > =A0 =A0cheers, > =A0 =A0 =A0DaveK > > > -- > Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html > FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/ > Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html > Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple > > That is an excellent tip. Can you recommend a tip sheet or webpage where tips along the same vein have been gathered? Gilles. -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |