On Fri, Nov 13, 2009 at 08:29:08PM +0100, Federico Hernandez wrote:
>> ?Also, you can check exit status from the shell by running "echo $?" after
>> the command, which is a bit less trouble than using the debugger. ?The "$?"
>> shell variable gets set to the status of the last command executed. ?(T
> Also, you can check exit status from the shell by running "echo $?" after
> the command, which is a bit less trouble than using the debugger. The "$?"
> shell variable gets set to the status of the last command executed. (This is
> generic shell stuff, not cygwin-specific.)
Of course. Why do
Federico Hernandez wrote:
>>> Sounds like you may be missing dll. cygcheck yourprogram.exe might help.
>> Thank you. We will do this.
>>
>> A gdb run provided some exit code which google and the mailing list
>> archive suggested to be some dll problem. Now I know how to find out.
>
> Problem solv
3 matches
Mail list logo
