From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-16748-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 31713 invoked by alias); 15 Sep 2010 21:32:22 -0000
Received: (qmail 31317 invoked by uid 48); 15 Sep 2010 21:32:07 -0000
Date: Wed, 15 Sep 2010 21:32:00 -0000
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20100915213207.12026.wcohen@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug runtime/12026] New: Revamp task_backtrace() to use same unwinder backtrace()
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2010-q3/txt/msg00421.txt.bz2

The task_backtrace() uses it own unwinder mechanism in _stp_stack_print_tsk().
It looks like there could be some simplification if task_backtrace(), used the
machinery as backtrace(). It might also make the task_backtrace() work better
than the current version of task_backtrace().

A improved version of task_backtrace() would be very useful for improving the
performance of latencytap.

-- 
           Summary: Revamp task_backtrace() to use same unwinder backtrace()
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: wcohen at redhat dot com
OtherBugsDependingO 6960
             nThis:


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

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