public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28511] New: Should --example imply -w ?
Date: Thu, 28 Oct 2021 08:31:48 +0000	[thread overview]
Message-ID: <bug-28511-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28511
           Summary: Should --example imply -w ?
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com
  Target Milestone: ---

I tend to think/expect that --example is used for linux admin work, just like
strace etc.  In that case, would it make sense to change the --example behavior
in a way that it implies -w ?

Here's an example without -w:

scr0   8.6 Server x86_64 # stap --example disktop.stp
WARNING: Potential type mismatch in reassignment: identifier 'root_dentry' at
/usr/share/systemtap/tapset/linux/dentry.stp:246:3
 source:                root_dentry = @cast(task, "task_struct",
"kernel")->fs->root->dentry
                        ^

Thu Oct 28 08:16:42 2021 , Average:   0Kb/sec, Read:       0Kb, Write:      0Kb

     UID      PID     PPID                       CMD   DEVICE    T        BYTES
       0      965        1             rs:main Q:Reg     vda1    W          374

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

             reply	other threads:[~2021-10-28  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28  8:31 mcermak at redhat dot com [this message]
2021-10-28 20:05 ` [Bug runtime/28511] " fche at redhat 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-28511-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).