public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/6580] revamp backtrace-related tapset functions
Date: Tue, 05 Jan 2010 09:38:00 -0000	[thread overview]
Message-ID: <20100105093810.26583.qmail@sourceware.org> (raw)
In-Reply-To: <20080529170209.6580.fche@redhat.com>


------- Additional Comments From mjw at redhat dot com  2010-01-05 09:38 -------
The split between sym*/backtrace() for kernel side and usym*/ubacktrace() for
user side is confusing. We really should deduce from the probe context which one
the user wants.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|mjw at redhat dot com       |systemtap at sources dot
                   |                            |redhat dot com
             Status|ASSIGNED                    |NEW


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2010-01-05  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 19:31 [Bug tapsets/6580] New: " fche at redhat dot com
2008-08-20 12:27 ` [Bug tapsets/6580] " fche at redhat dot com
2008-09-01 12:33 ` mjw at redhat dot com
2008-09-02 10:15 ` mjw at redhat dot com
2009-03-20 19:33 ` fche at redhat dot com
2009-03-30 11:59 ` mjw at redhat dot com
2010-01-05  9:38 ` mjw at redhat dot com [this message]
     [not found] <bug-6580-6586@http.sourceware.org/bugzilla/>
2011-09-08 17:11 ` mjw at redhat dot com
2012-05-08 18:45 ` 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=20100105093810.26583.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).