public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22582] SystemTap 3.2 stap script compilation error opt
Date: Thu, 18 Jan 2024 01:57:36 +0000	[thread overview]
Message-ID: <bug-22582-6586-DKYyPh4k9U@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22582-6586@http.sourceware.org/bugzilla/>

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

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
                 CC|                            |wcohen at redhat dot com
             Status|WAITING                     |RESOLVED

--- Comment #8 from William Cohen <wcohen at redhat dot com> ---
It appears to be an issue with the locally built kernel configuration rather
systemtap.  On the recent version of 32-bit raspberry pi has the
sched_process_* and sys_* tracepoints:

$ uname -a
Linux raspberrypi 6.1.21+ #1642 Mon Apr  3 17:19:14 BST 2023 armv6l GNU/Linux
$ sudo /home/wcohen/bin/perf list |grep sched_process*
  sched:sched_process_exec                           [Tracepoint event]
  sched:sched_process_exit                           [Tracepoint event]
  sched:sched_process_fork                           [Tracepoint event]
  sched:sched_process_free                           [Tracepoint event]
  sched:sched_process_hang                           [Tracepoint event]
  sched:sched_process_wait                           [Tracepoint event]
$ sudo /home/wcohen/bin/perf list |grep sys_
  raw_syscalls:sys_enter                             [Tracepoint event]
  raw_syscalls:sys_exit                              [Tracepoint event]

There hasn't been any response on this bug for over six year.  Going to close
this.

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

      parent reply	other threads:[~2024-01-18  1:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11  8:13 [Bug runtime/22582] New: " mysecondaccountabc at gmail dot com
2017-12-11 14:18 ` [Bug runtime/22582] " dsmith at redhat dot com
2017-12-11 22:16 ` mysecondaccountabc at gmail dot com
2017-12-11 22:21 ` mysecondaccountabc at gmail dot com
2017-12-11 22:27 ` mysecondaccountabc at gmail dot com
2017-12-12 15:04 ` dsmith at redhat dot com
2017-12-13  5:21 ` mysecondaccountabc at gmail dot com
2017-12-13 18:47 ` dsmith at redhat dot com
2024-01-18  1:57 ` wcohen at redhat dot com [this message]

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-22582-6586-DKYyPh4k9U@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).