This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug documentation/13713] MAXTRACE/MAXBACKTRACE undocumented feature
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 20 Feb 2012 13:54:41 +0000
- Subject: [Bug documentation/13713] MAXTRACE/MAXBACKTRACE undocumented feature
- Auto-submitted: auto-generated
- References: <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.