From: "marko@kevac.org" <marko@kevac.org>
To: Felix Lu <flu@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: JSON construction error: buffer size exceeded
Date: Thu, 16 Jun 2016 13:55:00 -0000 [thread overview]
Message-ID: <CA+RAKy4oFAZC+VJ0gVYA5mzAX+ze=PLFrHAVOs8Ha-115XYe5Q@mail.gmail.com> (raw)
In-Reply-To: <495681710.55615562.1466084582504.JavaMail.zimbra@redhat.com>
On Thu, Jun 16, 2016 at 4:43 PM, Felix Lu <flu@redhat.com> wrote:
> The upstream version is now much more stable if you would like to try that.
I will try upstream version. Thank you.
> It would be much appreciated if you could provide your script to help
> diagnose if this error still exists.
I am using systemtap to probe user space program. So without the
program it would not be useful I think.
Anyway, it's here
https://gist.github.com/mkevac/5fa180bf49ccb05855a2d555655bcd8d
next prev parent reply other threads:[~2016-06-16 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 11:51 marko
2016-06-16 13:43 ` Felix Lu
2016-06-16 13:55 ` marko [this message]
2016-06-16 14:27 ` marko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+RAKy4oFAZC+VJ0gVYA5mzAX+ze=PLFrHAVOs8Ha-115XYe5Q@mail.gmail.com' \
--to=marko@kevac.org \
--cc=flu@redhat.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).