From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4263 invoked by alias); 22 Jan 2010 20:58:27 -0000 Received: (qmail 4219 invoked by uid 48); 22 Jan 2010 20:58:16 -0000 Date: Fri, 22 Jan 2010 20:58:00 -0000 Message-ID: <20100122205816.4218.qmail@sourceware.org> From: "dsmith at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20090923141722.10690.fche@redhat.com> References: <20090923141722.10690.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/10690] need way to produce bigger procfs output X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00240.txt.bz2 ------- Additional Comments From dsmith at redhat dot com 2010-01-22 20:58 ------- (In reply to comment #0) > There exist uses for procfs("file").write and especially .read, > for which it is desirable for stap scripts to produce much more than > MAXSTRINGLEN bytes of output. I can see the value for .read to produce more than MAXSTRINGLEN bytes of output, but I'm unsure of the value of .write to be able to read more than MAXSTRINGLEN bytes of input. Assuming we could read more than MAXSTRINGLEN bytes of input, what could we then do with that data? We can't assign (all of it) to another string variable. We could print it (which might fail if the the number of bytes is greater than STP_BUFFER_SIZE). I'm unsure of anything else we could do with it. -- 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.