[Win32utils-devel] buffer size for win32-eventlog (was infinite
loop bug...)
win32utils-devel at rubyforge.org
win32utils-devel at rubyforge.org
Fri Oct 29 21:12:02 EDT 2004
Hi,
>>I just noticed the bug is not fixed completely.
>>If run with e.read , the output record number is from 42 to 2081.
>>If run with e.read(EventLog::SEEK_READ|EventLog::FORWARDS_READ,250) , the
>>output record number is from 250 to 820.
>>If run with e.read(EventLog::SEEK_READ|EventLog::FORWARDS_READ,42) , the
>>output record number is from 42 to 570.
>>Why this happens? Is it the bug of MS?
>I can confirm this behavior. It looks like a problem with the buffer size
>and reallocation. Because, if I increase the BUFFER_SIZE macro, I get more
>records.
>Now, as to why the realloc() isn't working like we expect I'm not sure.
OK, I understand what happens.
Now I fixed it and committed to CVS.
Thanks,
Park Heesob
More information about the win32utils-devel
mailing list