public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/23813] New: Make "too many pending warnings" more helpful
Date: Wed, 24 Oct 2018 04:47:00 -0000	[thread overview]
Message-ID: <bug-23813-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=23813

            Bug ID: 23813
           Summary: Make "too many pending warnings" more helpful
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: agentzh at gmail dot com
  Target Milestone: ---

Some times we only get something like below from stap:

```
WARNING: too many pending (warning) messages
ERROR: too many pending (error) messages
WARNING: /opt/stap-plus/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
```

It's not helpful at all since we have no idea what messages are actually
flooding the control message buffers.

We should make stap output the first few and also the last few messages in the
current control buffer when it thinks that there are "too many". Otherwise
there is no way to debug things here.

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

             reply	other threads:[~2018-10-24  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  4:47 agentzh at gmail dot com [this message]
2018-10-24 18:14 ` [Bug runtime/23813] " fche at redhat dot com
2018-10-24 18:47 ` agentzh at gmail dot com
2018-10-24 18:50 ` fche at redhat dot com
2018-10-24 18:52 ` agentzh at gmail dot com

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=bug-23813-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).