From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug documentation/13713] MAXTRACE/MAXBACKTRACE undocumented feature
Date: Mon, 20 Feb 2012 13:55:00 -0000 [thread overview]
Message-ID: <bug-13713-6586-CGKYGHmF2o@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13713-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13713
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mjw at redhat dot com
Resolution| |FIXED
--- Comment #1 from Mark Wielaard <mjw at redhat dot com> 2012-02-20 13:54:41 UTC ---
This has been fixed in Systemtap 1.7, from the NEWS file:
- MAXBACKTRACE did work in earlier releases, but has now been documented
in the stap 1 manual page.
commit 14bf445209e09681d9caa7eab2205d549fe43b3c
Author: Mark Wielaard <mjw@redhat.com>
Date: Mon Jul 25 15:52:30 2011 +0200
Clean up maximum backtrace level code. And document MAXBACKTRACE.
Lots of functions passed around the maximum level of backtraces allowed.
Now all consolidated inside stack.s. And documented in stap.1.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-02-20 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 6:00 [Bug documentation/13713] New: " brendan.gregg at joyent dot com
2012-02-20 13:55 ` mjw at redhat dot com [this message]
2012-02-21 23:21 ` [Bug documentation/13713] " brendan.gregg at joyent dot com
2012-02-22 9:01 ` mjw 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-13713-6586-CGKYGHmF2o@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).