Currently, SAGE_DEBUG is documented as
"If it is unset (the default) or set to 'yes', then debugging is turned
on."
As the "How to proceed to reduce Sage's memory leaking" thread shows, we
should make it easy for developers to build Python with debugging, which
has a certain performance impact. So that shouldn't be the default, but we
don't really need another arcane environment variable either. I propose
that we use SAGE_DEBUG in three different ways:
* SAGE_DEBUG=no means no debugging symbols (no gcc -g), which basically
only saves disk space.
* SAGE_DEBUG=yes builds debug versions if possible (in particular, Python
and Singular). These will be notable slower but allow us to pinpoint memory
problems much more easily.
* Anything else (including unset SAGE_DEBUG) is the same as the old
default, compile with debugging symbols but no debugging options that
influence performance.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
