#16978: Update gdb
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: packages: | Resolution:
experimental | Merged in:
Keywords: | Reviewers:
Authors: Volker Braun | Work issues:
Report Upstream: N/A | Commit:
Branch: | 1d96394ac16acdc331aed78acaca2f3a8acd097c
u/vbraun/update_gdb | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:6 vbraun]:
> > Will the Python build match if I take a sage install created with
`SAGE_DEBUG=yes`, and later do `sage -i gdb`?
>
> If and only if you don't change the setting of the `SAGE_DEBUG`
environment variable in the meantime.
OK, I will do "make" and "sage -i gdb" without break, and without changing
`SAGE_DEBUG`.
What happens if I change later some Cython file and compile this without
`SAGE_DEBUG`. Would gdb work on that file, since it only matters that
Python itself was build with `SAGE_DEBUG`? Or would gdb simply not work on
that single non-debug compiled Cython file?
--
Ticket URL: <http://trac.sagemath.org/ticket/16978#comment:7>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
