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/30415] conflicting types for ‘kallsyms_on_each_symbol’
Date: Wed, 03 May 2023 09:01:29 +0000	[thread overview]
Message-ID: <bug-30415-6586-yUakww46wi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30415-6586@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Martin Cermak <mcermak at redhat dot com> ---
The reproducer is even simpler:

[root@rawh ~]# uname -r; rpm -q systemtap
6.4.0-0.rc0.20230428git33afd4b76393.7.fc39.x86_64
systemtap-4.9-1.fc39.x86_64
[root@rawh ~]# 
[root@rawh ~]# stap -vp4 -e 'probe begin { exit() }'
Pass 1: parsed user script and 484 library scripts using
124832virt/101128res/11136shr/89524data kb, in 190usr/40sys/223real ms.
Pass 2: analyzed script: 1 probe, 1 function, 0 embeds, 0 globals using
126284virt/103048res/11520shr/90976data kb, in 0usr/0sys/8real ms.
Pass 3: translated to C into
"/tmp/stapLy8yoU/stap_6881d4c66122cefc1b5d5c230a431144_1182_src.c" using
126284virt/103432res/11904shr/90976data kb, in 0usr/0sys/0real ms.
In file included from /usr/local/share/systemtap/runtime/linux/runtime.h:288,
                 from /usr/local/share/systemtap/runtime/runtime.h:26,
                 from
/tmp/stapLy8yoU/stap_6881d4c66122cefc1b5d5c230a431144_1182_src.c:21:
/usr/local/share/systemtap/runtime/sym.c:1159:5: error: conflicting types for
‘kallsyms_on_each_symbol’;

[ ... stuff deleted ... ]

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

  reply	other threads:[~2023-05-03  9:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  8:56 [Bug runtime/30415] New: " mcermak at redhat dot com
2023-05-03  9:01 ` mcermak at redhat dot com [this message]
2023-05-03 10:41 ` [Bug runtime/30415] " mcermak at redhat dot com
2023-05-09 19:23 ` wcohen at redhat dot com
2023-05-22  8:56 ` mcermak at redhat dot com
2023-05-22 14:01 ` wcohen at redhat dot com
2023-05-22 14:48 ` wcohen at redhat dot com
2023-05-24 11:16 ` mcermak at redhat dot com
2023-05-24 11:24 ` mcermak at redhat dot com
2023-05-25 18:43 ` wcohen at redhat dot com
2023-05-26 10:28 ` mcermak at redhat dot com
2023-05-30 14:51 ` mcermak at redhat dot com
2023-05-31 13:59 ` wcohen at redhat dot com
2023-06-02  9:28 ` mcermak at redhat dot com
2023-06-02 15:22 ` wcohen at redhat dot com
2023-06-02 18:26 ` mcermak at redhat dot com
2023-06-02 21:21 ` wcohen at redhat dot com
2023-06-02 21:38 ` mcermak 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-30415-6586-yUakww46wi@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).