tcsh out of memory and core dump

[tsteven4]

On 11/29/2010 1:57 PM, Corinna Vinschen wrote:
> On Nov 29 05:58, tsteven4 wrote:
>> I can readily reproduce a tcsh error "Out of memory", however the
>> timing is variable.  In my actual application the time to failure
>> varies from seconds to hours.  I have a test case that seems to be
>> able to reproduce the error.
>>
>> The symptom of the error is a message like:
>> 188
>> ./test2
>> 189
>> ./test2
>> 190
>> ./test2
>> 191
>> tcsh current memory allocation:
>> free:       0  119   52   25   29   23   17    3    0    2    0    0
>> 2    0    0    0    0    0    0    0    0    0    0    0    0    0
>> 0    0    0
>> used:       0    9  204  167   51   33   19    3    1    1    2    2
>> 1    4    3    0    0    0    0    0    0    0    0    0    0    0
>> 0    0    0
>>          Total in use: 788560, total free: 100272
>>          Allocated memory from 0xab0000 to 0xffffffff.  Real top at 0xb89000
>> nbytes=32784: Out of memory
>> Abort (core dumped)
>> 192
>> ./test2
>> 193
>> ./test2
>> 194
>> ./test2
>> 195
>> ./test2
> Thanks for the testcase!  It helped me to track down a memory leak in
> Cygwin which occurs on each dup/dup2/dup3 call on a tty.  This is done
> very often in tcsh and thus affects long-running scripts quite heavily.
>
> I applied a patch to CVS.  Please test the next Cygwin developer snapshot
> from http://cygwin.com/snapshots/, which will contain the fix.
>
>
> Thanks again,
> Corinna
>
Corinna,

I tested today's snapshot and the tcsh memory issue appears to be 
fixed.  Thank you for the very speedy resolution.

Steve

--
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