Fwd: 1.5.25: Tools to diagnose unresponsive pre-compiled executables?
Gilles Lehoux
gcygarm@gmail.com
Thu Dec 17 18:23:00 GMT 2009
On Thu, Dec 17, 2009 at 1:23 PM, Dave Korn
<dave.korn.cygwin@googlemail.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. 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
>
>
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
More information about the Cygwin
mailing list