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/31039] New: implicit declaration of function ‘stap_task_finder_complete’
Date: Tue, 07 Nov 2023 14:39:13 +0000	[thread overview]
Message-ID: <bug-31039-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31039
           Summary: implicit declaration of function
                    ‘stap_task_finder_complete’
           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: ---

On Fedora 40, auto_path.exp fails with "implicit declaration of function
‘stap_task_finder_complete’".  Smaller reproducer:

f40 x86_64 # pwd
/root/systemtap/testsuite/systemtap.base
f40 x86_64 # gcc -g auto_path.c 
f40 x86_64 # stap -I tapset -e 'probe ap1.process {println(pp())}' -c ./a.out 
In file included from
/tmp/stap9p91aS/stap_6d06511a67f12d9b3e0b31aa80968db5_1658_src.c:250:
/usr/local/share/systemtap/runtime/linux/uprobes-inode.c: In function
‘stapiu_probe_prehandler’:
/usr/local/share/systemtap/runtime/linux/uprobes-inode.c:209:13: error:
implicit declaration of function ‘stap_task_finder_complete’; did you mean
‘stap_task_finder_post_init’? [-Werror=implicit-function-declaration]
  209 |         if (stap_task_finder_complete())
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~
      |             stap_task_finder_post_init
/tmp/stap9p91aS/stap_6d06511a67f12d9b3e0b31aa80968db5_1658_src.c: At top level:
/tmp/stap9p91aS/stap_6d06511a67f12d9b3e0b31aa80968db5_1658_src.c:394:76: error:
‘struct stap_task_finder_target’ has no member named ‘build_id_len’
  394 |   { .finder={  .purpose="inode-uprobes",
.callback=&stapiu_process_found, .build_id_len=0,
.procname="/tmp/stap_auto_path/a/ap1", },
.module_name="/tmp/stap_auto_path/a/ap1", .offset=(loff_t)0x110aULL,
.probe=(&stap_probes[0]), },
      |                                                                        
   ^~~~~~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:243:
/tmp/stap9p91aS/stap_6d06511a67f12d9b3e0b31aa80968db5_1658_src.o] Error 1
make: *** [Makefile:1931: /tmp/stap9p91aS] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed.  [man error::pass4]
Kernel version 6.7.0 is outside tested range 2.6.32 ... 6.5
f40 x86_64 #

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

             reply	other threads:[~2023-11-07 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 14:39 mcermak at redhat dot com [this message]
2023-12-06 22:36 ` [Bug runtime/31039] " wcohen at redhat dot com
2023-12-11 21:08 ` wcohen at redhat dot com
2023-12-11 22:15 ` wcohen 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-31039-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).