This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/14026] print_ubacktrace doesn't resolve the symbol name
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Sun, 06 May 2012 21:15:41 +0000
- Subject: [Bug runtime/14026] 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
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #20 from Frank Ch. Eigler <fche at redhat dot com> 2012-05-06 21:15:41 UTC ---
(In reply to comment #19)
> I finally understand what is happening, though I still don't understand how it
> can happen.
>
> The real problem is that we enter the unwinder with PC 8074811. While the probe
> point actually is 8074810.
The code you quote refers to the struct uprobe->vaddr as the intended original
address of the breakpoint. Perhaps that address is being munged.
Have we seen yet a version of the run with -DDEBUG_UPROBES and stap -p3 output?
Which uprobes/utrace version was being used? (stap-report?)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.