public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26702] New: historical intermittent rt-linux crashes
Date: Fri, 02 Oct 2020 20:50:26 +0000	[thread overview]
Message-ID: <bug-26702-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26702
           Summary: historical intermittent rt-linux crashes
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: fche at redhat dot com
  Target Milestone: ---

While numerous rt-linux tweaks to the runtime have been
made over the years, there may still be some problems.
Some problem reproducer from years ago may still cause
problems now.  Putting them here for the record.

Via <smakarov@redhat.com>:

Looked into reducing the conversions_profile.stp test case. So far I've reduced
down to

$ stap -g  --suppress-time-limits -vv -DMAXSKIPPED=99999 -DMAXERRORS=40 -e
'global hits; probe timer.profile { if (hits == 0) { hits = 1;
print(kernel_string(0xfffffff)) } }'

and

$ stap -g  --suppress-time-limits -vv -DMAXSKIPPED=99999 -DMAXERRORS=40 -e
'global hits; probe timer.profile { if (hits == 0) { hits = 1 } }'

The following works fine without crashing:

$ stap -g --suppress-time-limits -vv -DMAXSKIPPED=99999 -DMAXERRORS=40 -e
'probe timer.profile { print(kernel_string(0xfffffff)) }'

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

                 reply	other threads:[~2020-10-02 20:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-26702-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).