New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sage 3.2.1 + interactive gdb or valgrind are broken #4792
Comments
sagetrac-mabshoff
mannequin
changed the title
Sage 3.2.1+valgrind is completely broken
Sage 3.2.1+ interactive valgrind is completely broken
Dec 14, 2008
comment:2
The same applies to Sage+gdb. Note:
Cheers, Michael |
sagetrac-mabshoff
mannequin
changed the title
Sage 3.2.1+ interactive valgrind is completely broken
Sage 3.2.1 + interactive gdb or valgrind are broken
Dec 14, 2008
comment:3
Ok, here is some more info: The problem stems from the way we change initialization of ipython:
The above steps are from ipy_profile_sage.py in local/bin. Cheers, Michael |
comment:4
Attachment: trac_4792.patch.gz |
comment:5
Thanks Mike, positive review. I was getting close myself, but you beat me to it :) Cheers, Michael |
comment:6
Merged in Sage 3.2.2.rc0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Notice the following:
I would blame the IPython fixes, but I have zero evidence so far.
Cheers,
Michael
CC: @mwhansen
Component: packages: standard
Issue created by migration from https://trac.sagemath.org/ticket/4792
The text was updated successfully, but these errors were encountered: