#13865: Make SAGE_DEBUG three-state
-----------------------------+----------------------------------------------
Reporter: vbraun | Owner: mvngu
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.6
Component: documentation | Keywords:
Work issues: | Report Upstream: N/A
Reviewers: | Authors:
Merged in: | Dependencies:
Stopgaps: |
-----------------------------+----------------------------------------------
Currently, `SAGE_DEBUG` is documented as
{{{
If it is unset (the default) or set to “yes”, then debugging is turned on.
}}}
This is fine if you just add `gcc -g`, but the utility of having a real
Python debug build shows that there should be more to debugging than just
adding symbols. However, this has a real performance impact and should not
be the default. So I propose that `SAGE_DEBUG` have three possible values:
* `SAGE_DEBUG=no` means no debugging symbols (no `gcc -g`), which mostly
saves disk space.
* `SAGE_DEBUG=yes` builds debug versions if possible (in particular,
Python and Singular). These will be notable slower.
* Anything else (including unset `SAGE_DEBUG`) is the same as the old
default, compile with debugging symbols but no debugging options that
influence performance.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13865>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
