public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/14703] New: Add runtime/dyninst support for symbols & backtracing
Date: Thu, 11 Oct 2012 19:03:00 -0000	[thread overview]
Message-ID: <bug-14703-6586@http.sourceware.org/bugzilla/> (raw)


http://sourceware.org/bugzilla/show_bug.cgi?id=14703

             Bug #: 14703
           Summary: Add runtime/dyninst support for symbols & backtracing
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dyninst
        AssignedTo: systemtap@sourceware.org
        ReportedBy: jistone@redhat.com
    Classification: Unclassified


The dyninst runtime currently lacks any symbol resolution or backtrace
functions.

I'm not sure how much this is possible, with all the rewriting that dyninst
does to the process.  I'm not aware of any mutatee-side APIs to help out here. 
But for the first level uaddr(), at least, the pt_regs are currently passing
the original PC location.  We might also be able to inspect live unwind info,
especially if Dyninst's fix for PR14702 updates the appropriate sections.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-10-11 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 19:03 jistone at redhat dot com [this message]
2013-06-05 19:12 ` [Bug dyninst/14703] " jistone at redhat dot com
2016-08-18 15:52 ` bugzilla at tecnocode dot co.uk
2020-06-16 21:12 ` 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-14703-6586@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).