From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/24954] stapdyn on ppc/aarch64 do not support full register set
Date: Fri, 30 Aug 2019 21:13:00 -0000 [thread overview]
Message-ID: <bug-24954-6586-vTkk5gTT0a@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24954-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24954
--- Comment #1 from Stan Cox <scox at redhat dot com> ---
ah so for -O0 on ppc the stap probe gets the value from r31 + 0x80 but r31 is
not setup due to 8 arg restriction. optimization often works because r31 isn't
used. not too familiar with ppc, why not r1 (sp) + 0x80 ?
stapdyn sets up the probe register context using a dyninst synthesized call,
which dyninst limits to the number of register args. stapdyn sets up only
those registers so if a probe variable access requires a register that isn't
set, e.g. r31 + 0x80, then it fails.
If a non set register is not required, oftentimes this will be the case with
-O2, then the access will succeed. The possible solution is to set up all the
regs using multiple synthesized calls. See mutatee.cxx::get_dwarf_registers,
mutatee.cxx::mutatee::instrument_dynprobe_target,
uprobes-regs.c::enter_dyninst_uprobe_regs.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-08-30 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 21:02 [Bug dyninst/24954] New: " scox at redhat dot com
2019-08-30 21:13 ` scox at redhat dot com [this message]
2019-12-11 15:05 ` [Bug dyninst/24954] " scox at redhat dot com
2020-06-05 13:47 ` scox at redhat dot com
2020-06-16 20:34 ` scox 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-24954-6586-vTkk5gTT0a@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).