public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/4633] New: backtracing broken
Date: Tue, 12 Jun 2007 19:57:00 -0000	[thread overview]
Message-ID: <20070612195708.4633.fche@redhat.com> (raw)

Bug #3050 may have been closed but the bug did not stay dead.  The same code on
current fc7 kernels gives the usual single line of backtrace info.
The kernel backtracer always seems to do a better job than the code in the runtime.

There are several problems with the code.  It uses unprotected dereference code
like "*stack++", even though the stack values are not completely reliable.  It
does not know how to distinguish between alternative stacks such as the trap stack,
the normal kernel stack, or whatever happens to come in pt_regs.  This is key
because backtrace() should from both kprobes and from ordinary hook calls
such as timers, begin/end, and markers.  The backtrace() function should not
include the "Inexact backtrace:" string, as this breaks subsequent tokenizing 
with print_stack().

-- 
           Summary: backtracing broken
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com
  GCC host triplet: x86-64


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

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

             reply	other threads:[~2007-06-12 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 19:57 fche at redhat dot com [this message]
2007-06-12 20:56 ` [Bug runtime/4633] " fche at redhat dot com
2007-08-20 17:40 ` mhiramat at redhat dot com
2007-08-20 21:39 ` 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=20070612195708.4633.fche@redhat.com \
    --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).