public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Serhei Makarov" <me@serhei.io>
To: "Khadija Abdulkarim AlAradi via systemtap" <systemtap@sourceware.org>
Subject: Re: guru mode: invalid module format
Date: Fri, 14 Jun 2019 14:55:00 -0000	[thread overview]
Message-ID: <bd5358fe-4458-4475-b1f4-0840f034754d@www.fastmail.com> (raw)
In-Reply-To: <20190613234749.GC32764@redhat.com>

On Thu, Jun 13, 2019, at 7:48 PM, Frank Ch. Eigler wrote:
> Thanks for your patience.  I have not been able to reproduce this here
> on Fedora, so didn't look deeper until today.  I believe the problem
> may be buildrun.cxx:124, which for guru mode adds a
> CONFIG_MODEVERSIONS= override into the module kbuild makefile.
> Non-fedora kernels may interpret this differently.
I haven't been able to reproduce on Ubuntu either. Trying to think if there's any other distribution/kernel where this option is likely to work differently.

The reproduction steps point to another potential problem -- the regular and guru mode scripts are being compiled differently, but they appear to be treated equivalently by stap's compilation cache. Therefore deleting the cache changes the outcome of $ stap helloworld.stp -g

-- 
All the best,
    Serhei
    https://serhei.io

  reply	other threads:[~2019-06-14 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  7:12 Aubrey Li
2019-05-07 13:40 ` Aubrey Li
2019-05-07 19:58   ` Frank Ch. Eigler
2019-05-08  3:46     ` Aubrey Li
2019-06-13 23:47       ` Frank Ch. Eigler
2019-06-14 14:55         ` Serhei Makarov [this message]
2019-06-17 20:13           ` Serhei Makarov
2019-06-18  1:43             ` Aubrey Li

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=bd5358fe-4458-4475-b1f4-0840f034754d@www.fastmail.com \
    --to=me@serhei.io \
    --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).