From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/24224] tapsets.cxx Assert kernel relocation invariants fails for some kernel.function("*@*.c:*") probes
Date: Tue, 26 Feb 2019 19:18:00 -0000 [thread overview]
Message-ID: <bug-24224-6586-7BaLfeYYGN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24224-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24224
--- Comment #5 from William Cohen <wcohen at redhat dot com> ---
Mark Wielaard suspects the problem is due to some code in tapsets.cxx. From
IRC log:
<mjw> I think it is this:
<mjw> q.results.push_back(new dwarf_derived_probe
(funcname, filename,
<mjw>
i->decl_line, module,
<mjw> section,
i->entrypc,
<mjw>
i->entrypc, q,
<mjw>
&i->die));
<mjw> The second i->entrypc should be "relative"
<wcohen> mjw, where is that?
<mjw> tapsets.cxx:5492
Those changes from the following git commit:
commit 68bd23fd0cc5efa4fccad68e0df0d0c4cb774322
Author: Jafeer Uddin <juddin@redhat.com>
Date: Mon Dec 10 15:11:26 2018 -0500
PR16596: add support for DW_OP_GNU_entry_value in location expressions
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-02-26 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 21:06 [Bug translator/24224] New: " wcohen at redhat dot com
2019-02-15 21:33 ` [Bug translator/24224] " wcohen at redhat dot com
2019-02-22 21:58 ` wcohen at redhat dot com
2019-02-26 15:49 ` wcohen at redhat dot com
2019-02-26 18:44 ` wcohen at redhat dot com
2019-02-26 19:18 ` wcohen at redhat dot com [this message]
2019-02-26 19:23 ` [Bug translator/24224] tapsets.cxx kernel relocation assert fails when attempting to access some function parameters wcohen at redhat dot com
2019-03-08 16:33 ` 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-24224-6586-7BaLfeYYGN@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).