From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug uprobes/11249] uprobes fails on glibc get-pc-thunk call insn probe
Date: Sat, 13 Mar 2010 22:27:00 -0000 [thread overview]
Message-ID: <20100313222722.26035.qmail@sourceware.org> (raw)
In-Reply-To: <20100204125941.11249.mjw@redhat.com>
------- Additional Comments From jkenisto at us dot ibm dot com 2010-03-13 22:27 -------
After applying the patch from PR #11376, to get stap to emit correct code for
stap scripts generated by probe*.awk, I ran some a couple of simple tests, and
verified that uprobes still seems to support probing of relative jumps and
calls, at least in executable binaries. I didn't test shared libs, where
addressing is more complicated.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11249
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2010-03-13 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 12:59 [Bug runtime/11249] New: Tracking executable plus library fails on i386 mjw at redhat dot com
2010-02-04 13:17 ` [Bug runtime/11249] " mjw at redhat dot com
2010-02-04 13:26 ` mjw at redhat dot com
2010-02-04 14:13 ` mjw at redhat dot com
2010-03-04 17:46 ` srikar at linux dot vnet dot ibm dot com
2010-03-05 0:41 ` jkenisto at us dot ibm dot com
2010-03-05 17:40 ` jkenisto at us dot ibm dot com
2010-03-05 17:43 ` jkenisto at us dot ibm dot com
2010-03-05 17:44 ` jkenisto at us dot ibm dot com
2010-03-09 17:15 ` [Bug uprobes/11249] uprobes fails on glibc get-pc-thunk call insn probe fche at redhat dot com
2010-03-13 22:27 ` jkenisto at us dot ibm dot com [this message]
[not found] <bug-11249-1110@http.sourceware.org/bugzilla/>
2010-11-04 1:11 ` jistone at redhat dot com
2010-11-17 0:20 ` jistone at redhat dot com
[not found] <bug-11249-6586@http.sourceware.org/bugzilla/>
2020-02-18 21:47 ` fche 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=20100313222722.26035.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).