public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/11249] Tracking executable plus library fails on i386
Date: Fri, 05 Mar 2010 17:40:00 -0000	[thread overview]
Message-ID: <20100305173942.10553.qmail@sourceware.org> (raw)
In-Reply-To: <20100204125941.11249.mjw@redhat.com>


------- Additional Comments From jkenisto at us dot ibm dot com  2010-03-05 17:39 -------
(In reply to comment #5)
...
> 
> I haven't explicitly tested uprobes on relative calls and jumps, so maybe
> they've never worked.  Perhaps all the calls and [conditional] jumps listed in
> Comment #4 of PR #5509 are suspect.

Come to think of it, a couple of years ago I ran tests where I put a uprobe on
every instruction in a specified function or address range.  (They took
advantage of the fact that for x86_32, the address in the objdump -d output was
the virtual address in the running process.)  They worked only when stap supported
  probe process(pid).statement(addr).absolute[.return]
which it didn't for many months after dwarf support was added.  I'll attach the
awk scripts that generated the stap scripts.

Anyway, those tests definitely probed some relative jumps and calls -- but not
in libraries.  It might be worthwhile to try them again.  (Srikar and/or Ananth
are picking this up investigation again.)

Is it possible you're seeing a situation where the destination address, when the
call/jump instruction is in the SSOL area, is past 0xc0000000?

-- 


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.

  parent reply	other threads:[~2010-03-05 17:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 12:59 [Bug runtime/11249] New: " 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 [this message]
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

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=20100305173942.10553.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).