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/31274] New: Unsatisfied references to  _stp_module_0_debug_line_str
Date: Mon, 22 Jan 2024 18:59:50 +0000	[thread overview]
Message-ID: <bug-31274-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31274
           Summary: Unsatisfied references to
                    _stp_module_0_debug_line_str
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: wcohen at redhat dot com
  Target Milestone: ---

On x86_64 Fedora 39 see a number of tests that have errors during the
compilation of the C kernel modules of the form like following for usymfileline
() complaining about missing _stp_module_0_debug_line_str:


executing: stap -v -e { probe process("usymfileline").function("test_method") {
print("systemtap starting probe\nsystemtap ending probe\n") printf("%s\n",
usymfileline($1)) exit()} } 0 -c ./usymfileline
spawn stap -v -e  probe process("usymfileline").function("test_method") {
print("systemtap starting probe\nsystemtap ending probe\n") printf("%s\n",
usymfileline($1)) exit()}  0 -c ./usymfileline
Pass 1: parsed user script and 484 library scripts using
133280virt/107096res/14976shr/91576data kb, in 140usr/10sys/152real ms.
Pass 2: analyzed script: 2 probes, 3 functions, 0 embeds, 0 globals using
134864virt/110040res/16128shr/93160data kb, in 0usr/0sys/6real ms.
Pass 3: translated to C into
"/tmp/stapROzKTg/stap_39f1aea4bfdb6b66b7e6b56fe5417d5a_2596_src.c" using
135920virt/111320res/16384shr/94216data kb, in 10usr/70sys/75real ms.
/tmp/stapROzKTg/stap_symbols.c:261:19: error: '_stp_module_0_debug_line_str'
undeclared here (not in a function); did you mean '_stp_module_0_debug_line'?
  261 | .debug_line_str = _stp_module_0_debug_line_str,
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                   _stp_module_0_debug_line
make[4]: *** [scripts/Makefile.build:243: /tmp/stapROzKTg/stap_symbols.o] Error
1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [Makefile:1931: /tmp/stapROzKTg] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "stap_39f1aea4bfdb6b66b7e6b56fe5417d5a_2596.ko" in
2570usr/260sys/2873real ms.
Pass 4: compilation failed.  [man error::pass4]
Kernel version 6.6.11 is outside tested range 2.6.32 ... 6.6-rc1
FAIL: usymfileline () startup (eof)

See the similar messages for the following tests of "make installcheck" 

      FAIL: usymfileline () startup (eof)
      FAIL: usymfileline () startup (eof)
      FAIL: usymline () startup (eof)
      FAIL: usymline () startup (eof)
      FAIL: usymfile () startup (eof)
      FAIL: usymfile () startup (eof)
      FAIL: pp == usymfileline startup (eof)
      FAIL: systemtap.examples/profiling/fileline-profile run
      FAIL: systemtap.examples/profiling/fileline-profile run
      FAIL: systemtap.examples/profiling/periodic build

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

             reply	other threads:[~2024-01-22 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 18:59 wcohen at redhat dot com [this message]
2024-02-18  7:21 ` [Bug runtime/31274] " 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-31274-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).