Opened 9 years ago
Closed 7 years ago
#14097 closed defect (duplicate)
Fix broken 'sage -valgrind' interaction with ipython
| Reported by: | mabshoff | Owned by: | jason |
|---|---|---|---|
| Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
| Component: | misc | Keywords: | valgrind, ipython |
| Cc: | vbraun | Merged in: | |
| Authors: | mabshoff | Reviewers: | |
| Report Upstream: | N/A | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
Status badges
Description
In 5.6 Sage fails to start under valgrind due to interaction with ipython. The attached patch fixes the problem.
Attachments (1)
Change History (11)
Changed 9 years ago by
comment:1 Changed 8 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:2 Changed 8 years ago by
- Cc vbraun added
comment:3 Changed 8 years ago by
Note that valgrind-3.9.0 is out.
comment:4 Changed 8 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:5 Changed 7 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:6 Changed 7 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:7 Changed 7 years ago by
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
I've added this to #15586, propose to close as duplicate
comment:8 Changed 7 years ago by
- Status changed from new to needs_review
I agree, let's close this one.
comment:9 Changed 7 years ago by
- Status changed from needs_review to positive_review
comment:10 Changed 7 years ago by
- Resolution set to duplicate
- Status changed from positive_review to closed
Note: See
TracTickets for help on using
tickets.
I tried the above fix and it did not change anything for me on top of Sage 5.11 unfortunately.
Running a command equivalent to what sage-valgrind does (without the patch here) from a sage shell (./sage -sh) *just works* so something really fishy is going on here...