From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/17894] global_opt_unknown.exp failure
Date: Wed, 28 Jan 2015 16:50:00 -0000 [thread overview]
Message-ID: <bug-17894-6586-PbLpN9xGGb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17894-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17894
--- Comment #4 from Josh Stone <jistone at redhat dot com> ---
Ah, ignoring is relatively new behavior:
54041d8a7333 modules: don't fail to load on unknown parameters.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=54041d8a73337411b485ff76957fb106cb5d40d0
$ git describe --contains 54041d8a7333
v3.11-rc1~44^2~2
(In reply to Martin Cermak from comment #2)
> So looking at PR17858, we now have inconsistent behavior between kernel and
> dyninst runtimes in case an unknown parameter gets passed.
Given that kernels are now inconsistent, this can't be helped. I think it's
best to keep the dyninst runtime following newer kernels, but I'll see about
tweaking the test for kernels prior to 3.11.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-01-28 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 9:38 [Bug runtime/17894] New: " mcermak at redhat dot com
2015-01-28 9:38 ` [Bug runtime/17894] " mcermak at redhat dot com
2015-01-28 9:49 ` mcermak at redhat dot com
2015-01-28 10:00 ` mcermak at redhat dot com
2015-01-28 16:50 ` jistone at redhat dot com
2015-01-28 16:50 ` jistone at redhat dot com [this message]
2015-01-28 18:24 ` jistone 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-17894-6586-PbLpN9xGGb@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).