From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92045 invoked by alias); 16 Jun 2016 13:43:07 -0000 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 Received: (qmail 92033 invoked by uid 89); 16 Jun 2016 13:43:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_40,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*M:zimbra, H*x:ZimbraWebClient, H*UA:ZimbraWebClient, H*x:Linux X-HELO: mx5-phx2.redhat.com Received: from mx5-phx2.redhat.com (HELO mx5-phx2.redhat.com) (209.132.183.37) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 16 Jun 2016 13:43:05 +0000 Received: from zmail26.collab.prod.int.phx2.redhat.com (zmail26.collab.prod.int.phx2.redhat.com [10.5.83.33]) by mx5-phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u5GDh2Wk053042; Thu, 16 Jun 2016 09:43:02 -0400 Date: Thu, 16 Jun 2016 13:43:00 -0000 From: Felix Lu To: marko@kevac.org Cc: systemtap@sourceware.org Message-ID: <495681710.55615562.1466084582504.JavaMail.zimbra@redhat.com> In-Reply-To: References: Subject: Re: JSON construction error: buffer size exceeded MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-q2/txt/msg00235.txt.bz2 Hi Marko, Monitor mode is still undergoing development so there may be some bugs. > I am looking into monitor with sudo stap --monitor -o result.log > my4.stap meetmaker, but I get these errors: > > WARNING: JSON construction error: buffer size exceeded, consider > .maxsize(2325). > WARNING: JSON construction error: buffer size exceeded, consider > .maxsize(2336). > WARNING: JSON construction error: buffer size exceeded, consider > .maxsize(2337). > This is an error related to the internal implementation of monitor mode. The upstream version is now much more stable if you would like to try that. It would be much appreciated if you could provide your script to help diagnose if this error still exists. Thanks, Felix