[Bug translator/10690] need way to produce bigger procfs output

[dsmith at redhat dot com]

------- Additional Comments From dsmith at redhat dot com  2010-01-22 21:24 -------
I've done some testing on bigger procfs input/output with the current code,
trying to see what happens when MAXSTRINGLEN is changed.  For the .read tests, I
output a string MAXSTRINGLEN bytes long. For the .write tests, I fed a test file
with > 8k worth of data into the procfs file.

Here's what I found.

MAXSTRINGLEN = 512 (the default)
.read = OK
.write = bug - probe gets called multiple times, in MAXSTRINGLEN chunks, but the
last chunk is a mix of old and new data

MAXSTRINGLEN = 4096
.read = bug, only seeing ~3000 chars?
.write = bug, probe gets called multiple times in MAXSTRINGLEN chunks, but the
last chunk is a mix of old and new data

MAXSTRINGLEN = 8192
.read = bug, only seeing 1st 4k of data
.write = bug, probe gets called multiple times in MAXSTRINGLEN chunks, but the
last chunk is a mix of old and new data


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10690

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.