This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/14026] inode based uprobes print_ubacktrace doesn't resolve the symbol name
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 07 May 2012 13:44:33 +0000
- Subject: [Bug runtime/14026] inode based uprobes print_ubacktrace doesn't resolve the symbol name
- Auto-submitted: auto-generated
- References: <bug-14026-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14026
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
Summary|print_ubacktrace doesn't |inode based uprobes
|resolve the symbol name |print_ubacktrace doesn't
| |resolve the symbol name
--- Comment #23 from Mark Wielaard <mjw at redhat dot com> 2012-05-07 13:44:33 UTC ---
(In reply to comment #22)
> I guess that could be happening, but how?
>
> This is done this way to have an architecture neutral way of setting REG_IP to
> the actual probe address. But if it is unreliable then we might just have to
> make this architecture specific and have some ADJUST_REG_IP_BREAKPOINT macro
> that does the right thing per architecture. This might be needed anyway for the
> inode based uprobe handler which currently has:
>
> // XXX: Can't set SET_REG_IP; we don't actually know the relocated address.
This is indeed "it"!
<groleo> the latest k3.0 and the uprobes patch is the one here
http://sourceware.org/ml/systemtap/2011-q3/msg00157.html
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.