----Original Message---- >From: Corinna Vinschen >Sent: 03 May 2005 10:06
> On May 3 00:25, Utku Ozcan wrote: >> I *think* that the test below, which tests memory allocation limit of >> Cygwin *might* produce problems in Windows XP: >> >> http://sources.redhat.com/cygwin/cygwin-ug-net/setup-maxmem.html >> >> In this page, I have compiled the C code, and after having run the >> compiled executable, Windows XP gave suddenly a warning that virtual >> memory setting has been changed (I think, that repeated malloc() calls >> in this code somehow change the virtual memory settings in Windows >> XP). > > Not really. > > > Corinna Interestingly enough, there _is_ some kind of problem here. I haven't been hit by any HD problem, but when I tried the test program, it gave me an ever-increasing series of values, and then suddenly stopped working altogether and wouldn't recover! [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 5095e000 bytes (1289.4Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 518be000 bytes (1304.7Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 51956000 bytes (1305.3Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 519de000 bytes (1305.9Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 51a7e000 bytes (1306.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 51b7e000 bytes (1307.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 51dbe000 bytes (1309.7Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 51f7e000 bytes (1311.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 521be000 bytes (1313.7Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 523fe000 bytes (1316.0Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 525fe000 bytes (1318.0Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 528fe000 bytes (1321.0Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 52b7e000 bytes (1323.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 52dbe000 bytes (1325.7Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 52f7e000 bytes (1327.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 5317e000 bytes (1329.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 5337e000 bytes (1331.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 534ee000 bytes (1332.9Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 5367e000 bytes (1334.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 537de000 bytes (1335.9Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 5393e000 bytes (1337.2Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 53afe000 bytes (1339.0Mb) [EMAIL PROTECTED] /test/maxmem> [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 53d7e000 bytes (1341.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 53f7e000 bytes (1343.5Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe 542fe000 bytes (1347.0Mb) [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe [EMAIL PROTECTED] /test/maxmem> ./maxmem.exe Trying to run it under insight, the first time I tried it it worked, but when I tried to rerun it it crashed and took insight with it! There has been some persistent leak of some resource, because after getting into that state, other cygwin applications start failing with "resource temporarily unavailable" problems. Even after killing all my cygwin shells and processes (and therefore having hopefully completely unloaded the dll and released the shared heap and so on), newly started shells can only sometimes run the testapp, and never more than once. I'll post more information when I have it. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
